Semantically enhanced SLA Negotiation

1. Semantically enhanced SLA Negotiation Bastian Koller, High Performance Computing Center Stuttgart Semantic Week, Amsterdam

2. Motivation Contractual relationships between customer and providers require to support both in the process of service trading The contract is the result of a negotiation process between both parties An SLA can be used as electronic representation of contractual terms It is important to have a SLA description for SLA templates and the SLA specification terms for the provision of the service (service description), Quality of service (QoS) level to be maintain, Information about resources to be provided, the liability to compensation if SLAs are not met. WS-Agreement covers the syntacticaspects in the description of SLA, but not the vocabulary terms Additionally Current SLA descriptions lack in interoperability: Open marketplace: Providers and consumers are collaborating on a global scale competing for offering and consuming services  not possible 2 Semantic Week, Amsterdam

3. Problem Area • RAMMemory: 7.5 GB • ComputeUnit: 4 ECU • Storage: 850GB • Platform: 64 bit • Price: $0.4 per instance hour Different languages, different metrics Negotiation AMAZON • ANSYS request • CPUName: IntelCore Duo • CPU Speed: 2 GHz • Capacity: 400 MB • Price: 27 euros per day • DiskSpace: 250GB Negotiation • MemoryPerTask: 7.5 GB • ClockCPUSpeed: 100 MHz / process • StorageCapability: 850GB • Cost: 5 euros/task/hour CUSTOMER Software engineering company BSC Semantic Week, Amsterdam

4. BREIN (SA)SLAs Introduction of semantic annotations in current SLA template files Based on SA-WSDL WS-Agreement + WSLA compatible (as based on a merge of both) Allows for annotating SLA description with pointers to semantic concepts Annotation of: SLA Parameters. Metrics RDF, OWL, WSML Semantic descriptions QoS metrics SLA terms modelReferences SchemaMappings SA-SLA Non-semantic descriptions SLA template Metric Parameter SLO Semantic Week, Amsterdam

5. A Customer needs something I am offeringsomething…with an execution time between 8 and 12 minutes I needsomething…I needthiswith a duration of 10 minutes Welcome to Babel I canwithexecution time I canwithexecution time I canwithexecution time But I needwithduration But I needwithduration Can youprovide? But I needwithduration Service Provider Customer Semantic Week, Amsterdam

6. What we want to achieve • Customers and Service Provider need to be enabled to understand each other on a common level • Ontologies can help to overcome this problem • Introduction of Semantic Components, enhancing the SLA Negotiation Process • Provisioning of a specification for Semantic Annotated Service Level Agreements – SA-SLAs Semantic Week, Amsterdam

7. I needsomethingwithduration I needtheontologyforthiscustomer Service Provider Domain The SLA translator is an ontology repository, which allows for managing the local domain ontology. Within it, the domain rules are formalized. The Translator is a component in both domains. The Ontology Repository is a third party storage, where Service Providers as well as Customers can store their Ontologies to make them available for other partiesand vice versa, other parties can query this for ontologies Yeswecan!! duration = execution time!!! duration = ??? SLA Mediator Hereyouare The SLA Mediator is able to match SA-SLA requests and offers, by converting SLA documents from other domains (e.g. bids or templates) into the local SLA model to be usable inside the respective domain. It can either query the Translator for the matching Ontology or, in case the Ontology is not available, request this from a third party Ontology Provider. With the Mediator, the high level SLA Parameters (between Provider and Customer) can be mapped down to the Service Provider Infrastructure level. The Mediator is a component in both domains. SLA Translator Semantic Week, Amsterdam

8. Third party The Architecture QoS common ontology SA-SLA Provider side Customer side SLA Negotiator SLA Template repository SLA Negotiator Send Bid Templates scores Match request Send Offer SA-SLA Create Instances SLA Mediator Do SPARQL query Local domain knowledge TSLA Parser Ontology Manager TSLA Selector Semantic Week, Amsterdam

9. Demo • ANSYS request • CPUName: IntelCore Duo • CPU Speed: 2 GHz • Capacity: 400 MB • Price: 27 euros per day • DiskSpace: 250GB • RAMMemory: 7.5 GB • ComputeUnit: 4 ECU • Storage: 850GB • Platform: 64 bit • Price: $0.4 per instance hour Semantic Week, Amsterdam

10. BREIN approach • ANSYS request • CPUName: IntelCore Duo • CPU Speed: 2 GHz • Capacity: 400 MB • Price: 27 euros per day • DiskSpace: 250GB SLA file semantic annotated Capacity -> qos:RAMMemory CPUSpeed -> qos:CPUSpeed DiskSpace -> qos:StorageCapacity • RAMMemory: 15 GB • ComputeUnit: 8 ECU • Storage: 1690GB • Platform: 64 bit • Price: $0.8 per instance hour • RAMMemory: 7.5 GB • ComputeUnit: 4 ECU • Storage: 850GB • Platform: 64 bit • Price: $0.4 per instance hour • RAMMemory: 1.7GB • ComputeUnit: 1 ECU • Storage: 160GB • Platform: 32 bit • I/O Performance = moderate • Price: $0.10 per instance hour • SLA file semantic annotated • RAMMemory -> qos:RAMMemory • ECU -> qos:EC2_ComputeUnit • Storage -> qos:StorageCapacity Semantic Week, Amsterdam

11. What happens in the demo? Semantic Week, Amsterdam

12. With the BREIN solution • Enhanced Interoperability • Optimal Offer/Counter Offer creation • Support when needed • Due to the non-invasive annotations Semantic Week, Amsterdam