Initiation au Cloud

Chapter 7
Migration in Cloud Computing
4 ArcTIC
Manel Medhioub
[email protected]
 Lesson plan

1- Cloud reference model

2- Migration to the cloud
3- Application migration
4- Cloud-to-Cloud migration

2
 Cloud reference model

• We may classify Cloud reference models as one of two styles, either:

 Layer-based. Where activities or capabilities are mapped to
layers in an architecture:
• Cloud Security Alliance showing the cloud ‘stack’
• CISCO Cloud Reference Architecture Framework
• IEFT Cloud Reference Framework , showing the capabilities
for each layer.
 Role-Based. Where activities or capabilities are mapped to
roles
• DMTF Cloud Service Reference Architecture
• IBM Cloud Computing Reference Architecture
• NIST Cloud Computing Reference Architecture
3
 Cloud reference model
Reference Architecture Actors

• Actor is a person or an organization

 Participates in the cloud
 Performs tasks in the cloud
• Cloud Consumer
Cloud
Cloud Carrier

Cloud
• Cloud Provider Consumer Auditor

• Cloud Broker
• Cloud Auditor Cloud
Broker
Cloud
Provider
• Cloud Carrier
4
 Cloud reference model
Cloud Provider

• Makes a service available

• Acquires and manage the computing infrastructure
• Runs the cloud software to provide the service
• Makes arrangement to deliver the cloud service to the
cloud consumer.
• Activities:
 Service Deployment
 Service Orchestration
 Cloud Services Management
 Security
 Privacy
5
 Cloud reference model
Conceptual reference Model

Cloud Provider
Service Orchestration Cloud Service
Service Layers Management
SaaS
PaaS
Business support

Security
IaaS

Privacy
Resource Abstraction and Provisioning/
Control Layer Configuration

Physical Resource Layer Portability/

Hardware interoperability
Facility

6
NIST Special Publication 500-292
 Cloud reference model
Conceptual reference Model

Cloud Provider Cloud Broker

Service Orchestration Cloud Service

Service Layers Management
SaaS Service
Intermediation
PaaS
Business support

Security
IaaS

Privacy
Service
Resource Abstraction and Provisioning/ Aggregation
Control Layer Configuration

Physical Resource Layer Portability/

Hardware interoperability Service
Arbitrage
Facility

7
NIST Special Publication 500-292
 Cloud reference model
Cloud Broker

• Manages the use, performance and delivery of Cloud Service

• Negotiates relationships between cloud providers and cloud
consumers
• Three Categories:
 Service Intermediation:
• Improving capabilities of a service
• Providing value-added service to cloud consumer.
 Service Aggregation:
• Combines and integrates multiple services in one new service.
• Data integration and securing data transaction
 Service Arbitrage:
• Flexibility to aggregate multiple services from multiple agencies.
• No fixed combination and integration of services.
8
 Cloud reference model
Conceptual reference Model

Cloud Provider Cloud Broker

Service Orchestration Cloud Service

Service Layers Management
Cloud SaaS Service
Auditor Intermediation
PaaS
Business support

Security
IaaS

Privacy
Security
Audit Service
Resource Abstraction and Provisioning/ Aggregation
Privacy Control Layer Configuration
Impact Audit
Physical Resource Layer Portability/
Hardware interoperability Service
Performance Arbitrage
Audit Facility

9
NIST Special Publication 500-292
 Cloud reference model
Cloud Auditor

• A third-party that conducts independent

assessment of:
 cloud services, information system operations,
performance and security of the cloud
implementation.
• Verification of the compliance with regulation
and security policy.

• Protect the confidentiality, integrity, and

availability of the system and its information. 10
 Cloud reference model
Conceptual reference Model

Cloud Provider Cloud Broker

Service Orchestration Cloud Service

Service Layers Management
Cloud SaaS Service
Auditor Intermediation
PaaS
Business support

Security
IaaS

Privacy
Security
Audit Service
Resource Abstraction and Provisioning/ Aggregation
Privacy Control Layer Configuration
Impact Audit
Physical Resource Layer Portability/
Hardware interoperability Service
Performance Arbitrage
Audit Facility

