How To Build An Open Source Cloud Broker

Transcription

1 CompatibleOne : The Open Source Cloud Broker Architecture overview Cedric Thomas, OW2 CEO Alexandre Lefebvre, OW2 CTO Labelled by & Berlin, 29th May 2012

2 IN A NUTSHELL Support for interoperability, portability and reversibility Open Source and Open Standards OpenStack, OpenNebula,... OCCI, Internet technologies, Blue Print for DevOps Models and documents to be shared by developers and operators, customers and vendors The 1st Open Source Cloud Broker As defined by Gartner Cloud Service Intermediation Aggregation Cloud Service Arbitrage Compliant with NIST Reference Architecture 2

3 ECOSYSTEM 3

4 STATE OF THE ART Interoperability between cloud services: to be constructed Portability between cloud services: much more difficult SaaS, IaaS, PaaS, BPaaS, etc. have very different APIs Significant gaps on SLA and Security De facto standards vs. open standards No incentive for cloud service providers to let their customers go away: why should they participate to open standards? Consumer's pressure may influence their decision No mature standards for cloud computing (except HTTP) DMTF OVF / CIMI, OGF OCCI, SNIA CDMI,... have not (yet) been adopted by cloud providers Some standards are OK for IaaS but not for other layers (cf. OASIS TOSCA) Meanwhile interoperability and portability can be constructed and maintained by Cloud Service Brokers Gartner: Cloud Interoperability Can be Brokered by Daryl C. Plummer 4

5 RISKS Actually today's cloud computng model is not compliant with the original «utility» model Electricity system or telephone system Public and private clouds ofer their end consumers a "pay as you go" model - a powerful shif for computing, towards a utility model like the electricity system, the telephone system, or more recently the Internet. However, unlike those utilities, clouds cannot yet federate and interoperate. IEEE 2011 Annual SRII Global Conference Interoperability in «silos» Specific ecosystems of Cloud Service Providers and Vendors to address targeted markets, aggregated by specific contracts, patents, IPR, etc. Limited possibilities to interoperate with other silos (except for B2B) Extension of the «vendor lock in» concept 5

6 OPEN CLOUD OCCI is a trademark of the Open Grid Forum 6

7 KEY COMPONENTS CompatibleOne provides an open source cloudware* allowing creation, deployment and management of private, public and hybrid cloud platforms CORDS CompatibleOne Resource Description Schema ACCORDS Advanced Capabilities for CompatibleOne Resources Distribution Services EZVM Virtual Machine Interoperability PaaS4DEV Runtime OSGI UNIDATA Data Interoperability * cloud computing middleware 7

8 ACCORDS V CO ES SL A P MA NIF EST HTTP/REST/OCCI 1 SLA M Arbitrage PLA N PA RSE R CO EES CO OB AS Uni Da ta Pub lish er CO CO RD SS Co S mo ns SER VIC E CO NT RA CT EZ V M Value Added Pa as 4D ev HTTP/REST/OCCI Xaa S Pro cci Pro Act ve Pro cci Op ens tac k Pro cci 8 CO NE TS BR OK ER Integrators PR OC CI Providers Am azo n Pro cci 4 Paa S Pro cci Az ure Pro cci Op en Ne bul a Pro cci

9 DESCRIPTION MODEL Logical View OCCI Open Cloud Computing Interface Entity Core Resourc e Infrastructure Network CORDS CompatibleOne Ressource Description Schema Compute Link Storage Network Configuratio n Mixin StorageLink NetworkLin k Package Infrastructure Image System Provider Monitoring NODE Action Constrain t Manifest User Configuration Requirement Plan Account 9 ProviderTyp e

10 DESCRIPTION MODEL Virtual Instance View OCCI Open Cloud Computing Interface Entity Core Resource Link Mixin CORDS CompatibleOne Ressource Description Schema NODE Manifest Profile Plan 0 to N 1 to N Service Contract Provider Instruction Tarification 10

11 CORDS Version 2 COMPUTE Manifest INFRASTRUCTURE MANIFEST NODE NETWORK Manifest STORAGE IMAGE SYSTEM PACKAGE NODE MANIFEST 11 NODE

12 ACCORDS OpenStack Nova Provisioning User Accords Publisher Accords Instance Action REST OCCI REST OCCI 1 2 Accords Broker 4 Cloud Provider Announcement 0 Cloud Provider Enquiries OpenStack Procci REST OCCI HTTP REST OCCI REST OCCI Service Contracts SNMP 3 5 Accords Procci 12 Cloud Provider Provisioning

13 ACCORDS OpenNebula Provisioning User Accords Publisher Accords Instance Action REST OCCI REST OCCI 1 2 Accords Broker 4 Cloud Provider Announcement 0 Cloud Provider Enquiries OpenNebula Procci REST OCCI HTTP REST OCCI REST OCCI Service Contracts SNMP 3 5 Accords Procci 13 Cloud Provider Provisioning

14 ezvm Goal: Virtual machine interoperability Provides: Virtual machine description using OCCI Package System Image Vm Virtual machine registry Virtual machine storage Virtual machine provider 14

15 ezvm PARSER BROKER Image Preparation Interface Image Product ion Service PROCCI Image Production Interface PROVIDER PROCCI ezvm Image Delivery Interface Ressource Provisioning Interface Provider Platform 15

16 ACCORDS PaaS PUBLISHER PARSER BROKER PaaS PROCCI PROCCI MANIFEST 1 PaaS MANIFEST 2 MANIFEST 3 16

17 PaaS4dev functional architecture 17

18 PaaS4dev technical architecture ACCORDS Procci PaaS4Dev Console JPaaS REST API Applicatio n manager Tenant manag er Environ ment manage r Applicati ons Environm ents Catalog Provi sioni ng Sc ale Up Scal edo wn IaaS mana ger [Siroc co] VM config urator [Chef] Usage records Statistic s Place ment solver Constraints Engine Process Engine IaaS mana ger [EZV M/ Manif est C1] Meteri ng manag er FailO Scali ver ng Rules Engine Tenants Data Acce ss Laye r Statis tics mana ger Logger manag er Rout er man ager [jk API] Contai ner Manag er [JOnA S API] 18 Probe manag er [JASMI Ne API] Monit oring servic e Logs Enabl er APIs [Xaa S]

19 POC XWiki Provide a proof of concept for automatic provisioning Leverage CompatibleOne Platorm and use of its current features. Interoperability between different Providers Image production System configuration XWiki as a use case Deployment of a web application Separated Application Server and Storage Application Configuration 19

20 POC XWiki Declarative definition of reusable (high-level) services Automated image production System components installation and configuration Provider-independent metadata management Service configuration at deployment Composable manifests Building complex system deployments by assembling available service descriptions 20

21 XWiki Use Case Definition of high level services for relational storage Definition composite manifest for the application Image production automation Application configuration and deployment Support for multiple providers Goal: automate the previous POC version and remove dependencies on functionalities available on specific providers. 21

22 Next Steps Integration of Subsequent Components / Modules Monitoring Security Accountancy Intelligent Provisioning Integration of PaaS Services 22

23 Useful Resources CompatibleOne web For the latest components version For packages ready to install package=accords&project=virtualization%3acloud%3acompatibleone Developers Mailing list In Progress CompatibleOne platorm to test your manifests Openstack and Opennebula to connect to your CompatibleOne platorm 23

24 Let's Work Together! Promotng freedom in the cloud Contribute Share Spread the word 24