Key Design Considerations Private and Hybrid Clouds - RightScale Compute 2013
 

Key Design Considerations Private and Hybrid Clouds - RightScale Compute 2013

on

  • 1,015 views

Speaker: Utpal Thakrar - Product Manager, RightScale ...

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.

Statistics

Views

Total Views
1,015
Views on SlideShare
1,015
Embed Views
0

Actions

Likes
0
Downloads
19
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Good morning, folks. Welcome again to Rightscale compute.. Hope u are having a good time so far..I am utpalthakrar, product manager for cloud integration.. One of my areas of focus has been around private and hybrid cloud..Today we will talk about, u guessed it, private and hybrid clouds..
  • Virtualization (server)Division of one physical server into multiple isolated virtual environmentsPrivate CloudA collection of compute, storage, and network resources for a single tenant that are accessed programmatically via an API endpoint.Public CloudA similar set of resources that is multi-tenant and is provided by a cloud vendor with access via an API endpoint.Multi-CloudAn environment that spans two or more separate clouds, be they both public, both private, or one (or more) of each.Hybrid CloudAn environment that spans one or more public clouds as well as one or more private clouds.
  • Virtualization (server)Division of one physical server into multiple isolated virtual environmentsPrivate CloudA collection of compute, storage, and network resources for a single tenant that are accessed programmatically via an API endpoint.Public CloudA similar set of resources that is multi-tenant and is provided by a cloud vendor with access via an API endpoint.Multi-CloudAn environment that spans two or more separate clouds, be they both public, both private, or one (or more) of each.Hybrid CloudAn environment that spans one or more public clouds as well as one or more private clouds.
  • Old school DatacentersRacks of physical nodes, one application per nodeIt’s all we knew, it worked, and it was fine.Virtualization – The Early YearsCapability of a node outgrew the needs of any single applicationLots of idle resources on each nodeVirtualization provided the ability to have a many-to-one (servers per node) relationshipThis was betterCloudification (Virtualization grows up)Automated provisioning and management via an API appearsThis is much, much better
  • Workload and Infrastructure InteractionApplications have different resource needsChoose the right fit for your application and your infrastructureSecurityData may be contained within the private cloud, thus allowing for stricter security complianceLatencyConsumers of the private cloud resources are generally “closer” to the private cloud, which reduces latencyUser ExperienceRelated to latency, end user experience is enhanced due to proximity to resources.CostOPEX is generally reduced. (CAPEX is another story )
  • When private cloud resources are exhausted, a server tier expands into the public cloud to tap into the “infinite” resourcesConsiderations:Security – public Internet is traversedLatency – traversal of public Internet involves the Great UnknownCost – bandwidth charges for public Internet traversalComplexity – setting up a secure environment is not a trivial taskWe will explore use-cases for hybrid cloud
  • Considerations:Security – public Internet is traversedLatency – traversal of public Internet involves the Great UnknownCost – bandwidth charges for public Internet traversalComplexity – setting up a secure environment is not a trivial task
  • Rackspace has developed a hybrid cloud solution called RackConnectTM, which inte- grates dedicated hosting or private cloud infrastructure with the Rackspace Cloud. This solution has proven to be a significant benefit for customers who want to leverage public cloud resources as a portion of their hosted infrastructure. Customers have lever- aged this solution to enable rapid scale up of applications for things like e-commerce solutions, marketing campaigns, Software as a Service (SaaS) offerings, rich media applications such as games, and social media apps. As a colocated hybrid cloud, Rack- Connect offers low latency, high bandwidth connections, allowing very creative useof infrastructure for workloads such as batch video transcoding applications, desktop as a service, and more. In addition, full integration and automation have simplified the provisioning and management of this hybrid infrastructure, and enhanced the security of a RackConnect customer’s cloud deployment, by managing network access holisti- cally and programmatically, with an easy to use Graphical User Interface. Hybrid clouds have become a highly demanded solution for our customers, from SMBs and Enter- prises alike.
  • Various open source / commercially supported cloud orchestration platforms available.OpenStack and CloudStack are the two leading platforms we recommend.They both have flexible options, typically support various hypervisors
  • Hardware ProcurementPre-existing or new?Pre-existing limits ability to tailor infrastructure to workloadsCloud Infrastructure SoftwareThis decision will dictate/limit many future decisionsResearch options, and choose wisely!Cloud TopologyZones, regions, storage allocation, HA considerations, etc.Build or BuyUse in-house resources if expertise existsThird-party resourcesBuild using existing resourcesBuild using new preconfigured hardwareDesign – Design for HA, use uniform hypervisor, Network is a key consideration – switching from basic zone or FlatDHCP to advanced zone or quantum isn’t that simple.. Make use of hypervisors uniformly..Compute density is key factor in capacot planning.. You will need to incorporate physical CPU cores, RAM, oversubscription ration and instance storage.. Storage options, object storage, block storageScalability and HA of the cloud itself – controller nodes, api end point redundancy, Automate – crowbar, chef, puppet, fuel etcMonitoring – Is usually an after thought but it shouldn’t be.. It is important to establish so,etrendig so that you can forecast capacity and plan accordingly
  • Understand your workloadMonitorBe ready to grow or cloud burst
  • Understand your workloadMonitorBe ready to grow or cloud burstAutomate
  • Understand your workloadMonitorBe ready to grow or cloud burstAutomate
  • Understand your workloadMonitorBe ready to grow or cloud burstAutomate
  • If both goes down, u have no where to go..if the disaster hits management, u still have the app,if the disaster hit app u can execute on DR scenarios..
  • If both goes down, u have no where to go..if the disaster hits management, u still have the app,if the disaster hit app u can execute on DR scenarios..
  • If both goes down, u have no where to go..if the disaster hits management, u still have the app,if the disaster hit app u can execute on DR scenarios..
  • I AM representing RightScale today, so a little bit on how RightScale can help.Server templates allow you to pre-configure servers by starting from a base image and adding scripts that run during boot, operational and shutdown phases of a server instance.The key benefit of a server template is that they help you create a easily reproducible server setup. And this can be done across multiple clouds..Through the server configuration mechanism that is built into the server templates, they servers have the ability to automatically join load balancer pools, autoscale across zones etc.
  • From technical sys admin to the business userIT can maintain control, developers can customize, and operations can automate. Everyone can get the agility of the cloudBusiness is agile, efficient, and innovative.Enabling the basic benefits, that is what this platform is about.RightScale make the power of cloud accessible to everyone with automated solutions that are easy to use.Great technology is invisible.RightScale takes care of the annoying but critical details for operational excellence.

