This document discusses cloud computing concepts including desired features of clouds, cloud computing features, challenges of cloud computing, hypervisor types, virtual machine migration techniques, and examples of cloud platforms and tools. The key points covered are the desired features of self-service, metering and billing, elasticity, and customization for clouds. Virtualization, virtual networking, and dynamic resource allocation are listed as important cloud computing features. Security, portability, interoperability, and performance are identified as challenges.

2.  Cloud Computing refers to manipulating,
configuring and accessing the hardware and
software resources remotely.

3. 1.DESIRED FEATURES
2.FEATURES
3.CHALLENGES OF CLOUD COMPUTING
4.CHALLENGES AND RISKS
5.ADVANTAGES AND DIS-ADVANTAGES

4. DESIRED FEATURES OF A CLOUD:
1. Self-Service:
 Consumers of cloud computing services expect on-demand, nearly
instant access to resources.
 That customers can request, customize, pay, and use services
without intervention of human operators.
2. Per-Usage Metering and Billing:
 Cloud computing eliminates up-front commitment by users,
allowing them to request and use only the necessary amount.
 Services must be priced on a short term basis (e.g., by the hour),
allowing users to release (and not pay for) resources as soon as they
are not needed .
 For these reasons, clouds must implement features to allow efficient
trading of service such as pricing, accounting, and billing.
 Metering should be done accordingly for different types of service
(e.g., storage, processing, and bandwidth) .

5. 3.Elasticity:
 Cloud computing gives the illusion of infinite
computing resources available on
demand.(increase/decrease)
 Therefore users expect clouds to rapidly provide
resources in any quantity at any time.
 (a) provisioned, possibly automatically, when an
application load increases and
 (b) released when load decreases (scale up and
down).

6. 4.Customization:
 In a multi-tenant cloud a great disparity between user
needs is often the case.
 Thus, resources rented from the cloud must be highly
customizable.
 In the case of infrastructure services customization
means allowing users to deploy specialized virtual
appliances and to be given privileged (root) access to
the virtual servers.
 Other service classes (PaaS and SaaS) offer less
flexibility and are not suitable for general-purpose
computing , but still are expected to provide a certain
level of customization.

7. Features:
1. Virtualization Support.
2. Self-Service, On-Demand Resource Provisioning
3. Multiple Backend Hypervisors
4. Storage Virtualization.
5. Interface to Public Clouds
6. Virtual Networking.
7. Dynamic Resource Allocation
8. Virtual Clusters
9. Reservation and Negotiation Mechanism
10. High Availability and Data Recovery

8. 3. CHALLENGES OF CLOUD COMPUTING:

9. 1.Security and Privacy:
 Security and Privacy of information is the biggest challenge to cloud
computing. Security and privacy issues can be overcome by employing
encryption, security hardware and security applications.
2.Portability:
 applications should easily be migrated from one cloud provider to
another. There must not be vendor lock-in. However, it is not yet made
possible because each of the cloud provider uses different standard
languages for their platforms.
3.Interoperability:
 It means the application on one platform should be able to incorporate
services from the other platforms. It is made possible via web services,
but developing such web services is very complex.
4.Computing Performance:
 Data intensive applications on cloud requires high network bandwidth,
which results in high cost. Low bandwidth does not meet the desired
computing performance of cloud application.
5.Reliability and Availability:
 It is necessary for cloud systems to be reliable and robust because most
of the businesses are now becoming dependent on services provided by
third-party.

10. 1.SECURITY AND PRIVACY
2.DATA LOCK-IN STANDARDIZATION
3.AVAILABILITY,FAULT –TOLERANCE,AND
DIASTER RECOVEY.
4.RESSOURCES MANAGEMENT AND ENERGY-
EFFICIENCY.

11. Hypervisor:
A hypervisor or virtual machine monitor (VMM)
is computer software, firmware or hardware that creates and
runs virtual machines.
A computer on which a hypervisor runs one or more
virtual machines is called a host machine, and each virtual
machine is called a guest machine
There are two types of hypervisors: Type 1 and Type 2
1. Type 1 hypervisors :
Type 1 hypervisors run directly on the system hardware.
They are often referred to as a "native" or "bare metal" or
"embedded" hypervisors in vendor literature.
The type1 hypervisor does not have any host operating
system because they are installed on a bare system.

13. Type 2 hypervisor:
- Its Run on a host operating system.
- A Type 2 hypervisor (sometimes called a ‘Hosted’
hypervisor) runs inside an operating system which in turn runs
on the physical hardware.
Each guest operating system then runs a top the hypervisor.
Desktop virtualization systems often work in this manner.

15.  Provide an environment identical to the physical
environment
 Provide that environment with minimal performance
cost
 Retain complete control of the system resources

17. 1 server virtualization
2 Client or Desktop virtualization
3.service and Application virtualization
4 network virtualization
5 Storage virtualization

18.  The benefits of hardware virtualization decrease the
overall cost of cloud users and increase the flexibility.
1. Lower Cost
2. Efficient resource utilization
3. Increase IT flexibility:
4. Advanced Hardware Virtualization features

