How to Think Multi-Cloud
Download as PPTX, PDF1 like1,014 views
RightScale Webinar: December 8, 2010 – In this Webinar, we discuss the benefits and pain points of multi-cloud as well as key considerations to have in mind when going multi-cloud. We present examples of multi-cloud scenarios and describe the design principles to consider when architecting deployments that must span and migrate across different clouds and providers.
Ad
More Related Content
What's hot (19)
Similar to How to Think Multi-Cloud (20)
Ad
More from RightScale (20)
Ad
Recently uploaded (20)
How to Think Multi-Cloud
- 1. How to Think Multi-CloudDecember 8, 2010
- 2. Your Panel TodayPresenting:Michael Crandell, CEO Twitter: @michaelcrandell
- 3. Josep M. Blanquer, Sr. Systems ArchitectQ&A:John Newton, Account ManagerPlease use the questions window to ask questions anytime!
- 4. AgendaWhat do we mean by a cloud?What is multi-cloud and what’s different?How does RightScale help?Servers and ServerArraysMulti-Cloud Server TemplatesMulti-Cloud ImagesData locality and mobilityA multi-cloud example and demoConclusions / Q&APlease use the questions window to ask questions anytime!
- 5. What do we mean by cloud?A cloud is a physical data center entity behind an API endpointWhat do you mean by that?Amazon Web Services is not a cloudEC2 is not a cloudEucalyptus, Cloud.com are not a cloudEC2 East, EC2 AsiaPacific, my private cloud… are cloudsAn availability zone is not a cloud, it’s part of oneThink of a cloud as a “resource pool” accessed via API
- 6. Where is my cloud in the wild?
- 7. Where is my cloud in the wild?There might be just a few big cloud players…but there will be a myriad of clouds
- 8. Where are my clouds in RightScale?Dashboard example:AWS, Rackspace and several private clouds in one accountA cloud is first registered with RightScaleOnce a cloud is registered, a user can start using it
- 9. What does multi-cloud mean?It’s about deploying your application:Across different cloudsSpanning cloud providers (most likely with different API’s)Utilizing private and public onesIt’s about evolving your application to:Incorporate new clouds as they appearOr quickly moving servers to utilize leftover or new cloud capacityAll seamlessly:Without having to learn a new interface every timeWorking together in an integrated mannerIt’s about using multiple cloud providers, not choosing oneCurrent focus: cloud portability
- 10. Multi-cloud: benefitsRedundancyfor disaster recovery and business continuityGeo-location for latency and/or policy complianceLeverage unique cloud-specific services when neededLeverage public cloud cost benefits (cheaper and/or infinite)Leverage existing data centers: private cloudMove services with bursty, unpredictable apps to public cloudPrivate cloud for apps with regulatory compliance reqsSupport varying levels of security concerns
- 11. Multi-cloud: pain pointsAPIs differDifferent sets of resourcesDifferent formats and encodingsSeveral simultaneous versions for a single cloudAbstractions differNetwork architectures differ: VLANs, security groups, NAT, IPs, ACLs, …Storage architectures differ: local/attachable disks, backup, snapshots, …Hypervisors and machine images differSupported features differ…cost models, billing, reporting…etcThey are truly different applications, with different semantics
- 12. How to think multi-cloud? “Akin to designing your application using several programming languages”Deploy using cloud-specifics, design using generic conceptsHave tools that translate your concepts to cloud-specific ones.Design for geographic dispersionThink of how to share data acrossKnow if you’re designing for HA or simply for portability
- 13. How does RightScale help?Unified Multi-Cloud UI and new API (in progress)Multi-Cloud Servers/ArraysMulti-Cloud Server TemplatesMulti-Cloud ImagesOthers in the pipelineServerTemplateImageServer1:NI1:1IIIIrunnable abstractionsoftware configruntime configcloud resources
- 14. (Multi-Cloud) Servers and ArraysServers and Arrays are runtime abstractionsAll Servers look and smell similar, regardless of cloud: Can be started, stopped or run operational actions in the same wayShow monitoring data, and can configure alerts in the same wayThey coexist in mixed deployment listings, same filters, columns…They can support abstractions that some clouds don’t support…Can be very different beasts, but they are seamlessly integratedServerTemplateServer1:NI1:1IIIIMCIrunnable abstractionsoftware configruntime configcloud resources
- 15. Parenthesis: What are ServerTemplates?Configuring serversthrough bundling Images:Configuring serverswith ServerTemplates:Custom MySQL 5.0.24 (CentOS 5.2)Custom MySQL 5.0.24 (CentOS 5.4)A set of configuration directives that will install and configure software on top of the base imageMySQL 5.0.36 (CentOS 5.4)MySQL 5.0.36 (Ubuntu 8.10)MySQL 5.0.36 (Ubuntu 8.10) 64bitFrontend Apache 1.3 (Ubuntu 8.10)Frontend Apache 2.0 (Ubuntu 9.10) - patchedCMS v1.0 (CentOS 5.4)CMS v1.1 (CentOS 5.4)My ASP appserver (windows 2008)My ASP.net (windows 2008) – security update 1Base ImageVery few and basicMy ASP.net (windows 2008) – security update 8SharePoint v4 (windows 2003) – 32bitSharePoint v4 (windows 2003) –64bitWin 2003CentOS 5.2Ubuntu 8.10SharePoint v4.5 (windows 2003) –64bitCentOS 5.4Win 2007Ubuntu 9.10…
- 16. Parenthesis: What are ServerTemplates?Anatomy of aServer TemplateExample Server Template:MySQL 5.0RightScript/Recipe 6Initialize slave……operationsoperationsRightScript/Recipe 6Perform backupRightScript/Recipe NStart all services……RightScript/Recipe 5Setup DNS and IPsRightScript/Recipe 4Restore last backupboot sequenceboot sequenceRightScript/Recipe 3Configure/tune MySQLRightScript/Recipe 2Install MySQL ServerRightScript/Recipe 1Install monitoringBase ImageRight Image
- 17. (Multi-Cloud) Server TemplatesThey are software configuration abstractionsBridge the gap between the starting point (a base Image) and a fully configured machineAbstract Cloud and Operating System differencesGather a set of user defined, high-level Input valuesCan partially help in the sharing of dataAre versionable and publishableAllow configuring servers always in the same or equivalent wayServerTemplateServer1:NI1:1IIIIMCIrunnable abstractionsoftware configruntime configcloud resources
- 18. Multi-Cloud Images (MCI)MCI’s abstract a set of requirements in a cloud imageExample: A CentOS 5.4 ImageProvide an equivalency map of base images across cloudsCentOS 5.4 Image is ‘ami-feff’ in EC2 East, and ‘1234’ in RackspaceThey are versionable and publishableAre associated to ServerTemplatesServerTemplateServer1:NI1:1IIIIMCIrunnable abstractionsoftware configruntime configcloud resources
- 19. Multi-Cloud Images: RightImagesRightScale maintains such maps (MCI’s) for all public clouds
- 20. Data locality and mobilityA topic a bit further down the roadA big hurdle to overcome: clouds are isolatedHow can our app share data across its clouds then?External globally accessible services.Transferring data snapshots across. Maintaining online data replication across clouds. Using an inherently replicated service, that is distributed.Keeping track of your moving dataWhere’s the latest? What’s my lineage? how do I manage my datasets?...We’re thinking about useful multi-cloud abstractions to help with all that
- 21. Multi-Cloud Use Case: portability Test & devUS customers(production)EU customers(production)…US customers(beta)
- 22. Multi-Cloud Use Case: portability Scalable, powerfuland redundantAll-in-OnesTest & devUS customers(production)EU customers(production)…PHPMySQLLoad balancerScriptsand recipesUS customers(beta)PHPFront-EndRails All-in-OnePHPApp ServerMySQLTemplatesCentOS 5.4Multi-CloudImageLess powerand redundancyServers
- 23. Multi-Cloud Use Case: DemoLive Demo
- 24. Thinking multi-cloud: summaryWork with generic abstractions (deploy using cloud-specifics)Take advantage of each specific cloud’s strengthsAvoid lock in.Use or build generic templates:support multiple OSes, and cloud types (not just clouds)Keep a good and clean mapping of Images Maintain just a few and use them across your server templatesKnow your data:Where is it, and what access patterns you’re usingKeep track of where it is, and how it moves.Start with portability, then move to HA-distributed setupsThink different, again!
- 25. Q&A / Getting StartedHave a project, but need some help?Contact us: [email protected] or (866) 720-0208Ready to get started? Sign up for our Free Edition:www.RightScale.com/FreeCall us for a VIP trial of our paid editionsNeed to learn more?TCO calculator:www.RightScale.com/tco-calculator TCO white paper: www.RightScale.com/tco Webinar archive: www.RightScale.com/webinars White papers: www.RightScale.com/whitepapers
- 26. Thank You!
- 27. Using these abstractions: ServerA Server has a ServerTemplateUsing the abstractions: ServerTemplateA ServerTemplate has a list of suportedMCIsUsing these abstractions: MCI’sEach MCI will have mappings to several clouds
Editor's Notes
- #4: Betsy, transition to Ed
- #6: So here’s a graphical representation of existing clouds
- #7: So here’s a graphical representation of existing clouds
- #9: So…this sounds like a pretty onerous goal…quite a challenging…so how do we approach such a thing? What is different from working in single-cloud mode?
- #12: The punchline here is that one needs to step back, and look at the challenges a bit like an integration problem. That is, one needs to work with “portable abstractions” and be able to integrate them across.I think it is very similar to what one would do in building an application or service, consisting of several sub-applications written in different languages.So let me share some considerations to be had in mind when going multi-cloud [POINTS]So it is a fairly different way to think about stuff…it’s all about higher-level abstractions.But not all is lost, RightScale helps with these a lot….let me tell you how…
- #13: RightScale already provides several abstractions that are cloud-agnostic. In fact you’re already using probably all of them (despite you might only be deployed in 1 cloud)..We have the concept of a server (something that can be launched/running on any cloud)The concept of a ServerTemplate, which specifies the configuration we want on a serverAnd the concept of an MCI which specifies which image configuration we want (lower-level stuff)And all these things are RS concepts…the cloud is not really involved in all this…
- #20: Right not we focus on the ability to migrate applications…the next steps will be to run concurrentlyWE use some of these techniques…but are not packaged …let me finish with a multi-cloud deployment use case that can be realized today. We and others are using. Note it’s not about the more future looking scenario of having you production app runnig simultaneously in multiple clouds….it’s about being able to migration applications/deployments from cloud to cloud, much like in a cookie cutter type of way…