cloud migration and portability best practices
TRANSCRIPT
HOW RIGHTSCALE DOES IT:
CLOUD MIGRATION AND
PORTABILITY
• Brian Adler
Director, Enterprise Architecture
RightScale
Panelist
1
• Decision-Making Framework for Portability & Migration
• Common Use Cases for Portability
• How RightScale Helps
• Business & Technical Considerations
• Real Customer Examples
• Wrap-Up
Agenda
2
Broker Cloud Services with RightScale
Self-Service Cloud Analytics
Universal Cloud Management Platform
Cloud Management
Multi-Cloud Orchestration
3
Governance
Public
Clouds
Private
Clouds
Virtual
Servers
Bare Metal
Servers
13%
22%
17%
31%
Public Cloud Private Cloud
Enterprise Respondents with 1000+ VMs in Cloud
2015
2016
More Workloads Are Moving to Cloud
Source: RightScale 2016 State of the Cloud Report
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
Multi-Cloud Is a Given
5
• Migration
• Data center consolidation
• Cloud-first strategy
• Increased agility
• DevOps initiatives
• Cost reduction
• Portability
• Least expensive cloud
• Support global regions with different providers
• Avoid vendor lock-in; negotiating leverage
• High availability, disaster recovery
Drivers for Cloud Migration and Portability
6
But It’s Not All Rainbows and Unicorns
vSphere
AWS or
other clouds
Greenfield
workloads
Migrated
workloads
Resource Pools
Public Cloud 1
Requirements
Filters
Performance
Cost
Compliance
Geo-location
Security
Match Application Requirements to Clouds
Vendors
Existing DC
App 1 App 2
Application
Portfolio
App 1
App 2
App 3
App n
…
App 4
App 5
Public Cloud 2
Hosted Private
Internal Private
Virtualized
App 3
App 4 App 5
App 6
App 7
8
Assess Business Impact to Establish Priority
9
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
10
Manage
Natively
Migrate
Once Make Portable
Apply the Right Strategy
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
Manage
Natively
Migrate
Once
Make
Portable
Manage
Natively
Make
Portable
5 Use Cases for Portability
• Most Common
• Best-venue approach
• Geography, Cost, Features
• Lifecycle approach
• Dev/Test vs. Staging/Production
• Spiky vs. steady-state
• Disaster Recovery
• Less Common
• Split-tier architectures
• Cloud-bursting
PORTABILITY IN RIGHTSCALE
Two Options for Portability
14
AWS Azure Google CloudStack OpenStack vSphere
Multi-Cloud Image
Configuration Scripts Containers
ServerTemplate Portability
• Script-based
• Scripts that configure
appropriately for each
cloud
• Container-based
• Deploy code via Docker
containers
• Combo of both • Use scripts to configure
Docker hosts and containers
to deploy code
Application Templates
15
Load Balancers
App Servers
Master DB Slave DB
Replicate >
DNS
Configure a system: Cloud Application Template (CAT)
Configure a server: • ServerTemplates (portable)
• Docker container (portable)
• AMI
• CloudFormation
• VM template
Approaches for Cloud Selection in Self-Service
16
User chooses
cloud based on
allowed options
Requirements
dictate cloud
choice
Cost dictates cloud
choice
ASSESSING YOUR PORTFOLIO
FOR MIGRATION
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, FlexLM) w/
restricted IP Pools
Cloud-Suitability Scoring Criteria
Technical Considerations
Basics Data/Storage Other
OS availability
Clustering
Tenancy
Networking
Multicast
SSL termination
Static and Virtual
IP requirements
Filesystem/
Storage
configurations
Database I/O
requirements
Bandwidth
Data movement
Scale-down logic Master/Master DB
configurations
Application Assessment Examples
20
REFACTOR
DON’T MIGRATE HOLD OFF
QUICK WINS
Technical Fit
Bu
sin
ess Im
pa
ct App 6
App 5
App 9
App 5 – Easy
App 6 – Medium
App 9 – Hard
• App 5
• Partner lookup directory
• Internal user (employee) facing web application
• Stateless application
• No shared filesystem
• No unique network or IP requirements
Application Assessment – “Easy”
21
Application Assessment Examples
22
REFACTOR
DON’T MIGRATE HOLD OFF
QUICK WINS
Technical Fit
Bu
sin
ess Im
pa
ct App 6
App 5
App 9
App 5 – Easy
App 6 – Medium
App 9 – Hard
• App 6
• JBoss application
• Multicast used for clustering app servers
• Application redesign required to use WKA (well-known addresses)
• Unsupported OS (HP-UX)
• Required porting to different OS
• Stateless application
• No shared filesystem
• No unique network or IP requirements
Application Assessment – “Medium”
23
Application Assessment Examples
24
REFACTOR
DON’T MIGRATE HOLD OFF
QUICK WINS
Technical Fit
Bu
sin
ess Im
pa
ct App 6
App 5
App 9
App 5 – Easy
App 6 – Medium
App 9 – Hard
• App 9
• Oracle RAC
• Multicast required by Oracle grid infrastructure processes
• Shared, multi-mountable filesystem required
• Virtual IP required for failover
• Licensing concerns
Application Assessment – “Hard”
25
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, TLS, etc.
• Third-party tools also available for data at-rest encryption and key
management
Security
Migration Tool Realities
• 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 and benefits
Takeaways
30
• A Multi-Cloud Platform
• Professional Services to Help You Move
• Cloud vendors may fund some PS work to migrate apps to their cloud
• Managed Services to Keep It Running
RightScale Can Help
31
• Definitive Guide to Cloud Strategy
www.rightscale.com/lp/cloud-strategy-guide
Q&A
32
THANK YOU.