19. 1.Full Virtualization:
Here the hardware architecture is completely
simulated.(supported)
Guest software doesn't need any modification to run any
applications..
2.Emulation Virtualization:
Here the virtual machine simulates the hardware & is
independent.
Furthermore, the guest OS doesn't require any
modification.
3.Para-Virtualization: Here, the hardware is not simulated;
instead the guest software runs its isolated system.

21. Migration of Virtual Machines to Alternate
Platforms:
 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,

22. 1.IT SERVICE REQUEST
2.VM PROVISION
3.VM’S IN OPERATION
4.RELEASE ME

24. 1.IT SERVICE REQUEST:
◦ This request is being processed by the IT administration to start seeing the
servers’ resources Pool, matching these resources with the requirements starting
the provision of the needed virtual machine.
◦ Guest OS calculate actual requirements required to use resources such as
servers, bandwidth, computing power required to meet.
2.VM PROVISION:
- meet the environment to meet the requirements is a regular a regular user .
3.VM IN OPERATION:
- Meet the requirements application running on the web platform
VM operates auto licensing resources based on customers requirements.
4.RELEASE ME:
- End of service
- Compute resources de-allocated to other VM

26. VM Provision Process
 Firstly, you need to select a server from a pool of available
servers (physical servers with enough capacity) along with the
appropriate OS template you need to provision the virtual
machine.(-choose a good server).
 Secondly, you need to load the appropriate software
(operating system you selected in the previous step, device
drivers, middleware, and the needed applications for the
service required).
 Thirdly, you need to customize and configure the machine
(e.g., IP address, Gateway) to configure an associated network
and storage resources.(using)
 Finally, the virtual server is ready to start with its newly
loaded software.

27.  The virtual server provisioning is defining server
configuration based on the organization requirements a,
hardware and software component (processor ,RAM ,storage,
networking , operating system, applications ,etc ).
 Normally, virtual machines can be provisioned by manually
installing an operating system, by using a preconfigured VM
template, by cloning an existing VM, or by importing a
physical server or a virtual server from another hosting
platform.
 After creating a virtual machine by virtualizing a physical
server, or by building a new virtual server in the virtual
environment, a template can be created out of it. Most
virtualization management vendors (VMware, Xen Server,
etc.)

28.  Migration service, in the context of virtual machines, is the
process of moving a virtual machine from one host server or
storage location to another
 In this process, all key machines’ components, such as CPU,
storage disks networking, and memory, are completely
virtualized, thereby facilitating the entire state of a virtual
machine to be captured by a set of easily moved data files.

29. Migrations Techniques:
1.Live Migration and High Availability: HOT-REAL
 It can be defined as the movement of a virtual machine from
one physical host to another while being powered on.
 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.

31. 2.Live Migration Anatomy, Xen Hypervisor
Algorithm:
 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.
 Stage 0: Pre-Migration. An active virtual machine exists on
the physical host A.
 Stage 1: Reservation. A request is issued to migrate an OS
from host A to host B (a precondition is that the necessary
resources exist on B and on a VM container of that size).
 Stage 2: Iterative Pre-Copy: During the first iteration, all
pages are transferred from A to B. Subsequent iterations copy
only those pages dirtied during the previous transfer phase.

32.  Stage 3: Stop-and-Copy. Running OS instance at A is
suspended, and its network traffic is redirected to B. As
described in reference 21, CPU state and any 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.
 Stage 4: Commitment. Host B indicates to A that it has
successfully received a consistent OS image. Host A
acknowledges this message as a commitment of the migration
transaction. Host A may now discard the original VM, and
host B becomes the primary host.
 Stage 5: Activation. The migrated VM on B is now activated.
Post-migration code runs to reattach the device’s drivers to the
new machine and advertise moved IP addresses.

33. 3.Live migration effect on a running web server:
Take an example appache web server this served static
web content at a high rate as
4.Live migration vendor implementation examples:
there are lot of vm management and provisioning tools that
provide the live migration of vm facility two of which vm
ware vmotion and citrix xenserver “xen motion”.
5.Vmware v-motion
these are used to automatically optimize and allocate an
entire pool of resources for maximum hardware utilization,
flexibility and availability and perform hardware’s
maintenance without scheduling downtime along with
migrating virtual machines away from failing or
underperforming.

34. 6.Citrix xen-server xen-motion:
 which provides the IT administrator with the facility to
move a running VM from one Xen-Server to
another in the same pool without interrupting the
service (hypothetically for zero-downtime server
maintenance, which actually takes minutes), making it
a highly available service.

35. 7.Regular/cold migration:
 With cold migration, you have the option of moving the
associated disks from one data store to another.
 The virtual machines are not required to be on a shared
storage.
 It’s important to highlight that the two main differences
between live migration and cold migration are that live
migration needs a shared storage for virtual machines in the
server’s pool, but cold migration does not; also, in live
migration for a virtual machine between two hosts, there
would be certain CPU compatibility checks to be applied;
while in cold migration this checks do not apply.

