Avoiding Cloud Lock-in     Sebastien GoasguenGeek Speak Local October 23rd        Paris, France
Disclaimer• I work for Citrix as a Cloud Computing Evangelist, focused on Apache CloudStack• Quite a few slides are from M...
User concerns about moving to the                                    Source: http://blog.rightscale.com/2009/02/19/the-ski...
Outline•Cloud Computing Definition•Open Source, Open Standards Open APIs•Cloud Standards•Best practices for avoid cloud lo...
Google trends               Start of “Clouds”• Cloud computing trending down, while “Big Data”  is booming. Virtualization...
BigData on the Trigger• Cloud Computing  Going down to  the “through of  Disillusionment”• “Big Data” on the  Technology  ...
NIST Definition of Cloud• "cloud computing is a model for enabling  ubiquitous, convenient, on-demand network  access to a...
NIST Service/Deployment Models• Service Models:  • IaaS (e.g EC2, rackspace)  • PaaS (e.g GAE, Azure)  • SaaS (e.g Gapps)•...
Deployment Models               10
NIST Key Characteristics of Cloud• Elasticity   • Expands and Shrinks as needed   • E.g Elastic Load Balancing, Elastic Ma...
•What ? Lock-In – Costs to switch cloud providers/vendors are prohibitive•How ? • Ability to build own private clouds (*aa...
13Even vendors know that party is               CCA –NC : -Microsoft http://www.microsoft.com/global/en-us/news/publishing...
Outline•Cloud Computing Ontology•Open Source, Open Standards Open APIs•Cloud Standards•Best practices for avoid cloud lock...
Open source   •Consume on your terms, not    your vendors   •Transparency into features,    code, and process   •Vibrant u...
Apache Process•100% community driven•New ideas, decisions only taken on mailing lists.•Votes taken by community•Project le...
Apache Processes
Open data•Utilize open formats• Google’s Data Liberation Front - http://www.dataliberation.org/•Understand cost to (re)mov...
Open APIs•Every cloud has an API but is it copyrightable? -- Oracle says so, Google says No!•Defacto standard for IaaS is ...
Why now ?Evolution of the Mashup Revolution   thanks to an API “explosion”
Software as a Service
API issues
CloudStack very extensive API               Open API, but really its               own               Mapping from EC2 API ...
API adapters to  the rescue
Outline•Cloud Computing Ontology•Open Source, Open Standards Open APIs•Cloud Standards•Best practices for avoid cloud lock...
There’s nothingstandard, about cloudstandards.     Mark Hinkle –a.k.a The Boss -                                     26
DMTF – OVF and CIMI      • OVF first official Cloud Standard      • Open Virtualization Appliance (OVA)        single file...
OASIS TOSCA • Topology and Orchestration Specification   for Cloud Applications (TOSCA) • Portable deployment to any compl...
Storage Networking Industry     Association (SNIA)            • Cloud Data Management              Interface (CDMI)       ...
Official Cloud Standards• OVF (packaging of virtual appliances)  now an ANSI standard. Developed by  DMTF• OCCI (~EC2 spec...
OCCI
OCCI implementation
How About the IETF ?• IETF survey to identify “work items” in  cloud standards (July 2012):  • “This draft presents a surv...
Related standards• HTTP(s)• JSON, It is based on a subset of the  JavaScript Programming Language,  Standard ECMA-262 3rd ...
Open “Alliances”• Not standard organizations• Open Networking Foundation  (Software Defined Networking,  maintains Openflo...
Networking standards: OpenFlow                         •Leading SDN protocol                         •Decouples control an...
Outline•Cloud Computing Ontology•Open Source, Open Standards Open APIs•Cloud Standards•Best practices for avoiding cloud l...
We have a long way to go to    avoid cloud lock-in            • Nascent industry            • Lack of standards           ...
Key tenants for avoiding cloud           lock-in            • Easily replicable infrastructure            • Avoid propriet...
Avoid SaaS Lock-In•Know the consequences, SaaS has the most potential for lock-in•Unique apps will lock you in, no proxy f...
Avoiding PaaS lock-in•Make sure programming models based on open standards•Are there a variety of tools—IDEs, analytics, m...
Avoid IaaS Lock-In• Use API abstractions when possible• Consider virtualization choices carefully• Understand network cons...
Conclusions•Every type of infrastructure migration has some cost (time, capital, usage)•Interoperability/portability stand...
Info@sebgoasebgoa on IRC freenodesebastien.goasguen@citrix.comhttp://slideshare.net/sebastiengoasguen
Avoiding cloud lock-in
Avoiding cloud lock-in
Upcoming SlideShare
Loading in …5
×

Avoiding cloud lock-in

1,370 views

Published on

  • Be the first to comment

Avoiding cloud lock-in

  1. 1. Avoiding Cloud Lock-in Sebastien GoasguenGeek Speak Local October 23rd Paris, France
  2. 2. Disclaimer• I work for Citrix as a Cloud Computing Evangelist, focused on Apache CloudStack• Quite a few slides are from Mark Hinkle• The Slides are in English because I would have made too many grammatical mistakes in French  That’s what 14 years in the US do to you.
  3. 3. User concerns about moving to the Source: http://blog.rightscale.com/2009/02/19/the-skinny-on-cloud-lock-in/ 3 cloud (from Rightscale, 2009)
  4. 4. Outline•Cloud Computing Definition•Open Source, Open Standards Open APIs•Cloud Standards•Best practices for avoid cloud lock-in 4
  5. 5. Google trends Start of “Clouds”• Cloud computing trending down, while “Big Data” is booming. Virtualization remains “constant”.
  6. 6. BigData on the Trigger• Cloud Computing Going down to the “through of Disillusionment”• “Big Data” on the Technology Trigger
  7. 7. NIST Definition of Cloud• "cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.“ – NIST
  8. 8. NIST Service/Deployment Models• Service Models: • IaaS (e.g EC2, rackspace) • PaaS (e.g GAE, Azure) • SaaS (e.g Gapps)• Deployment model: • Private cloud • Public cloud • Hybrid cloud (Private than can use Public)
  9. 9. Deployment Models 10
  10. 10. NIST Key Characteristics of Cloud• Elasticity • Expands and Shrinks as needed • E.g Elastic Load Balancing, Elastic Map Reduce• Measured Service • Utility Pricing. You pay for what you use • E.g $0.08 for one hour of small instance• On-demand • You get it when you ask for it • E.g One api call and you get your machine, ~no queue
  11. 11. •What ? Lock-In – Costs to switch cloud providers/vendors are prohibitive•How ? • Ability to build own private clouds (*aaS) with Open Source Software • Ability to import/export data on-demand in non- proprietary format • Availability of multiple providers with interoperable interfaces • Open Source, Open Data, Open APIs 12
  12. 12. 13Even vendors know that party is CCA –NC : -Microsoft http://www.microsoft.com/global/en-us/news/publishingimages/images/features/2010/02-01Interop_lg_Page.jpgCC-byA ending…
  13. 13. Outline•Cloud Computing Ontology•Open Source, Open Standards Open APIs•Cloud Standards•Best practices for avoid cloud lock-in 14
  14. 14. Open source •Consume on your terms, not your vendors •Transparency into features, code, and process •Vibrant user communities •Multi-vendor Ecosystems
  15. 15. Apache Process•100% community driven•New ideas, decisions only taken on mailing lists.•Votes taken by community•Project led by Project Management Committee(PMC): •http://www.apache.org/dev/pmc.html •http://incubator.apache.org/guides/committer.html•Non committers get invited as committers: •http://community.apache.org/newcommitter.html
  16. 16. Apache Processes
  17. 17. Open data•Utilize open formats• Google’s Data Liberation Front - http://www.dataliberation.org/•Understand cost to (re)move data•Test network between providers (transfer rates) • Or do you really want to Fedex your drives ?•Look for Multi-Vendor Ecosystems 18
  18. 18. Open APIs•Every cloud has an API but is it copyrightable? -- Oracle says so, Google says No!•Defacto standard for IaaS is the Amazon API•Cloud Abstractions can provide a “common API”•Abstractions keep your options open 19
  19. 19. Why now ?Evolution of the Mashup Revolution thanks to an API “explosion”
  20. 20. Software as a Service
  21. 21. API issues
  22. 22. CloudStack very extensive API Open API, but really its own Mapping from EC2 API to CloudStack API (but…not complete) Similar situation with Opennebula and Openstack
  23. 23. API adapters to the rescue
  24. 24. Outline•Cloud Computing Ontology•Open Source, Open Standards Open APIs•Cloud Standards•Best practices for avoid cloud lock-in 25
  25. 25. There’s nothingstandard, about cloudstandards. Mark Hinkle –a.k.a The Boss - 26
  26. 26. DMTF – OVF and CIMI • OVF first official Cloud Standard • Open Virtualization Appliance (OVA) single file alternative, Virtual Box appliance. • CIMI (Standard for Infrastructure provisioning and configuration) • Orange Labs has a CIMI implementation called SIROCCO as well as a native CIMI API in Java. 27
  27. 27. OASIS TOSCA • Topology and Orchestration Specification for Cloud Applications (TOSCA) • Portable deployment to any compliant cloud • Smoother migration of existing applications to the cloud • Flexible bursting (consumer choice) • Dynamic, multi-cloud provider applications
  28. 28. Storage Networking Industry Association (SNIA) • Cloud Data Management Interface (CDMI) • Tag your data with special meta data • Indicates to cloud storage provider (backup, archive, encryption, etc.) 29
  29. 29. Official Cloud Standards• OVF (packaging of virtual appliances) now an ANSI standard. Developed by DMTF• OCCI (~EC2 spec), from OGF• Definition of Cloud from NIST now accepted widely• cloud-standards.org brings together main SDOs.
  30. 30. OCCI
  31. 31. OCCI implementation
  32. 32. How About the IETF ?• IETF survey to identify “work items” in cloud standards (July 2012): • “This draft presents a survey of the industry work items related to cloud activities. By conducting a comprehensive survey, work items in cloud standards can be determined. This will allow us to determine the IETF work that would be required to address the work items. Once these IETF work have been completed, seamless interoperability of cloud services can be realized.”
  33. 33. Related standards• HTTP(s)• JSON, It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999• OAuth and OPenID (for authentication and authorization)• REST is not a standard, it’s an architectural sytle that gives guidelines on managing web resources
  34. 34. Open “Alliances”• Not standard organizations• Open Networking Foundation (Software Defined Networking, maintains Openflow specification)• Open Compute project (Former Facebook project, shares designs/guidelines for efficient data center)• Open Data Center Alliance (User advocate)
  35. 35. Networking standards: OpenFlow •Leading SDN protocol •Decouples control and data plane by giving a controller the ability to install flow rules on switches. •Hardware or software •Google achieved 95% switches can useutilization of WAN OpenFlowbackbone by using SDN •Spec driven by ONF
  36. 36. Outline•Cloud Computing Ontology•Open Source, Open Standards Open APIs•Cloud Standards•Best practices for avoiding cloud lock-in 38
  37. 37. We have a long way to go to avoid cloud lock-in • Nascent industry • Lack of standards • Evolving technologies • Follow best practices 39
  38. 38. Key tenants for avoiding cloud lock-in • Easily replicable infrastructure • Avoid proprietary cloud features when possible • Abstract APIs as much as practical • Look for multiple vendor ecosystems • Use open source software
  39. 39. Avoid SaaS Lock-In•Know the consequences, SaaS has the most potential for lock-in•Unique apps will lock you in, no proxy for those services•Data should be free, export and back-up regularly•Test to see if that data is transferrable to new services 41
  40. 40. Avoiding PaaS lock-in•Make sure programming models based on open standards•Are there a variety of tools—IDEs, analytics, management, etc.—available•Do multiple vendors provide support and/or equivalent hosted services•Large, capable talent pool for the domain technology42
  41. 41. Avoid IaaS Lock-In• Use API abstractions when possible• Consider virtualization choices carefully• Understand network considerations to migrate between clouds• Include other cloud providers in your cloud design plans 43
  42. 42. Conclusions•Every type of infrastructure migration has some cost (time, capital, usage)•Interoperability/portability standards are evolving and market-driven•Good planning can mitigate lock-in risks•Look at automation practices to keep pace with your cloud. Look into Agile culture to build able to build and deploy anywhere, anytime
  43. 43. Info@sebgoasebgoa on IRC freenodesebastien.goasguen@citrix.comhttp://slideshare.net/sebastiengoasguen

×