cloud migration and portability (with and without containers)
TRANSCRIPT
CLOUD MIGRATION AND PORTABILITY
(WITH OR WITHOUT CONTAINERS)
• Brian Adler
• Director of Enterprise Architecture, RightScale
• Kim Weins
• VP Marketing, RightScale
Panelists
RightScale
Cloud Management Platform
Orchestrate, automate and govern applications
across any cloud, any server, and any container
Two Solutions from RightScale
VIRTUAL
SERVERS
PUBLIC
CLOUDS
IAAS+/PAAS
SERVICES
PRIVATE
CLOUDS
BARE METAL
SERVERS
CONTAINER
CLUSTERS
User access controls and governance
Governance
MULTI-CLOUD ORCHESTRATION
RightScale
Optima
Work collaboratively with business units and
resource owners to reduce wasted cloud spend.
Optima
Cost management and
collaborative optimization
RightScale CMP Solution
VIRTUAL
SERVERS
PUBLIC
CLOUDS
IAAS+/PAAS
SERVICES
PRIVATE
CLOUDS
BARE METAL
SERVERS
CONTAINER
CLUSTERS
RightScale Cloud Management Platform
User access controls and governance
Governance
Cloud Management
Multi-cloud visibility,
automation, and operations
Self-Service
Catalog of templates and
automated provisioning
MULTI-CLOUD ORCHESTRATION
• Migration and Portability Defined
• Onboarding to Cloud
• Cloud to Cloud
• Ongoing Portability
• Containers or Not?
Agenda
4
IT’S A
MULTI-CLOUD WORLD
85% of Enterprises Want Multi-Cloud
Single private 5%
Single public 9%
No plans 1%
Multiple private 7%
Multiple public 20%
Hybrid cloud 58%
Enterprise Cloud Strategy 1000+ employees
Multi-Cloud
85%
Source: RightScale 2017 State of the Cloud Report
Stage of Use # of Public
Clouds Used
Running applications 1.8
Experimenting 1.8
Total 3.6
Multiple Public Clouds in Use
Source: RightScale 2017 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
8
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
9
• Migration (one-time)
• Onboard – migrate to cloud for first time
• Cloud to Cloud – move from cloud A to cloud B
• Portability (ongoing)
• Semi-portable – architected to move later with some effort
• Fully-portable – can deploy seamlessly on multiple supported clouds
Definitions
10
Use Cases for Portability
• Most Common
• Avoid lock-in
• Ability to move at some point
• Best venue approach (typically for batch/dev/qa)
• Geography, Cost, Features
• Lifecycle approach
• Dev/Test vs. Staging/Production on different resource pools
• Disaster Recovery
• Less Common
• Split-tier architectures
• Cloud-bursting
ONBOARDING TO CLOUD
Onboarding:
Assess Business Impact to Establish Priority
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
Three Strategies Onboarding Workloads
14
Manage
As Is
Migrate
Once Make Portable
Onboarding: Apply the Right Strategy
15
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
Migrate
Once
Make
Portable
Manage
As Is
Make
Portable
Manage
As Is Migrate
Once
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
Multi-cast
SSL termination
Static and Virtual
IP requirements
Filesystem/
Storage
configurations
Database I/O
requirements
Bandwidth
Data movement
Scale-down logic Master/Master DB
configurations
CLOUD TO CLOUD
• Determine Regions Needed cloudcomparison.rightscale.com
• Map Available Cloud Services
cloudcomparison.rightscale.com
• Plan for Integrations
• Compare Cloud Costs
• Line Up Expertise/Training/Support
Cloud to Cloud Migration Assessment
19
Determine Regions Needed
20
Map Available Cloud Services
21
Select
required
services Compare
providers
Share with
others
Drill down
to provider
website
• Example one: On AWS, considering move to Google
• Using NFS from AWS Marketplace
• No equivalent on Google at the time
• Decision to stay on AWS and switch to AWS EFS
• Example 2: On AWS, considering move to Google
• Google ILB (Internal Load Balancer) was in preview and not Generally
Available
• Decision to move anyways
• Customer “rolled their own” with Nginx
What If It’s a Mismatch?
22
Compare Cloud Costs
23
RightScale Scenario Builder
Cloud Provider Calculators
• Application Assessment
• Application Migration
• Development of Automated Templates
• Training
• Managed Services
Expertise & Assistance: RightScale Can Help
24
• AWS – Basic, Developer, Business and Enterprise
• All different SLAs and capabilities
• Pricing is % of spend
• Google – Gold, Silver, Platinum
• All different SLAs and capabilities
• Pricing is % of spend
• Moving to Role Based support in 2017…flat fees, per user per month
• IBM BlueMix – Free, Basic, Standard, Premium
• All different SLAs and capabilities
• Pricing is % of spend
• Azure – Developer, Standard, Pro. Direct, Premier
• Flat Fee
• Premier is custom
Support Services and SLAs
25
PORTABILITY
IN RIGHTSCALE
Two Options for Portability
27
AWS Azure Google IBM OpenStack vSphere
Multi-Cloud Image
Automated Configuration Containers
RightScale Templates 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
Containers Help with Portability
28
Container Hosts
(VMs)
In Cloud
AWS ECS
GKE
Azure
Container
Service
Orchestrator
Container Hosts
(VMs)
On-Premise
Proprietary
Orchestrator
Kubernetes
Orchestrator
Choice of
Orchestrator
C C C
C C C
C C C
C C C
C C C
C C C
C C C
C C C
C C C
C C C
Changing clouds will change your host level provisioning and/or
setup and use a container orchestrator
Changing clouds will still require changes in use of
• persistent storage
• cloud specific services
• network topology
RightScale Templates for Portability
29
Load Balancers
App Servers
Master DB Slave DB
Replicate >
DNS
Configure a system: Cloud Application Template (CAT)
Configure a server & deploy
code: • RightScale ServerTemplates
• Chef, Puppet, Ansible
• Docker containers
Approaches for Cloud Selection in RightScale
30
User chooses
cloud based on
allowed options
Requirements
dictate cloud
choice
Cost dictates cloud
choice