36. 8.Live storage migration of virtual machine
 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.
 For more details about how this option is working in a
VMware product.

37.  AMAZON-S3
 AMAZON-EC2
 EUCALYPTUS
 EUCALYPTUS-ARCHITECTURE
 UBUNTU CLOUD AND EUCALYPTUS
 V.M DYNAMIC MANAGEMENT USING OPENNEBULA.
 OPEN NEBULAAND HAIZEA
 ANEKA
 ANEKA ARCHITECTRE

38.  Amazon S3 (Simple Storage Service)
It is just a storage service, typically used to store
large binary files.
◦ it is a scalable, high-speed, low-cost web-based service
designed for online backup and archiving of data and
application programs.
◦ It allows to upload, store, and download any type of files up to
5 GB in size.
The subscriber has control over the accessibility of
data,
◦ Long-Term Storage

39. Amazon Elastic Compute Cloud:
 On-Demand instances, which allow you to pay a fixed rate
by the hour with no commitment.
 Reserved instances, which allow you to pay a low, one-
time fee and in turn receive a significant discount on the
hourly usage charge for that instance.
 It ensures that any reserved instance you launch is
guaranteed to succeed (provided that you have booked them
in advance).
 This means that users of these instances should not be
affected by any transient limitations in EC2 capacity.
 Spot instances, which enable you to bid whatever price you
want for instance capacity, providing for even greater
savings, if your applications have flexible start and end
times.

40.  Open Source cloud tool
 Elastic utility computing architecture for linking your programs
to useful systems
 Private cloud and hybrid cloud
◦ Amazon EC2,S3 interface
 Features
◦ Interface compatibility with EC2, and S3
◦ Simple installation and deployment
◦ Support for most Linux distributions
◦ Support for running VMs that run a top the Xen or KVM (VMWare?!)
◦ Secure internal communication using SOAP with WS security
◦ Administrator’s tool for system’s management and user’s accounting
◦ configure multiple clusters each with private internal network addresses
into a single cloud
 Research Lines
◦ service’s provisioning, Scheduling, SLA formulation, hypervisors’
portability
4November 2012Cloud Computing - Part II 40

41. 4November 2012Cloud Computing - Part II 41

42. 1.NODE CONTROLLER(NC):
controls the execution ,Inspection, and termination of VM instances on the host
where it runs.
2.CLUSTER CONTROLLER (CC):
gather the information about and schedules VM execution on specific node
controllers, as well as manage virtual instance network.
3.STORAGE CONTROLLER(SC):
is a put/get storage service storage service that implementation Amazon’s S3
interface and provides a way for storing and accessing VM images and user data.
4.CLOUD CONTROLLER(CLC):
is the entry point into the cloud for users and administrators, it queries and node
managers for information about resources makes high-level scheduling decisions,
and implements them by ,making requests to cluster controller.
5.WALRUS(W):
is the controller component that manages access to the storage services within
Eucalyptus. Requests are communicated to walrus using the SOAP OR REST-
based interface.
it can be very beneficial in testing and debugging purpose before deploying it on a
real cloud.

43. Ubuntu Enterprise Cloud and Eucalyptus:
 This is by far the simplest way to install and try Eucalyptus.
 Just download the Ubuntu server version and install it wherever you want.
UEC is also the first open source project that lets you create cloud services
in your local environment easily and leverage the power of cloud
computing.

44. VM Dynamic Management Using Open Nebula:
 Open Nebula can be primarily used as a virtualization tool to
manage your virtual infrastructure which is usually referred to
as private cloud.
 Open Nebula supports a hybrid cloud to combine local
infrastructure with public cloud-based infrastructure,
enabling highly scalable hosting environments.
 Open Nebula also supports public clouds by providing cloud’s
interfaces to expose its functionality for virtual machine,
storage, and network management.
 The existence of public and private clouds and also the
resources being managed by its virtual manager.

45. Open Nebula and Haizea:
 it can be used as a scheduling backend for Open
Nebula.
Resource preemption (using
vmsuspend/resume/migrate).
 Policy engine, allowing developers to write
pluggable scheduling policies in Python.

47. Aneka:
 Aneka is a .NET-based platform and framework designed for
building and deploying distributed applications on clouds.
 It provides a set of APIs for transparently exploiting
distributed resources and expressing the business logic of
applications by using the preferred programming abstractions.
 Aneka is also a market-oriented cloud platform since it allows
users to build and schedule applications, provision resources,
and monitor results using pricing, accounting, and QoS/SLA
services in private and/or public cloud environments.
 Aneka also provides support for deploying and managing
clouds. By using its Management Studio and a set of Web
interfaces, it is possible to set up either public or private
clouds, monitor their status, update their configuration, and
perform the basic management operations

48. Aneka Architecture:
consists of a collection of physical and virtualized resources
connected through a network.
 Each of these resources hosts an instance of the Aneka container
representing the runtime environment where the distributed
applications are executed.
 The services are broken up into fabric, foundation, and execution
services. Fabric services directly interact with the node through the
platform abstraction layer (PAL) and perform hardware profiling and
dynamic resource provisioning.