1. Raffaele Di Fazio Connecting to the Clouds Cloud Brokers and OCCI.

2. Overview The Broker, components and architecture jOCCI: an OCCI Java implementation The “Connector Project” A full overview November 2012 Raffaele Di Fazio- 2

3. Disclaimer My visibility on the projects was limited. I was just asked to design and develop with a general overview of the goals. I do NOT have any details about European projects involved with the cloud broker nor any of the other parts I will show to you. November 2012 Raffaele Di Fazio- 3

4. The Broker November 2012 Raffaele Di Fazio- 4

5. The Broker: a cloud perspective A cloud broker is an intermediary between the customer and a cloud provider. The goal of a Cloud Broker is: To be able to provide a unified interface to manage multiple cloud providers. To simplify the choice for the customer. To try to understand the need of the customer and to find the provider that best suits its needs. November 2012 Raffaele Di Fazio- 5

6. The Broker: a cloud perspective Can have different goals based on the user request: Try to minimize the costs. Try to give the fastest service (i.e. deploying in EU instead of US) The Broker, essentially: propose the user a service. November 2012 Raffaele Di Fazio- 6

7. Cloud Platforms At the beginning: one player (Amazon) Now: multiple players, variegated offer. Several cloud providers: Amazon VCloud HP Cloud Eucalyptus … November 2012 Raffaele Di Fazio- 7

8. Amazon Web Services November 2012 Raffaele Di Fazio- 8

9. HP Cloud November 2012 Raffaele Di Fazio- 9

