Unit-2:

Migrating into
cloud
Here starts the
lesson!
 Contents
● Broad Approaches to Migrating into the Cloud
● The Seven-Step Model of Migration into a Cloud VM Migration
● Cloud Middleware and Best Practices
● Concept and Need of Cloud Middleware
● QoS Issues in Cloud
● Data Migration and Streaming in Cloud
● Interoperability
 Approaches to migrating
• It refers to the movement or transfer between different physical machines
without any discontinuity.
• What challenges and obstacles clients might have to overcome to tap into
the cloud?
• How their management of IT must change to secure and control their new
cloud-driven infrastructure?
• When you migrate from a client to the cloud, the issues you will face fall
into the following overall categories.
 Security Vendor Management
Security
When the user is going to migrate with
Security is an obvious threshold question,
the outsource providers, then the service
if the cloud is not secure, enterprises will
level agreements and its terms are
not consider migrating to it fearing their
thoroughly checked. While the whole
sensitive data will be tampered. For eg
idea behind cloud computing is to
Users must ensure that they understand the
propose a standardized, multi-tenant
underlying infrastructure of the cloud to
infrastructure, cloud vendors may not
which they migrate from their clients and
offer the same level
must also advise clients to include security
of custom SLAs as IT managers
in their cloud SLAs and terms of service.
 Technical Integration The Business View
Most firms that migrate to the cloud
When the user is going to migrate with
environment
the outsource providers, then the service
in a hybrid model, are keeping certain key
level agreements and its terms are
elements of their infrastructure in-house
thoroughly checked. While the whole
and under
idea behind cloud computing is to
their direct control, while outsourcing less
propose a standardized, multi-tenant
susceptible or core components.
infrastructure, cloud vendors may not
Integrating internal
offer the same level
and external infrastructures can be a
of custom SLAs as IT managers
technical concern.
While implementing a cloud, migration
expected at replacing on a premise major
business application may look like, at times,
a simple straightforward implementation.
It is burdened with pit
falls, which may undermine the true value
to the investment, and in fact put
enterprises in bad
situation than before.
Understanding and planning for these pitfalls is
significant for a successful
deployment of the solution.
IT and business stakeholders must work
together and have to:
● Clearly state business objectives for the cloud
migration.
● Define project scope of the cloud migration.
● Provide a set of guiding principles for all to follow.
 Seven step
migration model

Steps to perform suitable migration

 Step 1
These assessments are about the
Cloud migration assessments comprise cost of migration as well as about
assessments to understand the issues the ROI that can be achieved in
involved in the specific case of migration the case of production version.
at the application level or the code, the
design, the architecture, or usage levels.
 Step 2 Step 3
Isolating all systemic and environmental
Generating the mapping
dependencies of the enterprise application
constructs between what shall
components within the captive data center
possibly remain in the local
captive data center and what goes
onto the cloud.
 Step 4 Step 5
substantial part of the enterprise
We leverage the intrinsic features
application needs to be rearchitected,
of the cloud computing service to
redesigned, and reimplemented on the
augment our enterprise
cloud.
application in its own small ways.
 Step 6 Step 7
we validate and test the new form of the
Test results could be positive or
enterprise application with an extensive
mixed.
test suite that comprises testing the
components of the enterprise application In the latter case, we iterate and
on the cloud as well optimize as appropriate. After
several such optimizing iterations,
the migration is deemed
successful
Process
 Cloud
middleware
Another way to define
middleware is to say that
it is software that acts as a
liaison between
applications and
networks. The term is
often used in the context
of cloud computing, such
as public or private cloud.
 It is adopted by organizations trying to decouple
all their business units, depending on
Definition of integration and reusability for daily operations.
Concepts SOA allows organizations to use existing
application and system investments.
Most middleware follows the service-
oriented architecture (SOA) design or is Each of these components must be able to
designed as a platform-as-a-service (PaaS) interact with one another and other parts of the
solution. SOA is an architectural style that system. Apart from some basic components,
tries to achieve loosely coupled software each type of middleware needs a specific
applications that interact among component. For example, a database
themselves to run as a whole. middleware needs a database manager
component.
 ● Common messaging framework
