Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Key Design Considerations Private and Hybrid Clouds - RightScale Compute 2013

1,697 views

Published on

Speaker: Utpal Thakrar - Product Manager, RightScale

Interest in private and hybrid clouds is exploding, and implementations are becoming real. In this talk, RightScale’s product manager in charge of private clouds will cover key considerations for designing and building private and hybrid clouds. You will learn how to tie strategy to decisions covering use cases, workloads, hardware, software, and implementation.

Published in: Technology, Business
  • Be the first to comment

Key Design Considerations Private and Hybrid Clouds - RightScale Compute 2013

  1. 1. april25-26sanfranciscocloud success starts hereKey Design ConsiderationsPrivate and Hybrid CloudUtpal Thakrar, Sr. Product Manager
  2. 2. #2#2#RightscaleComputeGot Virtualization? That ain’t cloud
  3. 3. #3#3#RightscaleComputeVirtualization makes cloud happenVirtualizationCloud Computing
  4. 4. #4#4#RightscaleComputePublic Cloud• Hosted at a service provider• Supports multiple customers• Uses shared infrastructure• Supports connectivity over public internet• Typical consumption model ispay as you go, on-demand computing
  5. 5. #5#5#RightscaleComputePrivate Cloud – Have it your way!• Hosted on-premise or at a co-loco facility• Typically Single tenant• Suited for information requiring high levelof security• Accessed via API endpoint
  6. 6. #6#6#RightscaleComputeMulti-Cloud and Hybrid Cloud• Spans more than one private or publicclouds• Extending the definition to includeprivate virtualized environments
  7. 7. #7#7#RightscaleComputeInfrastructure EvolutionOld SchoolData CenterVirtualizationEarly daysEarly “Cloudification” Sophistication andSex appeal20th century 2000 2006 Present day
  8. 8. #8#8#RightscaleComputeKey to cloud adoption
  9. 9. #9#9#RightscaleComputeBuild with an end in mind
  10. 10. #10#10#RightscaleComputeBuild with an end in mind – Agility, agility, agility
  11. 11. #11#11#RightscaleComputeWhy would you build a private cloud?• Workload and Infrastructure Interaction• Security / Regulation / Compliance• Latency• User Experience• Cost
  12. 12. #12#12#RightscaleComputeWhen would I need a Hybrid Cloud or Multi-cloud?• What if application outgrows the private cloud?• Common desire is for “cloud-bursting”• Regulation / Compliance for parts of the application• Most common – multiple clouds used by different parts of the sameorganization for different applications, with each app in one cloud
  13. 13. #13#13#RightscaleComputeUse case - Hybrid Cloud BurstingPRIVATE CLOUD PUBLIC OR PRIVATE CLOUDLOAD BALANCERSAPP SERVERSMASTER DATABASESLAVE DATABASEOBJECT STORAGEAPP SERVERSPUBLICINTERNETCloud Bursting
  14. 14. #14#14#RightscaleComputeUse case – Untested workloads• Scalable Applications with Uncertain Demand• Public cloud used as “proving ground” for new applications• If applications fail, they are allowed to run their course in the public cloud untilthey are end-of-lifed• If an application gains traction, it remains in the public cloud during its growthphase• When stability of workload is reached, the application is transitioned into theprivate cloud
  15. 15. #15#15#RightscaleComputeUse Case – HA / DR using Hybrid Cloud• Disaster Recovery (DR)• Production environment in one cloud• DR environment in a second cloud• Most common configuration is the “Warm DR” scenario• Replicating slave in a second cloud• All other servers in non-operational state• Failure of production environment requires promotion of slave to master, launching of “standby”servers, and DNS reassignment
  16. 16. #16#16#RightscaleComputeRackConnect, Direct Connect, Hybrid for Metro Area• Disaster Recovery (DR)• Production environment in one cloud• DR environment in a second cloud• Most common configuration is the “Warm DR” scenario• Replicating slave in a second cloud• All other servers in non-operational state• Failure of production environment requires promotion of slave to master, launching of “standby”servers, and DNS reassignment
  17. 17. Copyright © 2013 Samsung SDS Co., Ltd. All rights reserved17FirewallIPSVPN GatewayCF RouterPublic ASN: XXXXPrivate: 10.x.x.x/24Public: *.*.*.0/24Private: 10.x.x.x/24Public: *.*.*.0/24VM VMSPCSVirtual GWVM10.x.x.x/24VMInternetGWEIP: e.x.y.bVMEIP: e.x.y.aVMObjectStorageVPCComputePublic CloudInternet trafficBetween SPCS and Public Cloud using publicIPBetween SPCS and Public Cloud using privateIPInternet traffic to SPCS and Public Cloud using public IPHybrid Cloud Network ArchitecturePrivate Network
  18. 18. #18#18#RightscaleComputeHardware Considerations• Compute• Commodity• Allows for easy addition of capacity• Easy swap-out of failed components• High end/specialized• May be required for intended workloads• Limits available options• Increases costs• Complicates maintenance• Networking• Driven by topology, latency demands, and price• Some cloud infrastructure software offerings have support for network hardwaredevices (load balancers in particular)• Storage• Cost vs. Performance (commodity? SSD?, etc.)
  19. 19. #19#19#RightscaleComputeSoftware Considerations• Cloud Infrastructure Software• CloudStack, OpenStack (Rackspace Private) etc.• Open source with commercial support• Dictates/influences other decisions regarding cloudimplementation• Access to resources• Web interface• API• Documentation• Industry talent pool• Hypervisor
  20. 20. #20#20#RightscaleComputeFinding a home• On-premise• Co-location facility• Hosting facility adjacent to a public cloud
  21. 21. #21#21#RightscaleComputeImplementation process• Design• Automate• Monitor• Test (and test again)
  22. 22. #22#22#RightscaleComputePrivate Cloud Infrastructure HASeveral single points of failure in OpenStack deployment• OpenStack API services• MySQL• RabbitMQSolved in various ways• Pacemaker cluster management• Keepalived (e.g: RAX Private Cloud)• MySQL (Galera), RabbitMQ (active-active mirrored queues)Eliminate SPoFs as best as you can.
  23. 23. #23#23#RightscaleComputeDesign Considerations/OptionsSimple ConfigurationNo HA or RedundancyHA Configuration
  24. 24. #24#24#RightscaleComputeNetwork options• OpenStack• FlatDHCP – typical for single tenant• VLAN manager – typical for multi-tenant env• CloudStack• Basic Zone• Advanced Zone
  25. 25. #25#25#RightscaleComputeCapacity planning – it’s simple!• A blank check backed by limitless funds• Unlimited time• A well-organized team of geniuses• Perfectly clear expectations that never change (up front & inwriting)Don’t have all that? Then we have to worry about capacity planning
  26. 26. #26#26#RightscaleComputeMonitor and Automate• Understand your workload• Monitor using tools like Gaglia + Nagios• Hypervisor hosts• VM containers• Resources consumed by the app• Automate• Chef, Puppet, Fuel etc..
  27. 27. #27#27#RightscaleComputeAccess Control and Tenant management• Each cloud platform is slightly different but follows similarprinciples
  28. 28. #28#28#RightscaleComputeSeparate Management layer from Infrastructure• Keep the keys to the car outside the car
  29. 29. #29#29#RightscaleComputeSeparate Management layer from Infrastructure• Connect your private / hybrid cloud to RightScale• Abstracts underlying details of the cloud infrastructure offerings• Presents consistent interface to the available resources regardless of theunderlying infrastructure provider• Provides a cloud-portable solution• Provides orchestration tools for provisioning and management
  30. 30. #30#30#RightscaleComputeAlways keep the application in mind!
  31. 31. #31#31#RightscaleComputeRightScale ServerTemplates™• Reproducible: Predictabledeployment• Dynamic: Configurationfrom scripts at boot time• Multi-cloud: Cloud agnosticand portable• Modular: Role and behaviorabstracted from cloudinfrastructureHow RightScale makes it possible
  32. 32. #32#32#RightscaleComputemy networkmy serversmy storageCONFIGURATION AUTOMATION GOVERNANCEPrivate CloudsPublic Clouds®Agile IT Multi-Cloud Full Control
  33. 33. #33#33#RightscaleComputeSummary/Conclusions• Private (and therefore hybrid) clouds were originally thought of as anacademic exercise or science project• Recent advances (particularly in cloud infrastructure software) haveshown private and hybrid clouds to be viable IT delivery models• Many considerations come into play• Design• Hardware• Software• Implementation Details• No “one size fits all”• Do your research. Find the right fit.Contact RightScale(866) 720-0208sales@rightscale.comwww.rightscale.com
  34. 34. april25-26sanfranciscocloud success starts hereQuestions?

×