Virtualization - MODULE 2 - Cloud Computing Btech
Virtualization - MODULE 2 - Cloud Computing Btech
TO
VIRTUALIZATION
Cloud Computing Technologies
There are certain technologies working behind the cloud computing platforms
making cloud computing flexible, reliable and usable. These technologies are listed
below:
➢ Virtualization
➢ Service-Oriented Architecture(SOA)
➢ Grid Computing
➢ Utility Computing
Virtualization is key enabler
Virtualization
➢ Virtualization is the process of running a virtual instance of a computer system in a layer
abstracted from the actual hardware. Most commonly, it refers to running multiple operating
systems on a computer system simultaneously.
➢ To the applications running on top of the virtualized machine, it can appear as if they are on
their own dedicated machine, where the operating system, libraries, and other programs are
unique to the guest virtualized system and unconnected to the host operating system which sits
below it.
Capability of server with and without
virtualization
Traditional Servers vs Virtualized
Servers
Single server running Virtualization
Some terminologies associated with
Virtualization
3.Container: Some light-weighted VMs that are subpart of the same operating system
instance as its hypervisor are known as containers. They are a group of processes that runs
along with their corresponding namespace for process identifiers.
Some terminologies associated with
Virtualization
5. Virtual Network: It is a logically separated network inside the servers that could be
expanded across multiple servers.
Characteristics of Virtualization
• Desktop Virtualization
• Application Virtualization
• Server Virtualization
• Storage Virtualization
• Network Virtualization
Hypervisors
A hypervisor is a form of virtualization software used in Cloud hosting to divide and
allocate the resources on various pieces of hardware. The program which provides
partitioning, isolation or abstraction is called virtualization hypervisor. The hypervisor is
a hardware virtualization technique that allows multiple guest operating systems (OS) to
run on a single host system at the same time. A hypervisor is sometimes also called a
virtual machine manager(VMM).
Types of Hypervisor
1. Type I Hypervisor – Bare Metal Structure
➢ The virtualization software resides on the “bare metal” or the hard disk of the hardware,
where the operating system is usually installed.
➢ Bare metal isn’t only used to describe hypervisors. A bare metal server is a regular,
single-tenant server. However, it can be a host machine for virtual machines with the
addition of a hypervisor and virtualization software.
➢ A bare metal cloud refers to a customer renting the actual servers that host the public
cloud from a cloud service provider, in addition to renting the public cloud services.
Type I Hypervisor – Bare Metal Structure
Pros & Cons of Type-I Hypervisor
Pros:
Such kind of hypervisors are very efficient because they have direct access
to the physical hardware resources(like Cpu, Memory, Network, Physical
storage). This causes the empowerment the security because there is
nothing any kind of the third party resource so that attacker couldn’t
compromise with anything.
Cons:
One problem with Type-1 hypervisor is that they usually need a dedicated
separate machine to perform its operation and to instruct different VMs and
control the host hardware resources.
Type II Hypervisor – Hosted Structure
➢ A Host operating system runs on the underlying host system. It is also known as
‘Hosted Hypervisor”. Such kind of hypervisors doesn’t run directly over the
underlying hardware rather they run as an application in a Host
system(physical machine). Basically, software installed on an operating system.
➢ Hypervisor asks the operating system to make hardware calls. Example of Type
2 hypervisor includes VMware Player or Parallels Desktop.
➢ The type-2 hypervisor is are very useful for engineers, security analyst(for
checking malware, or malicious source code and newly developed applications).
Type II Hypervisor – Hosted Structure
Pros & Cons of Type-II Hypervisor
Pros:
Such kind of hypervisors allows quick and easy access to a guest Operating
System alongside the host machine running. These hypervisors usually come with
additional useful features for guest machine. Such tools enhance the coordination
between the host machine and guest machine.
Cons:
Here there is no direct access to the physical hardware resources so the efficiency
of these hypervisors lags in performance as compared to the type-1 hypervisors,
and potential security risks are also there an attacker can compromise the
security weakness if there is access to the host operating system so he can also
access the guest operating system.
Choosing the right hypervisor
4. Ecosystem
There are several benefits to using a hypervisor that hosts multiple virtual machines:
•Speed
•Efficiency
•Flexibility
•Portability
Virtual Machines
• VMs can also provide integrated disaster recovery and application provisioning
options.
Disadvantages of Virtual Machines
While virtual machines have several advantages over physical machines, there are
also some potential disadvantages:
• Running multiple virtual machines on one physical machine can result in unstable
performance if infrastructure requirements are not met.
• Virtual machines are less efficient and run slower than a full physical
computer. Most enterprises use a combination of physical and virtual
infrastructure to balance the corresponding advantages and disadvantages.
Types of Virtual Machines
•Lightweight
•Portable and platform independent
•Supports modern development and architecture
•Improves utilization
Difference between VM and
Container
SNo. Virtual Machines(VM) Containers
1 VM is piece of software that allows you to install other software While a container is a software that allows different
inside of it so you basically control it virtually as opposed to functionalities of an application independently.
installing the software directly on the computer.
2. Applications running on VM system can run different OS. While applications running in a container environment share a
single OS.
3. VM virtualizes the computer system. While containers virtualize the operating system only.
4. VM size is very large. While the size of container is very light; i.e. a few megabytes.
5. VM takes minutes to run, due to large size. While containers take a few seconds to run.
6. VM uses a lot of system memory. While containers require very less memory.
7. VM is more secure. While containers are less secure.
8. VM’s are useful when we require all of OS resources to run various While containers are useful when we are required to maximize
applications. the running applications using minimal servers.
9. Examples of VM are: KVM, Xen, VMware. While examples of containers are:RancherOS, PhotonOS,
Containers by Docker.
Container vs hypervisor
Containers and hypervisors are both involved in making applications faster and more
efficient, but they achieve this in different ways.
Hypervisors:
•Allow an operating system to run independently from the underlying hardware through the use of
virtual machines.
•Share virtual computing, storage and memory resources.
•Can run multiple operating systems on top of one server (bare-metal hypervisor) or installed on top
of one standard operating system and isolated from it (hosted hypervisor).
Containers:
•Allow applications to run independently of an operating system.
•Can run on any operating system—all they need is a container engine to run.
•Are extremely portable since in a container, an application has everything it needs to run.
SERVICE ORIENTED
ARCHITECTURE
Service Oriented Architecture(SOA)
What is a Service?
• A service is a reusable component that can be used as a building block to form
larger, more complex business-application functionality.
• A service provides a discrete business function that operates on data. Its job is to
ensure that the business functionality is applied consistently, returns predictable
results, and operates within the quality of service required.
Service Oriented Architecture(SOA)
Use Service
Service
Client Provider
Service Oriented Architecture(SOA)
Service Oriented Architecture(SOA)
Call flow to a service
2. Discovery 1. Publishing
3. YP Lookup
Registry
Client
4. Request
Service Providing
4. Request Peers
5. Async Reply
Service Oriented Architecture(SOA)
Characteristics of a Service
• Supports open standards for integration
• Loose coupling
• Stateless
• Location agnostic
• Abstraction
• Reusability
• Autonomy
• Discoverability
• Composability
Service Oriented Architecture(SOA)
Advantages of EDI:
There are several advantages to Electronic Data Interchange:
Disadvantages of EDI:
•A very systematic and proper back up is required as the entire data relies on EDI.