1. Semantically enhanced SLA Negotiation Bastian Koller, High Performance Computing Center Stuttgart 5/5/2015Semantic Week, AmsterdamPage 1

2. 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 syntactic aspects 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 5/5/2015Page 2Semantic Week, Amsterdam

3. Problem Area Negotiation Different languages, different metrics ANSYS request CPUName: IntelCore Duo CPU Speed: 2 GHz Capacity: 400 MB Price: 27 euros per day DiskSpace: 250GB CUSTOMER Software engineering company -RAMMemory: 7.5 GB -ComputeUnit: 4 ECU -Storage: 850GB -Platform: 64 bit -Price: $0.4 per instance hour AMAZON -MemoryPerTask: 7.5 GB -ClockCPUSpeed: 100 MHz / process -StorageCapability: 850GB -Cost: 5 euros/task/hour BSC 5/5/2015Page 3Semantic 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 MetricParameterSLO modelReferencesSchemaMappings Non-semantic descriptions Semantic descriptions RDF, OWL, WSML SA-SLA SLA template QoS metricsSLA terms 5/5/2015Page 4Semantic Week, Amsterdam

5. A Customer needs something I need something…I need this with a duration of 10 minutes Service Provider Can you provide? Customer I am offering something…with an execution time between 8 and 12 minutes I can with execution time But I need with duration I can with execution time But I need with duration I can with execution time But I need with duration Welcome to Babel 5/5/2015Page 5Semantic 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 5/5/2015Page 6Semantic Week, Amsterdam

7. Service Provider Domain SLA Mediator duration = ??? SLA Translator I need something with duration I need the ontology for this customer Here you are 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. 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 parties and vice versa, other parties can query this for ontologies duration = execution time!!! Yes we can!! 5/5/2015Page 7Semantic Week, Amsterdam

8. The Architecture 5/5/2015Page 8 Customer side Third party QoS common ontology Send Bid SLA Negotiator SA-SLA SLA Negotiator Provider side Local domain knowledge SLA Template repository Create Instances Match request Do SPARQL query SLA Mediator TSLA Selector TSLA Parser Ontology Manager Send Offer SA-SLA Templates scores 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 5/5/2015Page 9Semantic Week, Amsterdam

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

11. What happens in the demo? 5/5/2015Page 11 Semantic Week, Amsterdam

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

13. BACKUP SLIDES 5/5/2015IOS 2009, BrusselsPage 13

14. SLA Negotiator SLA Negotiator Client Side –On behaver of customer –Receiving a bid from customer, which filled with desired QoS values. –Taking responsible to interact with SLA Negotiator Server SLA Negotiator Server Side –On behaver of Service provider –Checking service availablability –Using semantic Matching –Giving back a offer to Negotiator Client 5/5/2015BREIN — Vienna GAPage 14

15. availablability Negotiation Process for demo 5/5/2015BREIN — Vienna GAPage 15 SLA Negotiator Client SLA Template Page 15 bid, Negotiator URI SLA Negotiator (URI:http://localhost: http://localhost:8080/wsrf/services/ Brein/demo/sla-negotiation) SLA Mediator ( URI://localhost(SLAT/SLATServ let) SLA Mediator (URI://localhost(SLAT/ SLATServlet ) Ontology Manager SLA Repositoy (URI://localhost/sla/rep ositoy) Mediator URI offer URI

16. The negotiation sequence on the SP side 5/5/2015IOS 2009, BrusselsPage 16

17. SLAs in BREIN With the integration of Multiagent and Semantic Web concepts in BREIN, we foresee to enable –discovery on basis of SLA capabilities Customers will be able to define their requirements in “their language”, whereas the system understands this and is able to perform discover accordingly – a clear understanding of different SLA "languages" (term definitions) Current solutions require in-depth knowledge from the Users about the used SLA “language”  too much efforts, especially for SMEs –mapping between contractual terms and system terms Contractual terms are on a much higher level then system terms. (“timetocomplete” vs 4CPUs, 2days running…) –Automate the setup of the infrastructure according to the SLA and other requirements 5/5/2015IOS 2009, BrusselsPage 17

18. SLAs in BREIN (ii) Enable to…. –Dynamically negotiate QoS terms From “discrete offer” negotiation (one phase) to a multiphase negotiation, with offers and re-offers –Automatically understand the infrastructure capabilities for negotiation purposes Can I or can´t I offer this value (and I need to know this quick) –Optimize negotiation wrt business goals & policies Is it in my interest to negotiate this Service If I agree on an SLA of a high value customer, do I take the risk (intentionally) to violate an already running SLA of another –Compare current SLAs to prioritize (intentionally violation) –Optimize resource usage whilst still meeting the SLA 5/5/2015IOS 2009, BrusselsPage 18