This PPT covers the following topics: Introduction Broad Approaches to Migrating into the Cloud The Seven-Step Model of Migration in to a Cloud

1. MIGRATION
INTO
A CLOUD
Chap - 2
Unit - II

2. Contents:
 Introduction
 Broad Approaches to Migrating into the Cloud
 The Seven-Step Model of Migration in to a
Cloud

3. What is Cloud Migration?
 A cloud migration is when a company moves some
or all of its data center capabilities into the cloud,
usually to run on the cloud-based infrastructure
provided by a cloud service provider such as AWS,
Google Cloud, or Azure.
 When and how to migrate one’s application into cloud?
 What part of the IT application to migrate into a cloud?
 What not to migrate into a cloud?
 What kind of customers really benefit from migrating their
IT into the cloud?
Questions

4. Cloud Computing Definition
“It is a techno-business disruptive model of
using distributed large-scale data centers
either private or public or hybrid offering
customers a scalable virtualized infrastructure
or an abstracted set of services qualified by
service-level agreements (SLAs) and charged
only by the abstracted IT resources consumed.”

5. The Promise of the Cloud

6. IT needs had some common features:
- They were..
 Typically web-oriented
 Represented seasonal IT demands
 Amenable to parallel batch processing
 Did not have high security demands

7. The Cloud Service Offerings and Deployment Models

8. IaaS- oriented services offered abstracted
(virtualized or scalable), like compute
power/storage/badwidth
For Eg: Pricing tarrifs webpage for 2009, amazon offered 6 levels of
abstracted elastic cloude computer(EC2) server power:
“small-instance”
“large-instance”
“high-cpu instance”
High-cpu medium instance”
High-cpu extra-large instance”

9. Challenges in the Cloud

10. BROAD APPROACHES TO MIGRATING
INTO THE CLOUD
• Why Migrate?
– economic and business reasons why an enterprise
application can be migrated into the cloud, and there
are also a number of technological reasons.
– initiatives in adoption of cloud technologies in the
enterprise, resulting in integration of enterprise
applications running off the captive data centers with
the new ones that have been developed on the cloud.
– Adoption of or integration with cloud computing
services is a use case of migration.

11. • Migration can happen at one of the five levels of application,
code, design, architecture, and usage.
• Either the application is clean and independent
– So it runs as is
– Perhaps some degree of code needs to be modified and
adapted
– The design (and therefore the code) needs to be first
migrated into the cloud computing service environment
– Perhaps the migration results in the core architecture being
migrated for a cloud computing service setting, this
resulting in a new architecture being developed, along with
the accompanying design and code implementation
– while the application is migrated as is, it is the usage of the
application that needs to be migrated and therefore
adapted and modified

12. The migration of an enterprise application is best captured by
the following
• P is the application before migration running in captive
data center,
• P′c is the application part after migration either into a
(hybrid) cloud,
• P′l is the part of application being run in the captive local
data center,
• P′OFC is the application part optimized for cloud.

13.  However, when the entire application is migrated onto
the cloud, then P′l is null.
 Indeed, the migration of the enterprise application P
can happen at the five levels of application, code,
design, architecture, and usage. It can be that the P′c
migration happens at any of the five levels without any
P′l component.

14. THE SEVEN-STEP MODEL OF MIGRATION
INTO A CLOUD
A structured and process-oriented approach to migration into
a cloud has several advantages of capturing within itself the
best practices of many migration
projects.

15. Iterative Seven-Step Model

16.  These assessments are about the cost of migration as
well as about the ROI
 Isolating all systemic and environmental dependencies
of the enterprise application
 the mapping constructs between what shall possibly
remain in the local captive data center and what goes
onto the cloud.
 Perhaps the enterprise application needs to be re-
architected, redesigned, and re-implemented on the
cloud.

17.  validate and test the new form of the
enterprise application with an extensive test
suite that comprises testing the components of
the enterprise application on the cloud as well.
 iterate and optimize as appropriate.
 After several such optimizing iterations, the
migration is deemed successful.

19. Compared with the typical approach to migration
into the Amazon AWS
Seven-step model is more generic, versatile, and
comprehensive. It is about six steps is as follows:
 The 1st phase is the cloud migration assessment
phase wherein dependencies are isolated and
strategies worked out to handle these dependencies.
 The 2nd phase is in trying out proof of concepts to
build a reference migration architecture.
 The 3rd phase is the data migration phase wherein
database data segmentation and cleansing is
completed.
Or
 perhaps using the “hybrid migration strategy,”

20.  The critical parts of the enterprise application are
retained in the local captive data center while
noncritical parts are moved into the cloud.
 The 5th phase comprises leveraging the various
Amazon AWS features like elasticity, autoscaling,
cloud storage, and so on.
 Finally in the 6th phase, the migration is optimized for
the cloud.

21. Best Practices for Migrating into a Cloud
• Best Practices
– Design for failures – underlying cloud systems are commodity items
• Avoid Single Points of Failure in your Applications
• Develop loose coupling between applications / code / services
• Exploit key cloud features: scaling, elasticity, network locality
and location independence, anonymity, support for hybrid
clouds, etc
• Build security, reliability and other non-functional requirements
at every level and layer
• Rethink architectural constraints to avail cloud benefits
• Iterate and Optimize
• Beware of Vendor-Lock ins, Data Security Issues, SLAs and
Pricing Honeypots
• Optimal Migration yield best ROI for using Cloud offerings
• Data and Application migration is pretty popular while more
challenging is the Architecture and Design migration for PAAS
and SAAS platforms – it is still evolving.

22. Migration risks
The general migration risks :
• Performance monitoring and Tuning
• The business continuity and disaster recovery;
• The compliance with standards and governance issues;
• The IP and licensing issues;
• The quality of service (QoS) parameters as well as the
corresponding SLAs committed to;
• The ownership, transfer, and storage of data in the
application;
• The portability and interoperability issues;
• The issues that result in migration failure and loss of
business confidence in these efforts.

23. Security-related migration risks:
• Trust and privacy.
• Obtaining the right execution logs as well as retaining
the rights to all audit trails at a detailed level—which
currently may not be fully available.
• However, the robustness of the solutions to prevent
data loss is not fully validated.
• Key aspects of vulnerability management and incident
responses quality are yet to be supported in a
substantial way by the cloud service vendors.
• Finally there are issues of consistent identity
management as well.