1. SLAng - SLA notation generator A language for defining SLAs Davide Lamanna, James Skene and Wolfgang Emmerich University College London Computer Science Department {d.lamanna | j.skene | w.emmerich}@cs.ucl.ac.uk

2. Agenda Goals Approach Structure of SLAng Example Conclusion and future work

3. Goals Producing a formal language, with a well defined syntax and semantics for describing service level specifications (SLSs) Specification of non functional features (service level) of contracts between independent parties to allow the integration with the functional design of a distribuited component system Parameterisation, compositionality, validation of service level agreements

4. Approach 1/3 To concentrate on specific, state-of-the-art application server technologies (J2EE) To associate performance targets with identifiable ASP components To use popular and standard information exchange formats (XML)

5. Approach 2/3 The semantics is not dependent on complete models of the ASP. It is instead defined in terms of the domains of the performance properties QoS properties are somewhat dependent on the system tier being described

6. Approach 3/3 We assume the use of components for assembly of distributed application services We require horizontal SLSs that govern interaction between components We also need vertical SLSs that govern the support components get from their infrastructure

7. Vertical and Horizontal SLAs Components Container Network Database UserComponents Container Network

8. SLAng SLAng - SLA notation generator XML schema Parameterisation of SLSs at different system tiers, including vertical and horizontal agreements Focuses on interfaces thus allowing compositionality XML format enables validation

9. Structure of SLAng (1/3)

10. Structures of SLAng (2/3)

11. Structure of SLAng (3/3)

12. What is a SLA? Service Level Agreement Service Level Specification Client Service Provider «instance» Legal Contract

13. General structure of a SLA contract

14. User (1/3)

15. User (2/3)

16. User (3/3)

17. Hosting (1/3)

18. Hosting (2/3)

19. Hosting (3/3)

20. Persistence (1/3)

21. Persistence (2/3)

22. Persistence (3/3)

23. Communication (1/3)

24. Communication (2/3)

25. Communication (3/3)

26. Service (1/3)

27. Service (2/3)

28. Service (3/3)

29. Container (1/3)

30. Container (2/3)

31. Container (3/3)

32. Networking (1/3)

33. Networking (2/3)

34. Networking (3/3)

35. An example: the auction scenario Auctioneer ASP ISPSSP Buyer n TTP Seller 1 Seller m Credit Rating Agency Retail Bank 1 Retail Bank j Service Level Agreement (SLA) Buyer 1

36. Actors and SLAs Auctioneer ASP ISP SSP TTP Seller Credit Rating Agency Retail Bank Buyer ASP Auctioneer Service Hosting CommunicationPersistenceUser

37. Parties ➔ Seller ➔ Auctioneer ➔ ASP ➔ SSP ➔ ISP Polish Philatelic Society Kracov Auction Today Los Angeles EuroTelecom Connect Newark (UK) Compaq.com Houston, Texas EarthLink Connecticut

38. Seller/auctioneer Polish Philatelic Society Kracov Auction Today Los Angeles

39. Auctioneer/ASP Auction Today Los Angeles 95% EuroTelecom Connect Newark (UK) 99.6%

40. Auctioneer/credit rating Auction Today Los Angeles 96% Fitch Ratings Hong Kong 26.7 3056

41. ASP/SSP EuroTelecom Connect Newark (UK) 99.6% Compaq.com Houston, Texas 97% 90% 97% 75% 80% 4967295 4294964225

42. ASP/ISP EuroTelecom Connect Newark (UK) 99.6% EarthLink Connecticut 010100

43. Conclusion and future work SLAng can specify tier-specific horizontal and vertical SLAs between users and providers Easily extendable to increase expressivity Modeling and reasoning about SLAs Translating an SLA into a deployment descriptor Monitoring compliance to SLA Toolkit for service composition and analysis (assist ASP in determining what SLSs they can undertake to meet)

44. Questions ?