SLA Template Filtering: A Faceted Approach
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


SLA Template Filtering: A Faceted Approach

Uploaded on

Presentation in Valencia, Spain, 30.05.2013

Presentation in Valencia, Spain, 30.05.2013

More in: Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • Same number of experiments for both databases.Test 1: total time of the filtering operation over HTTP.Total time starts from the point a client request reaches the server up to the point the server returns the result to the client. Timings include HTTP and backend processing overhead.Concurrent client requests of diverse service parameters reach the server. A Python process handles the requests and returns the results over HTTP.Incoming parameters represent SLA facet attributes. Their number depends from the facet type and its nesting depth.
  • Test 2: filtering runs are processed locally on the server to avoid additional network overhead. Measurements combine the query processing from filtering and database updates to measure their overhead on the filtering operation.Update queries are processed in parallel to filtering requests and account for an extra 10% of workload on the total database processing. Start with 100 and reach up to 100,000 concurrent requests for both databases.


  • 1. T H E F O U R T H I N T E R N AT I O N AL C O N F E R E N C E O N C L O U DC O M P U T I N G , G R I D S , AN D V I R T U AL I Z AT I O NC L O U D C O M P U T I N G 2 0 1 3SLA Template Filtering:A Faceted ApproachK. Stamou, V. Kantere and J.H. Morin{aikaterini.stamou, verena.kantere, jean-henry.morin}@unige.chJune 1, 2013Institute of Services Science (ISS)
  • 2. ContentsJune 1, 2013Institute of Services Science (ISS) Problem formalization Faceted navigation SLA template repository Experimentation On-going work, conclusions
  • 3. SLA definition, tree-structureJune 1, 2013Institute of Services Science (ISS) A Service Level Agreement provides an explicit view on howaservice provisioning is planned Providers and customers use SLAs to measure actualconsumption of resources during service execution SLAs represent nested tree structures According to (Ludwig et al. 2003, Andrieux etal. 2007) a SLA consists of three primary sections:o Service descriptiono Guarantees or obligationso Aninformativesectionregardinginvolvedpartiesand/or the provisionedservice
  • 4. Research challengesJune 1, 2013Institute of Services Science (ISS) Obstacle: SLAs hardly appear in marketplaces… Equilibrium: SLAs as automated processes vs. static, non-machine readable documents Semantic and structural heterogeneity of SLA content, semi-structured data of unbounded length SLA data model requirements: Modularity Dynamic updates Rapid traversals through branches of diverse, nested information
  • 5. SLA templatesJune 1, 2013Institute of Services Science (ISS) A pre-instantiated SLA that encloses aprovider’s resourceavailability and provisioning plan Customers review SLA templates and proceed with eitheragreement initialization or negotiation with service providers SLA templates: Can be viewed as ”What You See Is What You Get” (WYSIWIG) snapshots Include dynamic information that is updated at frequent time intervals Need to ensure dynamic content updates Content modularity allows viewing service offer sections as facets
  • 6. Facets, SLA data-modelJune 1, 2013Institute of Services Science (ISS) A facet represents a category of hierarchically orderedinformation SLA faceted filtering enables flexible service navigation that isdriven by customer provisioning requirements Data-model: Data categorization into distinct SLA modules Nesting within a SLA template module depends on information content Information granularity
  • 7. SLA filtering modelJune 1, 2013Institute of Services Science (ISS) 2-layered design A template may contain up to NSLAroot-themes Parametercombinationsindicate navigationand filtering options Data modularity and modelmultidimensional structure allowfor quick and selectivenavigation through designatednested information
  • 8. SLA template storageJune 1, 2013Institute of Services Science (ISS) Document-basedschema (MongoDB) Relationalschema (MySQL)
  • 9. Experimentation setupJune 1, 2013Institute of Services Science (ISS) Filters in faceted navigation translate customer choices into conditionalqueries Assumptions: An IT marketplace provides SLA faceted navigation as an interaction tool forcustomers to submit their criteria One centralized data repository for the SLA template storage Simulation environment setup: 24 Intel-Xeon 2.50 GHz computing machine, 128GB of RAM, OS: Ubuntu 12.04 Web server deployment: Tornado (Python) Client: multithreaded Python scripts pass HTTP GET requests to the web server Both DBMS are deployed on the same machine to reduce TCP overhead Goal: server response timeto incoming customer requests and scalabilityof the filtering operation as the number of simultaneous requests increase
  • 10. Experimentation resultsJune 1, 2013Institute of Services Science (ISS)oConcurrent client requests of diverse service parameters reach the serveroIncoming parameters represent SLA facet attributesoTest 1: total time of thefiltering operation overHTTPoTimings include HTTPand backend processingoverhead
  • 11. Experimentation resultsJune 1, 2013Institute of Services Science (ISS)oTest 2: filtering runs areprocessed locally on the server toavoid additional network overheadoStart with 100 and reach up to100,000 concurrent requests forboth databasesoUpdate queries are processedin parallel to filtering requestsand account for an extra 10% ofworkload on the total databaseprocessing
  • 12. Conclusions and on-going workJune 1, 2013Institute of Services Science (ISS)oA NoSQL approach possibly fits better for the web scenario, where SLAoffers are manipulated over HTTPoCurrent work involves the SLA transformation into a dependency graph(Ward et al. 2002)oExperimentationwith regular pathqueries can helpevaluate thepros/cons of thegraph databaseapproach
  • 13. Thank you!June 1, 2013Institute of Services Science (ISS)Q&A:
  • 14. ReferencesJune 1, 2013Institute of Services Science (ISS)Ludwig, H., Keller, A., Dan, A., King, R.P., Franck, R. 2003."Web Service Level Agreement (WSLA) LanguageSpecification," in: IBM Research. IBM Corporation.Andrieux, A., Czajkowski, K., Dan, A., Keahey, K., Ludwig, H.,Nakata, T., Pruyne, J., Rofrano, J., Tuecke, S., Xu, M.2007. "Web Services Agreement Specification (WS-Agreement)." Open Grid Forum.Ward, C., Buco, M.J., Chang, R. N., Luan, L. Z. 2002. "AGeneric SLA Semantic Model for the ExecutionManagement of E-Business Outsourcing Contracts,"Proceedings of the Third International Conference on E-Commerce and Web Technologies: Springer-Verlag, pp.363-376.