rightscale webinar: designing private & hybrid clouds (hosted by citrix)

Partner Logo

March 21, 2013

Building Blocks for Private and Hybrid Clouds

Partner Logo

-Brian Adler, Sr. Services Architect, RightScale

-Vijay Tolani, Private Cloud Specialist, RightScale

Please use the “Questions” window to ask questions any time!

Your Panel Today

Partner Logo

Definitions and Terminology

Infrastructure Evolution

Private Cloud Key Considerations

Hybrid Clouds – Different things to different people

Use Cases for Private and Hybrid Clouds

Best Practices for Private/Hybrid Cloud Design and Implementation

• Design Considerations• Hardware Considerations• Software Considerations• Implementation• Management

Conclusion/Q&A

Agenda


Application Portfolio

Requirements Filter

Resource Pools

App 1

App 2

App 3

Performance

Cost

Compliance

Geo-location

Security

Workload Liberation

Management & automation – across cloud resource pools

App N

…

App 1

App 2

App 3

Hosted Private

Public Cloud 2

Public Cloud 1

Vendors

Existing DC

App 4

App 5

App N

…

App 4

App 5

Internal Private


Virtualization (server)• Division of one physical server into multiple isolated virtual environments

Private Cloud• A collection of compute, storage, and network resources for a single tenant

that are accessed programmatically via an API endpoint.

Public Cloud• A similar set of resources that is multi-tenant and is provided by a cloud

vendor with access via an API endpoint.

Multi-Cloud• An environment that spans two or more separate clouds, be they both

public, both private, or one (or more) of each.

Hybrid Cloud• An environment that spans one or more public clouds as well as one or

more private clouds.

Definitions and Terminology


Old school Datacenters• Racks of physical nodes, one application per node• It’s all we knew, it worked, and it was fine.

Virtualization – The Early Years• Capability of a node outgrew the needs of any single application

• Lots of idle resources on each node• Virtualization provided the ability to have a many-to-one (servers per node)

relationship• This was better

Cloud Computing• Automated provisioning and management via an API appears

• This is much, much better

Infrastructure Evolution


Workload and Infrastructure Interaction• Applications have different resource needs• Choose the right fit for your application and your infrastructure

Security• Data may be contained within the private cloud, thus allowing for stricter

security compliance

Latency• Consumers of the private cloud resources are generally “closer” to the private

cloud, which reduces latency

User Experience• Related to latency, end user experience is enhanced due to proximity to

resources.

Cost• OPEX is generally reduced. (CAPEX is another story )

Private Cloud Key Considerations


What if application outgrows the private cloud?

Common desire is for “cloud-bursting”• When private cloud resources are exhausted, a server tier expands into the

public cloud to tap into the “infinite” resources• Considerations:

• Security – public Internet is traversed• Latency – traversal of public Internet involves the Great Unknown• Cost – bandwidth charges for public Internet traversal• Complexity – setting up a secure environment is not a trivial task

More common use case is multiple clouds in an organization, with multiple applications, and with each application contained entirely within a single cloud.

Hybrid Clouds


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


Self-Service IT Portal (“IT Vending Machine”)• Users select one of several preconfigured tech stacks• Isolated Test/Dev environments

Use Cases


Use Cases

Self-Service IT Portal (“IT Vending Machine”)• Demo


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

Use Cases


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

Use Cases


Location of Physical Hardwareᵒ On-premise

• Availability considerations (power, cooling, networking, etc.)ᵒ Hosted or Colocation facility

• Accessibility of hardware for additions and/or modification• Latency to end users• Security

Availability and Redundancy Configurationᵒ Easiest configuration (single zone, single region, single API endpoint) does

not promote high availability• Outage of API endpoint renders entire cloud unavailable• Power issues affect entire pool of resources

ᵒ High Availability of cloud resources requires more complex configurations• Multiple zones, multiple regions (if possible/practical)• Multiple API endpoints• Redundant and segregated power and networking

Design Considerations


Design Considerations/Options

Simple ConfigurationNo HA or Redundancy

HA Configuration


Intended Workloads and Use Casesᵒ Does the application require high availability or is it tolerant of interruptions of

service?• User-facing will most likely require HA.• Batch processing tasks may not.

ᵒ Is flexibility of the infrastructure required for test-beds and/or proof-of-concepts?• Potential topologies and hardware options will be affected/limited

ᵒ Does the application require (or greatly benefit from) GPUs or other specialized processors?

ᵒ Does the application have high IOPS demands?ᵒ Are low-latency or high bandwidth interconnects required?

Design 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.)

Hardware Considerations


Cloud Infrastructure Softwareᵒ CloudStack /CloudPlatform

• Open source vs. commercialᵒ Dictates/influences other decisions regarding cloud implementationᵒ Access to resources

• Web interface• API

Cloud Management Softwareᵒ 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

Software Considerations


Hardware Procurementᵒ Pre-existing or new?

• Pre-existing limits ability to tailor infrastructure to workloads

Cloud Infrastructure Softwareᵒ This decision will dictate/limit many future decisionsᵒ Research options, and choose wisely!

Cloud Topologyᵒ Zones, storage allocation, HA considerations, etc.

Build or Buyᵒ Use in-house resources if expertise existsᵒ Third-party resources

• Build using existing resources• Build using new preconfigured hardware

Implementation Process


Compatibilityᵒ Avoid vendor lock-in at IaaS level, hypervisor level, cloud infrastructure

software level

Unified Control/Securityᵒ “Single pane of glass” for user access, keys and credentials, etc.

On-Demand, Self-Service Provisioningᵒ Allow users to access resources without administrative intervention

Focus on Applicationsᵒ Core competency is in application development, so remove yourself from

image management, automation, provisioning, etc.

Management Process


Zynga’s zCloud

• Concept to production in < 6 months

• Built on commodity hardware

• Supports no less than thousands of physical servers

• Can (and have) fully provisioned over 1,000 physical servers in less than 24 hours

• Integrated with RightScale

RightScale’s Hybrid-cloud Engine at work

Source: Zynga CTO – Infrastructure; InterOp, May 2011


Hybrid Cloud Reality: Zynga’s zCloud


Coupa

Results: • Built hybrid cloud in with Cloudstack

Challenges: • Customer data residency

requirements in Canada and Europe

“RightScale multi-cloud support enables us to transparently host Coupa on public clouds such as Amazon and Rackspace or a CloudStack-based private cloud while delivering high availability and data privacy compliance.”

Sanket Naik, Sr. Director, Cloud Operations and Integrations


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.

Summary/Conclusions


1. Learn: Read Brian’s White Paper

Will be included in follow-up email

2. Try: Free Edition www.rightscale.com/free

3. Attend our Conference to talk

more with us and the CloudPlatform teamwww.RightScaleCompute.com

Next StepsContact RightScale

(866) [email protected]

The next big RightScale Community Event!April 25-26 in San Francisco

www.RightScaleCompute.com• Attend technical breakout sessions

• Get RightScale training• Talk with RightScale customers• Ask questions at the Expert Bar

http://www.rightscale.com/free

http://www.rightscalecompute.com/

mailto:[email protected]

http://www.rightscale.com/

http://www.rightscalecompute.com/

rightscale webinar: designing private & hybrid clouds (hosted by citrix)

Technology

private cloud resources

private cloud specialist

cloud vendor

private clouds

privatehybrid cloud

cloud resource pools

public clouds

security app