Key Design Considerations Private and Hybrid Clouds - RightScale Compute 2013 Key Design Considerations Private and Hybrid Clouds - RightScale Compute 2013 Presentation Transcript

  • april25-26sanfranciscocloud success starts hereKey Design ConsiderationsPrivate and Hybrid CloudUtpal Thakrar, Sr. Product Manager
  • #2#2#RightscaleComputeGot Virtualization? That ain’t cloud
  • #3#3#RightscaleComputeVirtualization makes cloud happenVirtualizationCloud Computing
  • #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#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#RightscaleComputeMulti-Cloud and Hybrid Cloud• Spans more than one private or publicclouds• Extending the definition to includeprivate virtualized environments
  • #7#7#RightscaleComputeInfrastructure EvolutionOld SchoolData CenterVirtualizationEarly daysEarly “Cloudification” Sophistication andSex appeal20th century 2000 2006 Present day
  • #8#8#RightscaleComputeKey to cloud adoption
  • #9#9#RightscaleComputeBuild with an end in mind
  • #10#10#RightscaleComputeBuild with an end in mind – Agility, agility, agility
  • #11#11#RightscaleComputeWhy would you build a private cloud?• Workload and Infrastructure Interaction• Security / Regulation / Compliance• Latency• User Experience• Cost
  • #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#RightscaleComputeUse case - Hybrid Cloud BurstingPRIVATE CLOUD PUBLIC OR PRIVATE CLOUDLOAD BALANCERSAPP SERVERSMASTER DATABASESLAVE DATABASEOBJECT STORAGEAPP SERVERSPUBLICINTERNETCloud Bursting
  • #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#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#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
  • 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#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#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#RightscaleComputeFinding a home• On-premise• Co-location facility• Hosting facility adjacent to a public cloud
  • #21#21#RightscaleComputeImplementation process• Design• Automate• Monitor• Test (and test again)
  • #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#RightscaleComputeDesign Considerations/OptionsSimple ConfigurationNo HA or RedundancyHA Configuration
  • #24#24#RightscaleComputeNetwork options• OpenStack• FlatDHCP – typical for single tenant• VLAN manager – typical for multi-tenant env• CloudStack• Basic Zone• Advanced Zone
  • #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#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#RightscaleComputeAccess Control and Tenant management• Each cloud platform is slightly different but follows similarprinciples
  • #28#28#RightscaleComputeSeparate Management layer from Infrastructure• Keep the keys to the car outside the car
  • #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#RightscaleComputeAlways keep the application in mind!
  • #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#RightscaleComputemy networkmy serversmy storageCONFIGURATION AUTOMATION GOVERNANCEPrivate CloudsPublic Clouds®Agile IT Multi-Cloud Full Control
  • #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
  • april25-26sanfranciscocloud success starts hereQuestions?