Cloud Carrier
11
NIST Special Publication 500-292
 Cloud reference model
Cloud Carrier

• It acts as an intermediary providing connectivity

and transport between the cloud consumer and
the cloud provider.
 Network, telecommunication and access devices.

• Provides dedicated and secure connections

between cloud consumers and cloud providers.
 According to the SLAs set up with a cloud provider

12
 Cloud reference model
Conceptual reference Model

Cloud Provider Cloud Broker

Cloud
Consumer Service Orchestration Cloud Service
Service Layers Management
Cloud SaaS Service
Auditor Intermediation
PaaS
Business support

Security
IaaS

Privacy
Security
Audit Service
Resource Abstraction and Provisioning/ Aggregation
Privacy Control Layer Configuration
Impact Audit
Physical Resource Layer Portability/
Hardware interoperability Service
Performance Arbitrage
Audit Facility

Cloud Carrier
13
NIST Special Publication 500-292
 Cloud Migration

• Cloud migration is the process of moving

data, applications or other business elements
from
 an organization's onsite computers to the cloud
 or moving them from one cloud environment to
another.

14
Migration to the cloud
Ready for the Cloud?

15
 Migration to the cloud
characteristics of workload

• Fluctuating demand: When a workload has a stable and

predictable demand, having dedicated and properly sized
infrastructure for that workload is probably more efficient than
paying hourly charges for VMs in a public cloud or building and
using a private and automated cloud.

• Standard: Efficiencies in cloud computing are achieved thanks

to virtualization and automation. Automation is only cost-
effective if there is a limited set of features (in SaaS solutions)
or pieces of software (in IaaS in PaaS solutions) available in the
catalog.

16
 Migration to the cloud
characteristics of workload

• Independent: If a workload requires heavy communications

with other systems, migration of that workload alone to a
public cloud environment might affect performance negatively
because of issues with latency and bandwidth between the
data center and the public cloud environment.

• Non-critical: Workloads with very high demanding

requirements (availability, response time, recovery time
objective…) might not be ready to be hosted in public clouds
yet. Service levels offered by public clouds do not usually meet
the requirements of critical workloads

17
 Migration to the cloud

START MODEL OF MIGRATION INTO A CLOUD

Assess

Optimize isolate
END

The iterative Seven

Steps7
Test Migration model Map

Augmen Re-
t architect

18
Cloud computing : principles and paradigms
 Migration to the cloud
Assess Isolate Map Re-Architect Augment Test Optimize

- Cloudonomics -Runtime - Mapping -New - Exploit - Augment Test -Optimize–

-Migration Environment Environments Usecases additional Cases and rework and
Costs - Licensing - Mapping -Analysis cloud features Test Automation iterate
-Recurring - Libraries libraries & - Design - Autoscaling - Run Proof-of- - Significantly
Costs Dependency runtime -Storage Concepts Satisfy
-Database -Applications - Approximat -Bandwidth - Test Migration cloudonomics
Migration Dependency -ions - Security strategy of migration
-Functionality - Latencies the mapping - Test new - Optimize
migration Bottlenecks constructs Test cases due compliance
-Performance between what to cloud with standards
bottlenecks shall augmentation -Deliver best
- Architectural possibly - Test for migration ROI
Dependencies remain in the Production - Develop
local captive Loads roadmap for
data center leveraging new
and what cloud features
goes onto the
cloud

Some details of the iterative Seven Step Model 19

 Migration to the cloud

• Return on investment (ROI) is the ratio between

net profit and the cost of investing in resources.
• ROI is usually evaluated over a given period of
time.
• Therefore, ROI can be increased by decreasing
the investment, increasing profits, or realizing
the profits sooner.
• Cloud is often a very efficient (high ROI)
investment.
20
Application Migration

21
Application Migration

22
 Application Migration
Decisions

Key questions in “cloud planning” include:

• public cloud (and if so, which one), or a private cloud
within my existing data center?
• application remediation strategy to accommodate
such a move or rebuild from scratch?
• Should I hybridize my application?
• When should I consider public cloud SaaS solutions
for my end-users?
• is portability across multiple heterogeneous clouds
important for my application?
• http://technet.microsoft.com/en-us/cloud/hh389787.aspx
23
 Application Migration
