CONSIDERATIONS FOR

CHOOSING CLOUD PROVIDERS

• Rishi Vaish VP of Product, RightScale

• Kim Weins VP of Marketing, RightScale

Q&A

• Ben Ingalls Sales Development Representative, RightScale

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

Your Panel Today

• Market Stats

• Building a Cloud Portfolio

• 6 Considerations for Choosing Clouds

• Geography

• Demand

• Availability

• Functionality

• Security and Compliance

• Cost

Agenda

2

About RightScale

Self-Service Cloud Analytics

RightScale Cloud Portfolio Management

Cloud Management

Design

Private/Virtualized

Environments

Public

Clouds

Other

Services

Automate

Multi-Cloud Orchestration

Operate Deploy Report Optimize

Public Cloud

Only

Private

Cloud

94% of Respondents are Using Cloud

58% 7% 29%

Public

and Private

Source: RightScale 2014 State of the Cloud Report

Cloud Usage is Ubiquitous

Hybrid is the Preferred Strategy

Source: RightScale 2014 State of the Cloud Report

4%

4%

5%

8%

9%

11%

12%

18%

49%

8%

17%

10%

17%

14%

25%

19%

15%

25%

10%

12%

8%

10%

11%

10%

10%

14%

9%

0% 20% 40% 60% 80% 100%

HP Cloud

Google IaaS

Softlayer/IBM

Google App Engine

Rackspace Public Cloud

Azure IaaS

Azure PaaS

VMware vCHS

AWS

Enterprise Public Cloud Usage % of Respondents Running Applications

Running apps

Experimenting

Plan to use

AWS is Dominating Public Cloud Adoption

Source: RightScale 2014 State of the Cloud Report

6%

13%

15%

21%

26%

52%

9%

12%

25%

15%

17%

10%

3%

6%

12%

7%

10%

6%

0% 20% 40% 60% 80%

Eucalyptus

Citrix CloudStack

OpenStack

Microsoft System Center

VMware vCloud Director

VMware vSphere/vCenter

Enterprise Private Cloud Usage % of Respondents Running Applications

Running apps

Experimenting

Plan to use

VMware Dominates Private Environments

Source: RightScale 2014 State of the Cloud Report

It’s a Portfolio

1. Operate anywhere

2. Leverage existing investments

3. Optimize costs

4. Access unique capabilities

5. Create resilient architectures

6. Maintain vendor leverage

7. Future-proof your cloud strategy

8. Multi-cloud happens

Why a Cloud Portfolio?

9

Application

Portfolio Requirements

Filters Resource

Pools

App 1

App 2

App 3

Geography

Demand

Functionality

Compliance

Availability

Choosing the Best Venue for an Application

App N

…

Hosted Private

Public Cloud 2

Public Cloud 1

Cost

Existing DC

App 4

App 5 Internal Private

Virtualized

App 1 App 2

App 3

App 4 App 5

App 6

App 7

Preserving Future Portability: Two Approaches

11

AWS Azure Google CloudStack OpenStack vSphere

Multi-Cloud Image

Configuration Scripts Containers

12

You Need a Framework

6 Considerations For Choosing Clouds

13

Geography Demand Availability

Functionality Security &

Compliance Cost

6 Considerations For Choosing Clouds

14

Geography Demand Availability

Functionality Security &

Compliance Cost

Geography: Where Are Your Apps? Users?

Map Against Cloud Options

Amazon Web Services

Datapipe

Google Cloud Platform

HP Cloud

IBM SoftLayer

Rackspace

Windows Azure

Public Clouds

Singapore

Hong Kong

Tokyo

Dallas

DC Area

NYC

Area

SF Area

Seattle

Chicago

Dublin

London

Amsterdam

Oregon

São Paulo

Las Vegas

Southeast

Midwest

Shanghai

Sydney

W Europe

Private Clouds

CloudStack

OpenStack

vSphere

Cloud Considerations

Public If there is a provider that has a datacenter in the geography

Private If no public provider or you have a private cloud in the geography

Virtualized If you already have a virtualized datacenter in the geography

Hybrid If you need to span public and private for different geographies

Geography

17

General Considerations

You may need more than one public cloud provider

Plan for zones or regions for DR in each geography

Consider data residency requirements

You may need special business relationships in certain geographies

6 Considerations For Choosing Clouds

18

Geography Demand Availability

Functionality Security &

Compliance Cost

Demand: How Will It Evolve?

Variable Steady State Spiky

Public Cloud

Cloudburst

What About Hybrid Cloudbursting?

20

Low latency

Private Network

Private Cloud

Cloud Considerations

Public Good fit for large, spiky or transient workloads

Private Provides elasticity within a fixed pool of resources

Virtualized Works for very steady and predictable demand

Hybrid Provides the flexibility to move between the above options

Demand

21

General Considerations

Greenfield workloads tend to be unpredictable

Dev and Test are very transient/variable workloads

Marketing campaigns and promos can be spiky

Think about seasonal variations

Cloudbursting and split-tier architectures are advanced options, but not widely used

6 Considerations For Choosing Clouds

22

Geography Demand Availability

