april25-26 sanfrancisco

cloud success starts here

Key Design Considerations Private and Hybrid CloudUtpal Thakrar, Sr. Product Manager

# 2# 2

#RightscaleCompute

Got Virtualization? That ain’t cloud

# 3# 3

#RightscaleCompute

Virtualization makes cloud happen

Virtualization

Cloud Computing

# 4# 4

#RightscaleCompute

Public Cloud

• Hosted at a service provider

• Supports multiple customers

• Uses shared infrastructure

• Supports connectivity over public internet

• Typical consumption model is pay as you go, on-demand computing

# 5# 5

#RightscaleCompute

Private Cloud – Have it your way!

• Hosted on-premise or at a co-loco facility

• Typically Single tenant

• Suited for information requiring high level of security

• Accessed via API endpoint

# 6# 6

#RightscaleCompute

Multi-Cloud and Hybrid Cloud

• Spans more than one private or public clouds

• Extending the definition to include private virtualized environments

# 7# 7

#RightscaleCompute

Infrastructure Evolution

Old SchoolData Center

VirtualizationEarly days

Early “Cloudification” Sophistication and Sex appeal

20th century 2000 2006 Present day

# 8# 8

#RightscaleCompute

Key to cloud adoption

# 9# 9

#RightscaleCompute

Build with an end in mind

# 10# 10

#RightscaleCompute

Build with an end in mind – Agility, agility, agility

# 11# 11

#RightscaleCompute

Why would you build a private cloud?• Workload and Infrastructure Interaction• Security / Regulation / Compliance• Latency• User Experience• Cost

# 12# 12

#RightscaleCompute

When 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 same

organization for different applications, with each app in one cloud

# 13# 13

#RightscaleCompute

Use case - Hybrid Cloud Bursting

PRIVATE CLOUD PUBLIC OR PRIVATE CLOUD

LOAD BALANCERS

APP SERVERS

MASTER DATABASE

SLAVE DATABASE

OBJECT STORAGE

APP SERVERS

PUBLIC INTERNET

Cloud Bursting

# 14# 14

#RightscaleCompute

Use 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 until

they are end-of-lifed• If an application gains traction, it remains in the public cloud during its growth

phase• When stability of workload is reached, the application is transitioned into the

private cloud

# 15# 15

#RightscaleCompute

Use 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

#RightscaleCompute

RackConnect, 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 Copyright © 2013 Samsung SDS Co., Ltd. All rights reserved

Firewall IPS

VPN Gateway

CF RouterPublic ASN: XXXX

Private: 10.x.x.x/24Public: *.*.*.0/24

Private: 10.x.x.x/24Public: *.*.*.0/24

VM VM

SPCS

Virtual GW

VM

10.x.x.x/24

VM

Internet GW

EIP: e.x.y.bVM

EIP: e.x.y.aVM

ObjectStorage

VPC

Compute

Public Cloud

Internet traffic

Between SPCS and Public Cloud using public IPBetween SPCS and Public Cloud using private IPInternet traffic to SPCS and Public Cloud using public IP

Hybrid Cloud Network Architecture

Private Network

# 18# 18

#RightscaleCompute

Hardware 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 hardware

devices (load balancers in particular)

• Storage• Cost vs. Performance (commodity? SSD?, etc.)

# 19# 19

#RightscaleCompute

Software Considerations

• Cloud Infrastructure Software• CloudStack, OpenStack (Rackspace Private) etc.

• Open source with commercial support• Dictates/influences other decisions regarding cloud

implementation• Access to resources

• Web interface• API• Documentation• Industry talent pool

• Hypervisor

# 20# 20

#RightscaleCompute

Finding a home

• On-premise• Co-location facility• Hosting facility adjacent to a public cloud

# 21# 21

#RightscaleCompute

Implementation process

• Design• Automate• Monitor• Test (and test again)

# 22# 22

#RightscaleCompute

Private Cloud Infrastructure HA

Several single points of failure in OpenStack deployment• OpenStack API services• MySQL• RabbitMQ

Solved 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

#RightscaleCompute

Design Considerations/Options

Simple ConfigurationNo HA or Redundancy

HA Configuration

# 24# 24

#RightscaleCompute

Network options• OpenStack

• FlatDHCP – typical for single tenant• VLAN manager – typical for multi-tenant env

• CloudStack• Basic Zone• Advanced Zone

# 25# 25

#RightscaleCompute

Capacity 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 & in writing)

Don’t have all that? Then we have to worry about capacity planning

# 26# 26

#RightscaleCompute

Monitor 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

#RightscaleCompute

Access Control and Tenant management• Each cloud platform is slightly different but follows

similar principles

# 28# 28

#RightscaleCompute

Separate Management layer from Infrastructure

• Keep the keys to the car outside the car

# 29# 29

#RightscaleCompute

Separate 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 the

underlying infrastructure provider• Provides a cloud-portable solution• Provides orchestration tools for provisioning and management

# 30# 30

#RightscaleCompute

Always keep the application in mind!

# 31# 31

#RightscaleCompute

RightScale ServerTemplates™

• Reproducible: Predictable deployment

• Dynamic: Configuration from scripts at boot time

• Multi-cloud: Cloud agnostic and portable

• Modular: Role and behavior abstracted from cloud infrastructure

How RightScale makes it possible

# 32# 32

#RightscaleCompute

my network

my serversmy storage

CONFIGURATION AUTOMATION GOVERNANCE

Private CloudsPublic Clouds

Agile IT Multi-Cloud Full Control

# 33# 33

#RightscaleCompute

Summary/Conclusions• Private (and therefore hybrid) clouds were originally thought of as an

academic exercise or science project• Recent advances (particularly in cloud infrastructure software) have

shown 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-0208

sales@rightscale.com www.rightscale.com

april25-26 sanfrancisco

cloud success starts here

Questions?