Components Middleware requires messaging services to
communicate with services, applications, and
in middleware platforms. Most of these frameworks rely on
existing standards such as simple object access
● Middleware management console protocol (SOAP), representational state transfer
This console provides an overview of events (REST), or Javascript object notation (JSON).
and activities, transactions, configuration
management, and contract rules.

● Platform interface
Middleware needs to work across multiple
platforms, irrespective of where it resides.
This is the interface that is in direct contact
with the backend servers.
 Need of
cloud
middleware
 Configure and control Secure connections and
connections and data transfer
integrations
Based on information in a client or front-end Middleware typically establishes a secure
application request, middleware can customize connection from the front-end application
the response from the back-end application or to back-end data sources using Transport
service. In a retailer's ecommerce application, Layer Security (TSL) or another network
middleware application logic can sort product security protocol. And it can provide
search results from a back-end inventory authentication capabilities, challenging
database by nearest store location, based on the
front-end application requests for
IP address or location information in the HTTP
request header.
credentials (username and password) or
digital certificates.
Manage traffic
dynamically across
distributed systems
When application traffic spikes, enterprise
middleware can scale to distribute client
requests across multiple servers, on
premises or in the cloud. And concurrent
processing capabilities can prevent
problems when multiple clients try to
access the same back-end data source
simultaneously.
Quality of service- It is a challenge to
issues in Cloud implement QoS in cloud computing
applications. There are
Quality of Service refers to the ability of many techniques to provide quality of service to
networks to attain the cloud
maximum bandwidth and handle other network applications. Scheduling, admission control and
elements dynamic
like latency, error rate and uptime. Quality of resource provisioning are some techniques used
Service to achieve
include the management of other networks that goal.
resource by
allocating priorities to specific type of data
(audio, video
and file).
 Challenges
Scheduling:
Cloud service scheduling categorized into two categories:
user level and system level. At user level scheduling deals with problems raised by service
providing between both service provider and customer. Market based and auction based
schedulers are fit for ruling the supply and demand of cloud resources. Market based resource
allocation is powerful in cloud computing environment where resources are handed over to
user as a service. The system level scheduling handles with resource management in
datacenter. Datacenter contain many physical machines, Million request sent from user’s side,
scheduling these requests to the physical machines done in datacenter. This scheduling affect
the performance of datacenter. Service provisioning in cloud systems based on Service Level
Agreement (SLA). SLA is the contract between service provider and customer mentioning the
terms of agreement
including the nonfunctional requirement represented as QoS.
 Challenges
Admission Control: The main purpose of admission control is to provide strong
performance. At admission control time, the Infrastructure Provider (IP) must consider
the extra requirement along with the fundamental computational and networking
necessities that may be required to be added to runtime so it become flexible. In many
cases, these flexible requirements may be very large comparing it to the normal
requirements. For example, if there are many users are working on cloud application
with high divergence, the number of virtual machines are required more and that may
be added at runtime many times multiple of the number of the basic ones. So that, the
number of flexible requirements plays important role in the total requirements and
therefore the cost of hosting the service
 Challenges
Resource provisioning:
Dynamic resource provisioning is the process of assigning
available resources to the cloud application. Resource
allocation will make services suffer if the allocation not
managed in the right way. Resource provisioning will solve
this problem by allowing the service providers to manage
the resources of modules individually. Resource Allocation
Strategy (RAS) is all about integrating service provider
services activities to allocate insufficient resources within
the limit of cloud environment so that it meets the needs of
the cloud application. It need the demand and type of
resources for each application to complete the user task.
The order and allocation time for resources are inputs for
optimal RAS.
 Cloud
Interoperability There is a strong need for the development
of integrated interoperability
Cloud interoperability. This term authentication among all provider
refers to the ability of two or more
systems or applications to
exchange information and to use
the information that has been
exchanged together.
 ● Platform Portability: It means

Standards application development environment

or IDE should be capable enough to run
over any type of cloud infrastructure.
When consumer wishes to migrate
from one cloud Provider to another,
interoperability falls into these categories: ● Infrastructure Portability: It means
virtual server or machine images should
● Data and Application Portability: It have the freedom of portability. They
means by running applications and should be able to migrate from one
data, consumers should be able to cloud provider to another.
migrate easily from one cloud
provider to another without any
lock-in issue.