Functionality Security &

Compliance Cost

Availability? Dev/Test is About Agility

23

AWS VMware AWS

While Production Requires HA/DR

24

Load Balancers

App Servers

Master DB Slave DB

App Servers

Slave DB

Replicate > Replicate >

Load Balancers

PRIMARY WARM DR

DNS

Outage-Proof with Independent Control Plane

25

Replicate >

< Failover> < Failover>

Your Public

Cloud A

RightScale

Primary

RightScale

Backup

Your Public

Cloud B

Your Private

Cloud

RightScale UI RightScale API

User B User A User C

Globally Hosted

Scalable

Resilient

SaaS Platform

Your Cloud

Applications

Secure authentication

and communication

Cloud Considerations

Public Achieved through best practice architectures, not just SLAs

Private On-premise and hosted datacenters have outages too

Virtualized See above

Hybrid Consider hybrid DR scenarios

Availability

26

General Considerations

Outages happen – regardless of public or private. Plan for resiliency.

SLAs in the cloud will be different

6 Considerations For Choosing Clouds

27

Geography Demand Availability

Functionality Security &

Compliance Cost

Functionality: An Evolving Feature Set

28

Cloud Considerations

Public IaaS+/PaaS features, networking options, hybrid options, etc..

Private Depends on your private cloud platform and implementation

Virtualized How do you cloud-enable your virtualized environment

Hybrid How will you replace “cloud-specific” features?

Functionality

29

General Considerations

If portability is a goal, plan for substitutes for cloud-specific features

Stay up-to-date with the latest offerings

6 Considerations For Choosing Clouds

30

Geography Demand Availability

Functionality Security &

Compliance Cost

31

Cloud Security

Ecosystem

Cloud Provider

Enterprise

RightScale

3rd Party Vendors

Plan for a Cloud Security Ecosystem

Options Abound

32

• RightScale provides

visibility, governance,

auditing across clouds

• Cloud providers offer

cloud-specific security

options

• 3rd party vendors offer

multi-cloud options

• Ability for segregation of

duties: encryption provider

vs cloud storage provider

Capability Who?

Encrypt data in transit Vendor, Enterprise

Encrypt data at rest Vendor, Cloud, Enterprise

Secure communications RightScale, Cloud, Enterprise,

Vendor

Systems Configuration /Network

segmentation

Cloud, Enterprise, RightScale

Integrate with IAM RightScale, Cloud, Enterprise,

Vendors

Privileged identity management RightScale, Cloud, Enterprise

Backup/Replicate data RightScale, Cloud, Enterprise,

Vendor

Coordinate BC & DR RightScale, Cloud, Enterprise,

Vendor

Log cloud activity RightScale, Cloud, Enterprise,

Vendor

Shared Responsibility for Cloud Security

Cloud Provider Certifications

33

Cloud Considerations

Public Ensure cloud provider has certifications necessary for your apps

Private If you need to own the infrastructure

Virtualized If you need to own the infrastructure

Hybrid Compliance itself does not force hybrid

Security & Compliance

34

General Considerations

Security/Compliance in the cloud is a shared responsibility

Compliance requirements does NOT automatically mean you have to go private

Some enterprises are not comfortable with certain types of data in the public cloud

6 Considerations For Choosing Clouds

35

Geography Demand Availability

Functionality Security &

Compliance Cost

Is Public or Private Most Cost-Effective?

36

Variable

load Seasonality

Traditional on-premise provisioning

• Have you accounted for all your costs?

• Are your loads steady-state?

• Will usage of steady-state loads change in the future?

Seasonality? Growth?

• How much do you need to overprovision on-premise

infrastructure to cover spikes?

• What is the value of agility and flexibility?

• What is affinity for CapEx vs OpEx?

Assessing Cost: Public vs Private

37

• Instance Capabilities

• Instance RAM/Memory

• What generation of chips?

• Included storage? Or not?

• SSD drives?

• Purchase Options and Discounts

• Reserved Instances

• Spot pricing

• Sustained use

• EAs

• Other Discounts

• Support and Services

• Future Price Cuts

Public Cloud: Not Always Apples-to-Apples

38

Accurate Planning with Cloud Analytics

39

Cloud Considerations

Public Combine on-demand pricing with RIs/Sustained Use/Discounts

Private Are you considering all costs?

Virtualized Are there sunk costs you want to take advantage of?

Hybrid Preserve portability for cost arbitrage

Cost

40

General Considerations

Public cloud providers have thousands of price points

Virtualized environments may have a heavy licensing fee to the virtualization vendor

Many enterprises are maintaining multiple public cloud options

Negotiation leverage comes with portability

• Hybrid and Multi-Cloud are Strategies of Choice

• Expect a Portfolio of Clouds

• Choose Clouds to Meet Business and Technical

Requirements

Wrap Up

41

42

Thank You and Q&A

Next Steps:

RightScale Definitive Guide to Cloud Portfolio Management: http://www.rightscale.com/lp/cloud-portfolio-management-guide

RightScale Definitive Guide to Cloud Strategy: http://www.rightscale.com/lp/cloud-strategy-guide

THANK YOU.