10. OpenStack A scalable “operating system” for cloud computing. It is used to control “compute, network, storage” resources. A “compute” is any information processing resource (i.e. a VM). It can be used to control cloud infrastructures. It is a software suite. This leads to multiple custom clouds ( see http://www.openstack.org/user-stories/) November 2012 Raffaele Di Fazio- 10

11. Differences btw cloud providers Interfaces APIs Costs Way of managing the VMs (i.e. different functionalities) Even the terminology used can be different. GOAL: simplify this mess! November 2012 Raffaele Di Fazio- 11

12. Broker + OCCI + Proactive November 2012 Raffaele Di Fazio- 12 OCCI Server ProActive Cloud Provider Broker

13. Broker + OCCI + Proactive: 2 nd architecture November 2012 Raffaele Di Fazio- 13 OCCI Server Broker Cloud Provider ProActive

14. Broker + OCCI + Proactive: expanded November 2012 Raffaele Di Fazio- 14 OCCI Server ProActive Broker jOCCI PROCCI Cloud connectors

15. JOCCI: AN OCCI JAVA LIBRARY November 2012 Raffaele Di Fazio- 15

16. Dictionary… pay attention! OCCI has a particular naming convention we must follow. There are very common words that are keywords when speaking about OCCI. Kind, Link, Resource, Attributes, Category are some of them. Other classes are: Parser, Server, Model. Please be careful! November 2012 Raffaele Di Fazio- 16

17. OCCI OCCI: Open Cloud Computing Interface It is a standard for interoperability between cloud platforms. GOALS: Interoperability: between cloud providers Portability: avoid vendor lock-in Integration: possibility to support multiple platforms Extensibility November 2012 Raffaele Di Fazio- 17

18. OCCI continued Currently focus on IaaS. An extension to support PaaS, SaaS is possible. It is a set of specifications: Core: Model specification Rendering: How to structure the OCCI requests … IN PRACTICE: RESTful protocol for cloud management tasks November 2012 Raffaele Di Fazio- 18

19. OCCI Core Model November 2012 Raffaele Di Fazio- 19

20. OCCI implementation – core Main classes reflect the OCCI core model: Category: basic classes to identify OCCI types Kind: type identification system for all the Entities. Mixin: extension mechanism for a Kind. Action: … Entity: abstract type of resource and link types Resource: represent a concrete resource and represents real world instances of VMs, etc. Link: association between two resources. November 2012 Raffaele Di Fazio- 20

21. jOCCI It is a OCCI server written in Java. Born because of the necessity to replace occi4java Unsupported, unmaintainable, ugly code. Inspired by the design of rOCCI, a ruby based OCCI implementation. November 2012 Raffaele Di Fazio- 21

22. jOCCI design goals Be extensible Model expressed by means of JSONs, defined at runtime. Extendible, following OCCI principles. No assumption on the backend (more about this later) Only supporting OCCI core model by default November 2012 Raffaele Di Fazio- 22

23. jOCCI implementation Made up of two components: OCCI Core: contains the definitions of all the classes representing the OCCI core specifications OCCI Server: contains the server, the parser and all the other classes with functionalities to handle OCCI requests/responses. This makes the development of the specification (CORE) and the server, decoupled. November 2012 Raffaele Di Fazio- 23

24. jOCCI core – features jOCCI implements only the core classes of the OCCI Model. Rough example: It defines what are the fields of the Kind class It does NOT define which types of Kind we can use (i.e. Compute) This approach makes jOCCI independent from a specific definition of the instances. November 2012 Raffaele Di Fazio- 24

25. jOCCI – Server Developed using the following technologies: Apache Tomcat RESTEasy Jackson (JSON parsing) Completely independent of the backend implementation. This is loaded at runtime (more about this later). November 2012 Raffaele Di Fazio- 25

26. jOCCI - Server REST interfaces supporting HEAD, GET, POST, PUT, DELETE HTTP methods. OCCI requests are HTTP requests that can be expressed in different formats. Request formats: text/occi, text/plain, application/json, etc. The server should be flexible enough to support these different types. November 2012 Raffaele Di Fazio- 26

27. Example of OCCI request curl -X POST --header 'Content-type:text/occi' --header 'X- OCCI-Attribute: method=start' http://localhost:8080/jocci/compute/8432c343-15ec-40ff-bb19- 1a7062a1aa5b?action=start --header 'Category: start; scheme="http://schemas.ogf.org/occi/infrastructure/compute/acti on#"; class="action"' -u demo:demo http://localhost:8080/jocci/compute/8432c343-15ec-40ff-bb19- 1a7062a1aa5b?action=start --header 'Category: start; scheme=" November 2012 Raffaele Di Fazio- 27

28. Broker + OCCI + Proactive: an Expanded view November 2012 Raffaele Di Fazio- 28 OCCI Server ProActive Broker jOCCI PROCCI Cloud connectors

29. PROCCI Connecting to ProActive: November 2012 Raffaele Di Fazio- 29

30. PROCCI Procci was created to be integrated with occi4java to allow ProActive to process OCCI requests. These requests are mainly intended to be used to manage virtual machines. The final goal of this interconnection is to be able to speak with the broker. November 2012 Raffaele Di Fazio- 30

31. PROCCI jOCCI parses OCCI requests. Methods exposed by PROCCI are called directly by jOCCI. Under the hood, a job is created and it is submitted to the scheduler. After the job is executed, a response is shown to the user through jOCCI by means of HTTP response. November 2012 Raffaele Di Fazio- 31

32. PROCCI Connection When jOCCI is started, it executes the setup phase. In each Action class attach the method implemented by the backend. This allow us to plug the actions to be executed. Does not force jOCCI to know the backend. November 2012 Raffaele Di Fazio- 32

33. PROCCI connection November 2012 Raffaele Di Fazio- 33

34. THE CONNECTOR PROJECT November 2012 Raffaele Di Fazio- 34

35. Broker + OCCI + Proactive: an Expanded view November 2012 Raffaele Di Fazio- 35 OCCI Server ProActive Broker jOCCI PROCCI Cloud connectors

36. The connector project We wanted to write several connectors to be able to connect to multiple cloud providers. Connectors are fundamental for the broker. It must talk with the cloud service providers. Technically they are built on top of APIs to connect to the cloud providers. Not much more to say here! November 2012 Raffaele Di Fazio- 36

37. A complete example A user submit a OCCI request to start an already created virtual machine. jOCCI receives the request. Once processed, it calls PROCCI. PROCCI creates a job. The job is submitted to ProActive scheduler. The job is executed. A remote cloud provider is called using a connector. November 2012 Raffaele Di Fazio- 37

38. November 2012 Raffaele Di Fazio- 38 That’s it! Thank you!