Wa0000.
Wa0000.
UNIT – II
Unit 2: Virtual Machines Provisioning and Migration Services
Virtual Machines Provisioning and Manageability, Virtual Machine Migration Services,
VM Provisioning and Migration in Action, Provisioning in the Cloud Context.
VM Provisioning Process:
Typical life cycle of VM and its major possible states of operation, which make
the management and automation of VMs in virtual and cloud environments easier
Process & Steps to Provision VM. Here, we describe the common and normal
steps of provisioning a virtual server:
4. Finally, the virtual server is ready to start with its newly loaded
software. Typically, these are the tasks required or being performed
by an IT or a data center’s specialist to provision a particular virtual
machine.
This enables the administrator to quickly provision a correctly configured virtual server on
demand. This ease and flexibility bring with them the problem of virtual machine’s sprawl,
where virtual machines are provisioned so rapidly that documenting and managing the
virtual machine’s life cycle become a challenge.
Migrations Techniques
When it is properly carried out, this process takes place without any noticeable effect
from the end user’s point of view (a matter of milliseconds). One of the most significant
advantages of live migration is the fact that it facilitates proactive maintenance in case
of failure, because the potential problem can be resolved before the disruption of
service occurs. Live migration can also be used for load balancing in which work is
shared among computers in order to optimize the utilization of available CPU
resources.
In this section we will explain live migration’s mechanism and how memory and
virtual machine states are being transferred, through the network, from one host A to
another host B, the Xen hypervisor is an example for this mechanism. The logical steps
that are executed when migrating an OS are summarized in the diagram below In this
research, the migration process has been viewed as a transactional interaction between
the two hosts involved
Stage-2: Pre-Copy Phase:- At this stage, the VM continuously run, and its memory is
copied page wise from the source to the target host. It starts with transferring all active
memory pages.
Stage-3: Stop-and-Copy: - In this, the VM will be stopped in source and the remaining dirty
pages will be copied to the destination and VM will be resumed in destination. Running OS
instance at A is suspended, and its network traffic is redirected to B. As described in fig.3,
CPU state and remaining inconsistent memory pages are then transferred. At the end of this
stage, there is a consistent suspended copy of the VM at both A and B. The copy at A is
considered primary and is resumed in case of failure.
This approach to failure management ensures that at least on host has a consistent VM
image at all times during migration:
a) Original host remains stable until migration commits and that the VM may be suspended
b) A migration request essentially attempts to move the VM to a new host and on any sort of
failure; execution is resumed locally, aborting the migration.
This kind of migration constitutes moving the virtual disks or configuration file of a
running virtual machine to a new data store without any interruption in the availability
of the virtual machine’s service.
One of the nicest advantages of having facility in data center’s technologies is to have
the ability to migrate virtual machines from one platform to another. There are a
number of ways for achieving this, such as depending on the source and target
virtualization’s platforms and on the vendor’s tools that manage this facility—for
example, the VMware converter that handles migrations between ESX hosts; the
VMware server; and the VMware workstation. The VMware converter can also import
from other virtualization platforms, such as Microsoft virtual server machines.
There are lots of VM management and provisioning tools that provide the live
migration of VM facility, two of which are VMware VMotion and Citrix XenServer
―XenMotion‖.
Citrix XenServer ―XenMotion‖: Based on Xen live migrate utility, it provides the IT
Administrator the facility to move a running VM from one XenServer to another in the
same pool without interrupting the service (hypothetically zero – downtime server
maintenance), making it a highly available service and also good feature to balance
workloads on the virtualized environments.
- A highly loaded server can be migrated with both controlled impact on live services
and a short downtime
- Migration on an Apache 1.3 web server, this served static content at high rate.
- Web server VM with 800 MB memory size, which serves 512 KB file to 100
customers.
In this topic we see some business with a real example of how we can manage the life cycle,
provision, and migrate a virtual machine by the help of one of the open source frameworks
used to manage virtualized infrastructure.
Here, we will use ConVirt (open source framework for the management of open source
virtualization like Xen and KVM known previously as XenMan).
1. Basic configuration in which the Xen or KVM virtualization platform is on the local
machine, where ConVirt is already installed.
In our example, we will use this dedicated machine where ConVirt is installed and used
to manage a pool of remote servers (two machines). In order to use advanced features
of ConVirt (e.g., live migration), you should set up a shared storage for the server pool
in use on which the disks of the provisioned virtual machines are stored.
Xen supports live migration. It is a useful feature and natural extension to virtualization
platforms that allows for the transfer of a VM from one physical machine to another with
little or no downtime of the services hosted by the VM. Live migration transfers the working
state and memory of a VM across a network when it is running. Xen also supports VM
migration by using a mechanism called Remote Direct Memory Access (RDMA).
This allows migration to be carried out with minimal impact on guest operating systems and
hosted applications. Fig.7 shows the a compression scheme for VM migration.
Fig. 7: Live migration of VM from the Dom0 domain to a Xen-enabled target host
The structure of this live migration system is presented in Dom0. Migration daemons
running in the management VMs are responsible for performing migration. Shadow page
tables in the VMM layer trace modifications to the memory page in migrated VMs during
the precopy phase.
Cloud provisioning is a key feature of the cloud computing model, relating to how a
customer access cloud services and resources from a cloud provider.
The growing of this cloud computing technology of cloud services that customers can
provision includes infrastructure as a service (IaaS), software as a service (SaaS) and
platform as a service (PaaS) in public or private cloud environments.
4) Service Provisioning: It requires setting up a service and handling its related data.
1) Context Brokers:
A context broker is a mediator service that decouples context consumers from context
services. It is in charge of handling subscriptions of context consumers in which they
express their interest to receive context information, and registration of context services.
Context services may then publish their newly acquired context information to the context
broker, which notifies context consumers about that newly acquired context information.
Context brokers can also be deployed on the cloud.
2) Context services:
Typically residing in different clouds, deliver context information to context consumers with
various quality-of-context and quality-of-service (QoS). Therefore, the Context Broker is in
charge of selecting appropriate context services to deliver context information to which a
context consumer has subscribed. Context information may be delivered to the same
consumer by several context services.
Context-aware Web services (CAWS) are the consumers of context information obtained
from the cloud-based context services. A CAWS is a Web service that can understand
situational context and can adapt its behavior according the changing circumstances as
context data may change rapidly. It produces dynamic results according to the 5 WH
questions: who, where, when, what, and why it was invoked. A CAWS can be responsive to
various situational circumstances, such as:
The identity of the client who invoked the service, whether it is a person, or another
Web service.
The activity that the client is carrying out at the time it invokes the service.
The preferences that the client may have defined prior to invoking the service.
The security and privacy policies associated with the client of this service.
The device (laptop, PDA, smartphone, etc.) that the client is using to invoke the
Prof. Taur A.R.
(CSE Dept.) 12
service.
1) AWS CloudFormation
5) CloudBolt
6) Snow Commander
7) Morpheus Data
8) Flexera
9) CloudSphere
10) Scalr
11) Eucalyptus
12) Open-Nebula
Eucalyptus:
Eucalyptus is a system for implementing on-premise private and hybrid clouds using
the hardware and software’s infrastructure, which is in place without modification.
The current interface to Eucalyptus is compatible with Amazon’s EC2, S3, and EBS
interfaces, but the infrastructure is designed to support multiple client-side
interfaces.
Eucalyptus is implemented using commonly available Linux tools and basic Web
service’s technologies.
Open-Nebula:
MCQ Questions:
Descriptive Questions