Assess application

• Understand the business objectives of

application for the cloud.
• Verify if there is a variable demand for resources
within app that can take advantage of flexible
cloud infrastructure
• Understand network needs and dependencies.
• Make in consideration compliance with
regulatory requirements

24
 Application Migration

• Many IT professionals are struggling to

overcome the complexities of
 selecting, analyzing, and migrating existing
applications portfolios to private and/or public
clouds.
• After an application has been identified as a
candidate for cloud migration, it is necessary
to consider for what service model of cloud
the application is best suited.
25
 Application Migration
Criteria

• Software as a Service: if SaaS-based alternatives

exist and can meet both business and technical
needs.
• Platform as a Service: if applications are based on
standard application server software such as Java
EE 5 or Microsoft’s .NET platform.
• Infrastructure as a Service: Migration of an
application to an IaaS involves deploying the
application on the cloud service provider’s
servers. 26
 Application Migration
Criteria

• SLAs: availability, scalability, and performance

• Data portability: ability to export data in a format
that can be easily migrated
• Long-term costs: carefully compare longer-term
recurring costs over time
• Security: security policies for virtual and physical
isolation, adequate security is provided, based on
the nature of application data.
• Scalability: dynamic scaling features
27
 Application Migration
Gartner’ ways 1/2

• Gartner presentsfive ways by which organizations can

move applications into the cloud, IT organizations can:

 rehost on (IaaS)
– redeploy applications to a different hardware environment
– change the application’s infrastructure configuration.
– It can provide a fast cloud migration solution.

 refactor for (PaaS)

– run applications on a cloud provider’s infrastructure
– developers can reuse languages, frameworks, and containers
they have invested in
28
 Application Migration
Gartner’ ways 2/2

 revise for IaaS or PaaS

– modify or extend the existing code base to support legacy modernization
requirements
– allows organizations to optimize the application to leverage the cloud characteristics
of providers' infrastructure.
– Use rehost or refactor options to deploy to cloud
 rebuild on PaaS
– discard code and re-architect the application
– access to innovative features in the provider's platform
– improve developer productivity
 replace with software-as-a-service (SaaS)
– discard an existing application (or set of applications) and use commercial software
delivered as a service
– avoids investment in mobilizing a development team when requirements for a
business function change quickly.

• according to research firm Gartner

29
 Application Migration
Cloud migration strategies

30
 Application Migration
Cloud migration strategies

31
 Application Migration
Cloud migration strategies

32
 Cloud-to-cloud migration

• (C2C) is the movement of physical or virtual

machines from one cloud computing provider to
another:
• along with their associated configurations, operating systems,
applications and storage
• The cost of a cloud migration should not outweigh
the advantages of moving to a new cloud provider.
• Having the ability to move easily between cloud
providers is an important consideration when
choosing a cloud provider.
33
 Cloud-to-cloud migration
Spreading Workloads Across Multiple Cloud Providers

• Migration between providers is a major

concern due to lack of portability standards.
• Customer workloads should be evidently
 Interoperable
 securely portable between providers

• Providers and cloud brokers should

• allow migration without additional formatting
• address vendor/virtualisation platform lock-in fears
• alleviate any provisioning and management burden 34
 Cloud-to-cloud migration
Spreading Workloads Across Multiple Cloud Providers

• Various open source cloud management

platforms designed to simplify cloud-to-cloud
migration have recently emerged:
 Apache distribution of Citrix’ CloudStack alongside
that vendor’s own Cloud Platform derivative,
 OpenStack framework
 The private cloud IaaS platform from Eucalyptus.

35
 Cloud-to-cloud migration
Spreading Workloads Across Multiple Cloud Providers

• Move some applications to the cloud’,

architects face embarrassing choices about
how to do this.
• Decision must consider:
 an organization’s requirements
 evaluation criteria
 architecture principle

36
 Conclusion

• Transitioning to the cloud or between cloud

environments presents the usual IT issues:
 Privacy and security,
 interoperability,
 data and application portability,
 business continuity.

37