rightscale webinar: key considerations for cloud migration and portability
DESCRIPTION
Migrating applications to the cloud requires both a sound strategy and a clear understanding of technical considerations. In addition, you will want to ensure portability between clouds to avoid lock-in. This session will define strategic approaches to cloud migration and how to assess application suitability for migration. In this webinar we cover the following: 1. Three common strategies to guide your migration decisions 2. Evaluating cloud-readiness of your application portfolio 3. Twelve technical considerations when migrating applications to cloud 4. Six use cases for cloud portability 5. Ensuring portability between AWS, Azure, Google, OpenStack, VMware vSphere and other cloudsTRANSCRIPT
KEY CONSIDERATIONS
FOR CLOUD MIGRATION AND
PORTABILITY
• Rishi Vaish VP of Product, RightScale
• Brian Adler Principal Cloud Architect, RightScale
Q&A
• Nicholas Martinazzi Sales Development Representative, RightScale
Please use the “Questions” window to ask questions at any time
Your Panel Today
RightScale Cloud Portfolio Management
Your Cloud Portfolio
Self-Service Cloud Analytics Cloud Management
Manage Govern Optimize
RightScale Cloud Portfolio Management
Public
Clouds
Private
Clouds
Virtualized
Environments
Public Cloud
Only
Private Cloud
Only
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
VMware Dominates in Private Environments
Source: RightScale 2014 State of the Cloud Report
Dev, Test and Web are the Top Workloads
Source: RightScale 2014 State of the Cloud Report
0%
20%
40%
60%
80%
100%
Cloud Beginners Cloud Explorers Cloud Focused
% o
f R
esp
on
de
nts
Benefits Grow with Cloud Maturity % of Respondents Reporting these Benefits
CapEx to OpEx
Business continuity
IT staff efficiency
Geographic reach
Higher performance
Cost savings
Faster time-to-market
Higher availability
Faster access to infrastructure
Greater scalability
Adoption is Driven by Clear Benefits
Source: RightScale 2014 State of the Cloud Report
What about
Existing
Workloads?
What workloads
should I move to
the cloud?
Use a Portfolio
Strategy
Segment Your App Portfolio by Technology Fit
• Web architecture
• Elastic design
• Monolithic
• Legacy
• Traditional vendors
Cloud-Ready
• Greenfield
• Designed for cloud
Elastic Web
Traditional
Assess Business Impact to Establish Priority
11
REFACTOR
DON’T MIGRATE HOLD OFF
QUICK WINS
Technical Fit
Bu
sin
ess Im
pa
ct
App 1
App 7
App 3
App 12
App 4
App 6
App 2
App 5
App 8
App 11
App 10
App 9
Three Strategies for Existing Workloads
12
Manage
Natively
Migrate
Once Make Portable
Apply the Right Strategy
13
REFACTOR
DON’T MIGRATE HOLD OFF
QUICK WINS
Technical Fit
Bu
sin
ess Im
pa
ct
App 1
App 7
App 3
App 12
App 4
App 6
App 2
App 5
App 8
App 11
App 10
App 9
Manage
Natively
Migrate
Once
Make
Portable
Manage
Natively
Make
Portable
Manage
Natively
Cloudify Virtualized Environments
15
On-premises
Private
Clouds
Self-Service Portal
Corporate Firewall
Cloud Orchestration
Layer
vCenter Server™
ESXi
VMware® vSphere®
Public
Clouds
Migrate
Once
What Everyone Expects
vSphere
AWS or
other clouds
Greenfield
workloads
Migrated
workloads
Best Practice 1; Understand the realities
Understand the
Realities
Is it really one
way?
Best Practice 3; Consider portability
Make Portable
Why Portability – Dev/Test vs Production
20
VMWare AWS
Why Portability – Getting to Steady State
21
Time
Load
Public Cloud Private Cloud
Why Portability – Geographical Reach
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
Why Portability – Arbitrage Cost
23
Public
Clouds
Private
Clouds
Virtualized
Environments
Why Portability – Disaster Recover Scenarios
24
Load Balancers
App Servers
Master DB Slave DB
App Servers
Slave DB
Replicate > Replicate >
Load Balancers
PRIMARY WARM DR
DNS
Public Cloud
Cloudburst
Why Portability - Cloudburst
25
Low latency
Private Network
Private Cloud
Two Approaches to Make Applications Portable
26
AWS Azure Google CloudStack OpenStack vSphere
Multi-Cloud Image
Configuration Scripts Containers
How to Assess
Your Portfolio
Photo: stevendepolo
Cloud-Suitability Scoring Criteria
Business Considerations
Cost//ROI Vendor
Relationships Licensing
Workload
variability
OPEX vs CAPEX
Migration
Costs
Agility
Workload reuse
Speed-to-market
Level of changes
Existing vendor
relationships
Lock-in avoidance
IP-Locked
MAC-Locked
Licensing servers (FlexNet, FlexIM) w/
restricted IP Pools
Cloud-Suitability Scoring Criteria
Technical Considerations
• Windows 2008R2 ubiquitous. Windows 2012 fairly common. Windows 2003 often unsupported
• RHEL 6.x and CentOS variants fairly common. Other Linux distros may or may not be supported
Operating
Systems
• Classic one IP per SSL certificate can be prohibitive
• Some IaaS vendors have solutions (ENI, EIP, etc.) SSL
Termination
• Dynamic/transient nature of cloud complicates clustering
implementation Clustering
Cloud-Suitability Scoring Criteria
Technical Considerations
• Not supported in most IaaS offerings (Cloud Networks in
Rackspace being the exception) Multicast
Static IP
requirements
• Classic VIP implementation not available in IaaS offerings
• Higher-latency workarounds are available (i.e. ENIs/EIPs in
AWS)
Virtual IP
requirements
• Hosted VMs are co-resident with other unaffiliated VMs. May be in breach of
security/compliance regulations.
• Some vendors have alternatives for this (i.e. Dedicated Instances in AWS)
Tenancy
• Standard IP addressing scheme is dynamic. Alternatives
exist, but can be complicated and cumbersome.
Cloud-Suitability Scoring Criteria
Technical Considerations
• Classic SAN/NAS environments are not available in IaaS offerings
• Alternatives such as Ceph, GlusterFS, OpenAFS, etc.
• Some third-party vendors do provide SAN/NAS functionality
• Network proximity cannot generally be assumed.
• Network segmentation can result in false positives (i.e.
incorrect “master is down” determination)
Filesystems/
Storage
Configurations
Database I/O
requirements
Master/Master
Database
configurations
• Some IaaS providers support “provisioned IOPS”
• SSD-based storage available, but typically requires an aggressive
backup strategy
Cloud-Suitability Scoring Criteria
Technical Considerations
• Virtual NIC cannot support the exchange rates of physical
hardware due to overhead of hypervisor, multiple network stack
traversal, etc.
Bandwidth
Scale-down
Logic
Master/Master
Database
configurations
• Stateful applications require special handling of decommissioned
servers (session handoff, connection draining, etc.)
Data
Movement
• Large datasets may need to be moved to IaaS resources
• WAN optimization tools can assist in moving/copying large datasets
• Replicate data before app/VM migration to reduce migration window
• Some vendors provide disk copying services
Cloud Infrastructure Considerations
Technical Considerations
• User-controlled IP address space, routing, etc. is possible with many IaaS
offerings
• Use of VPN functionality can “extend” on-premises datacenter to the cloud
securely
Network Connectivity
Scale-down
Logic
Master/Master
Database
configurations
• Several IaaS vendors support dedicated links (AWS Direct Connect, Azure
ExpressRoute)
• Security, latency, complexity reduced
• Varying port speeds (and cost structures) available
Physical Connectivity
Cloud Infrastructure Considerations
Technical Considerations
• Public Internet (usually) required, thus latency targets can be difficult to achieve
• WAN Accelerators can be of great benefit in certain situations
Latency
Scale-down
Logic
Master/Master
Database
configurations
• Typical SAN/NAS configurations not available
• IaaS vendors provide object storage options (non-POSIX compliant)
• Shared filesystems need to be self-implemented
• GlusterFS
• Ceph
• OpenAFS
Storage
Cloud Infrastructure Considerations
Technical Considerations
Scale-down
Logic
Master/Master
Database
configurations
• Network
• VPC, Virtual Network, Cloud Networks, etc.
• Data
• At-rest: Some vendors provide encrypted block and/or object storage
• In-flight: HTTPS, SSL, etc.
• Third party tools also available for data at-rest encryption and key
management
Security
Migration Tools
• AWS VM Import/Export, etc.
IaaS Vendor-Supplied
Scale-down
Logic
• Entire industry sprouting up around this use-case
• Varying approaches
• Automation -Storage and networking ignored or reconfigured
• Container/Wrapper
-VMs run in third-party container
-Adds overhead impacting performance
• Combination: Automation & Manual
-Networking and storage can be duplicated
-Scalability questionable for large (dozens to hundreds of VMs) deployments
Third-Party Tools
• Hybrid cloud is the dominant model for enterprises
• You have to decide which workloads to move to cloud
• Apply a technical filter to identify segments
• Apply a business impact filter to identify priority
• Apply the appropriate strategy for migration to cloud
• Manage Natively
• Migrate Once
• Make Portable
• Portability provides a lot of flexibility!
Takeaways
37
Portability Has a Real Business Impact
38
“…it is so important for us to work with RightScale. RightScale
helps us avoid vendor lock-in with any one cloud provider,
ensures that we have the very best in cloud managed
services.”
Jeff Titus, GM, Digital Technology Solutions and Strategy, Audi of America, VW Group
Next Steps and Q&A
• Cloud Workload Migration Overview:
www.rightscale.com/lp/cloud-migration-
overview
• Try RightScale Today:
www.rightscale.com/free-trial
• Talk to us today about your requirements:
+1 888-989-1856
THANK YOU.