#rightscaleKey Design Considerations forPrivate and Hybrid CloudsWatch the video of this presentation
#2#rightscaleYour Panel TodayPresenting• Utpal Thakrar, Sr. Product Manager, RightScale• Ryan Geyer, Cloud Solutions Engineer, RightScaleQ&A• Cory Smith, Account Manager, RightScalePlease use the “Questions” windowto ask questions as any time!
#3#rightscaleAgenda• Definitions and terminology• Infrastructure evolution• Why would you build a private cloud?• Use cases + demo• Hardware and software considerations• Best practices for design and implementation• Conclusion/Q&A
#rightscaleTerminology: Quick Recap
#5#rightscaleTerminologyVirtualization• Division of one physical server into multiple isolated virtual environmentsPublic Cloud• Hosted by cloud provider• On-demand, pay-as-you-go, accessible via APIPrivate Cloud• Typically single-tenant• Hosted on-premises or co-lo facilityHybrid Cloud• Spans more than one private or public clouds• Extending the definition to include private virtualized environments
#6#rightscaleInfrastructure EvolutionOld SchoolData CenterVirtualizationEarly daysEarly “Cloudification” Sophistication andSex appeal20th century 2000 2006 Present day
#rightscaleState of the Cloud Report
#8#rightscaleRightScale State of the Cloud Report 2013• 625 respondents from various industry segments• Equal representation from large enterprises and SMBsComplete report available athttp://www.rightscale.com/lp/state-of-the-cloud-report.phpSource: April 2013 RightScale State of the Cloud Report
#rightscaleWhy Do You NeedPrivate or Hybrid Cloud?
#10#rightscaleWhy would you build a private cloud?• Workload and infrastructure interaction• Security / Regulation / Compliance• Latency• User experience• Cost over a longer time horizonAnd of course, agility…
#11#rightscaleBuild with an end in mind
#12#rightscaleWhen would you need a hybrid or multi-cloud?• What if your 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 same organization fordifferent applications, with each app in one cloud
#14#rightscaleUse 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 thepublic cloud until they are end-of-lifed• If an application gains traction, it remains in the public cloudduring its growth phase• When stability of workload is reached, the application istransitioned into the private cloud
#15#rightscaleUse Case: Hybrid Cloud BurstingPRIVATE CLOUD PUBLIC OR PRIVATE CLOUDLOAD BALANCERSAPP SERVERSMASTER DATABASESLAVE DATABASEOBJECT STORAGEAPP SERVERSPUBLICINTERNETCloud Bursting
#16#rightscaleUse Case: HA / DR using Hybrid Cloud (Demo)• 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 tomaster, launching of “standby” servers, and DNS reassignment
#17#rightscaleUse Cases: IT Vending Machine (Demo)• Users select one of several preconfigured tech stacks• Isolated dev/test environments
#18#rightscaleRackConnect, Direct Connect, Hybrid for Metro Area• Rackspace uses RackConnect between RAX dedicated hostingprivate cloud and RAX public cloud• Amazon uses Direct Connect between private clouds and AWSAZs• Both offer low-latency, secure connectivity• The catch is – your private cloud needs to be “near” the publiccloud
#rightscaleHardware and SoftwareConsiderations
#20#rightscaleHardware 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 networkhardware devices (load balancers in particular)• Storage• Cost vs. Performance (commodity? SSD?, etc.)
#21#rightscaleSoftware Considerations• Cloud Infrastructure Software• CloudStack, OpenStack (Rackspace Private) etc.• Open source with commercial support• Access to resources• Web interface• API• Documentation• Industry talent pool• Hypervisor• Baremetal
#22#rightscaleFinding a home for your cloudVarious options, although, trade-offs with each decision• On-premises• You are responsible for facility, power, network, operations• You get full access, physical security, secure access for your internalusers• Co-location facility• Co-lo provider takes the headache of operations and physical aspects• You would need to have managed service to go with co-lo, to make itpractical• Hosting facility adjacent to a public cloud
#24#rightscaleImplementation Process• Design• Know the workload / performance requirements• Keep HA in mind• Capacity Planning• Monitor and Automate• Access Control• Manage• Test (and test again)
#25#rightscaleDesign: High-availability optionsNo HA or Redundancy HA ConfigurationSimple Complex
#26#rightscaleOpenStack Infrastructure HA (example)Several 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.
#27#rightscaleDesign: Network Options• OpenStack• FlatDHCP – Typical for single tenant• VLAN manager – Typical for multi-tenant env• CloudStack• Basic Zone – Typical for single tenant• Advanced Zone – Typical for multi-tenant env
#28#rightscaleDesign: Capacity Planning – it’s simple!• Don’t have a blank check backed by limitless funds or perfectlyclear expectations from your user that never change? Well, youneed capacity planning!• Capacity planning is also budget planning and is directly relatedto SLA you offer• Know your workload, determine the difference between spikeand trend• Monitor, tweak capacity, rinse, repeat …• Check out http://www.planforcloud.com
#29#rightscaleMonitor and Automate• Understand your workload• Number of VMs requested• Allocated CPU, Memory, Disk capacity• Actual utilization of resources• Monitor using tools like Gaglia + Nagios• Hypervisor hosts• VM containers• Resources consumed by the app• Automate• Chef, Puppet, Fuel etc..
#30#rightscaleAccess Control and Tenant Management• Each cloud platform is slightly different but follows similarprinciples• Most clouds have option of integrating with existingauthentication and authorization system
#31#rightscaleSeparate Management Layer from Infrastructure• Keep the keys to the car outside the car
#32#rightscaleSeparate 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
#33#rightscaleAlways keep the application in mind!
#34#rightscaleSummary/Conclusions• Private (and therefore hybrid) clouds were originally thought ofas an academic exercise or science project• Recent advances (particularly in cloud infrastructure software)have shown private and hybrid clouds to be viable IT deliverymodels• 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) email@example.com