0% found this document useful (0 votes)
28 views

Cloud Computing Unit3

Uploaded by

sudip
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
28 views

Cloud Computing Unit3

Uploaded by

sudip
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 58

Unit 3: Cloud Virtualization technology

(10 Hrs.)
• Introduction to Virtualization,
• different types of Virtualization,
• Implementation Levels of Virtualization
Structures,
• Benefits of virtualization,
• server virtualization,
• virtualization software,
• Types of Hypervisor, and Load balancing,
• Infrastructure requirement for virtualization
Introduction to Virtualization,
• Virtualization is a technique, which allows to
share single physical instance of an application
or resource among multiple organizations or
tenants (customers).

• It does so by assigning a logical name to a


physical resource and providing a pointer to
that physical resource on demand.
Virtualization Concept
• Creating a virtual machine over existing
operating system and hardware is referred as
Hardware Virtualization.
• Virtual Machines provide an environment that
is logically separated from the underlying
hardware.
• The machine on which the virtual machine is
created is known as host machine and virtual
machine is referred as a guest machine.
• This virtual machine is managed by a software
or firmware, which is known as hypervisor.
Hypervisor
• The hypervisor is a firmware or low-level
program that acts as a Virtual Machine Manager.
There are two types of hypervisor:
• Type 1 hypervisor executes on bare system.
LynxSecure, RTS Hypervisor, Oracle VM, Sun
xVM Server, VirtualLogic VLX are examples of
Type 1 hypervisor.
The following diagram shows the Type 1
hypervisor
• Type 2 hypervisor is a software interface that
emulates the devices with which a system
normally interacts.
• Containers, KVM, Microsoft Hyper V, VMWare
Fusion, Virtual Server 2005 R2, Windows Virtual
PC and VMWare workstation 6.0 are examples of
Type 2 hypervisor.
The following diagram shows the Type 2
hypervisor.
• Types of Hardware Virtualization
• Here are the three types of hardware virtualization:
• Full Virtualization
• Emulation Virtualization
• Paravirtualization

Full Virtualization
• In full virtualization, the underlying hardware is
completely simulated.
• Guest software does not require any modification to
run.
Emulation Virtualization
• In Emulation, the virtual machine simulates the
hardware and hence becomes independent of it.
• In this, the guest operating system does not
require modification.
Paravirtualization
• In Paravirtualization, the hardware is not
simulated.
• The guest software run their own isolated
domains.
Types of Virtualization
• OS Virtualization—aka Virtual Machines
• Application-Server Virtualization
• Application Virtualization
• Administrative Virtualization
• Network Virtualization
• Hardware Virtualization
• Storage Virtualization
1. OS Virtualization—aka Virtual
Machines
• Virtualizing an operating system environment is
the most common form of virtualization.
• It involves putting a second instance or multiple
instances of an operating system, like Windows, on
a single machine.
• This empowers businesses to reduce the amount of
physical hardware required to run their software by
cutting down the number of actual machines.
• It saves companies cash on energy, cabling,
hardware, rack space, and more, while still allowing
them to run the same quantity of applications.
2. Application-Server Virtualization
• Application-server virtualization is another large presence
in the virtualization space, and has been around since the
inception of the concept.
• It is often referred to as ‘advanced load balancing,’ as it
spreads applications across servers, and servers across
applications.
• This enables IT departments to balance the workload of
specific software in an agile way that doesn’t overload a
specific server or underload a specific application in the
event of a large project or change.
• In addition to load balancing it also allows for easier
management of servers and applications, since you can
manage them as a single instance.
• Additionally, it gives way to greater network security, as
only one server is visible to the public while the rest are
hidden behind a reverse proxy network security appliance.
3. Application Virtualization
• Application virtualization is often confused
with application-server virtualization.
• What it means is that applications operate on
computers as if they reside naturally on the
hard drive, but instead are running on a server.
• The ability to use RAM and CPU to run the
programs while storing them centrally on a
server, like through Microsoft Terminal
Services and cloud-based software, improves
how software security updates are pushed, and
how software is rolled out.
4. Administrative Virtualization
• Administrative virtualization is one of the least-
known forms of virtualization, likely due to the
fact that it’s primarily used in data centers.
• The concept of administration, or ‘management,’
virtualization means segmented admin roles
through group and user policies.
• For example, certain groups may have access to
read specific servers, infrastructure, application
files, and rules, but not to change them.
5. Network Virtualization
• Network virtualization involves virtually managing IPs,
and is accomplished through tools like routing tables,
NICs, switches, and VLAN tags.
6. Hardware Virtualization
• Hardware virtualization is one of the rarer forms of
virtualization, and when simply explained it is similar to
OS virtualization (it is, in fact, often required for OS
virtualization).
• Except, instead of putting multiple software instances on a
single machine, chunks of a machine are partitioned off to
perform specific tasks.
7. Storage Virtualization
• Storage virtualization is an array of servers that are
managed by a virtual storage system.
• The servers aren’t aware of exactly where their data is, and
instead function more like worker bees in a hive.
1. Instruction Set Architecture Level
• At the ISA level, virtualization is performed by
emulating a given ISA by the ISA of the host
machine.
• For example, MIPS binary code can run on an x86-
based host machine with the help of ISA emulation.
With this approach, it is possible to run a large
amount of legacy binary code writ-ten for various
processors on any given new hardware host
machine.
• Instruction set emulation leads to virtual ISAs
created on any hardware machine.
2. Hardware Abstraction Level
• Hardware-level virtualization is performed right on top of
the bare hardware.
• On the one hand, this approach generates a virtual
hardware environment for a VM.
• On the other hand, the process manages the underlying
hardware through virtualization. The idea is to virtualize a
computer’s resources, such as its processors, memory, and
I/O devices.
• The intention is to upgrade the hardware utilization rate by
multiple users concurrently.
• The idea was implemented in the IBM VM/370 in the
1960s.
• More recently, the Xen hypervisor has been applied to
virtualize x86-based machines to run Linux or other guest
OS applications.
3. Operating System Level
• This refers to an abstraction layer between traditional
OS and user applications.
• OS-level virtualiza-tion creates isolated containers on a
single physical server and the OS instances to utilize
the hard-ware and software in data centers.
• The containers behave like real servers. OS-level
virtualization is commonly used in creating virtual
hosting environments to allocate hardware resources
among a large number of mutually distrusting users.
• It is also used, to a lesser extent, in consolidating server
hardware by moving services on separate hosts into
containers or VMs on one server.
4. Library Support Level
• Most applications use APIs exported by user-level
libraries rather than using lengthy system calls by the
OS.
• Since most systems provide well-documented APIs,
such an interface becomes another candidate for
virtualization.
• Virtualization with library interfaces is possible by
controlling the communication link between
applications and the rest of a system through API
hooks. T
• he software tool WINE has implemented this approach
to support Windows applications on top of UNIX hosts.
Another example is the vCUDA which allows
applications executing within VMs to leverage GPU
hardware acceleration.
5. User-Application Level
• Virtualization at the application level virtualizes an
application as a VM. On a traditional OS, an application
often runs as a process. Therefore, application-level
virtualization is also known as process-level virtualization.
• The most popular approach is to deploy high level language
(HLL)
• VMs. In this scenario, the virtualization layer sits as an
application program on top of the operating system, and the
layer exports an abstraction of a VM that can run programs
written and compiled to a particular abstract machine
definition.
• Any program written in the HLL and compiled for this VM
will be able to run on it.
• The Microsoft .NET CLR and Java Virtual Machine
(JVM) are two good examples of this class of VM.
Benefits of virtualization
• By adopting virtualization in their cloud environment, organizations can
realize the following security benefits.
1. Flexibility
Organizations have the flexibility to share systems without essentially having
to share critical information or data across the systems.
2. Data Protection
They can prevent loss or damage to critical data, in cases where the system is
compromised owing to malicious activities.
3. Security against attacks
They have the ability to reduce the risk of multiple attacks in case of an
exposure by methodically isolating applications and virtual machines.
4. Cost Effectiveness
It improves the physical security of organizations by reducing hardware
requirements, thereby leading to fewer data centers.
5. Better Access Control
• A higher level of access control is offered to system and network
administrators, which separates responsibilities and improves the system’s
efficiency.
Server virtualization
• Server Virtualization is the process of dividing
a physical server into several individuals and
isolated virtual servers with software
applications.
• Every virtual server can run its own operating
systems individually
• Server Virtualization is one of the most cost-
effective methods to offer Web hosting
services and uses the existing resources
effectively in IT Infrastructure.
• If there is no server Virtualization, the servers will
only use a tiny section of their processing power.
It will result in idle servers because the workload
is divided into one portion of the network servers.
• Data centers have become overcrowded with
unutilized servers, resulting in wasting resources
and heavy power consumption.
• By having every physical server divided into
multiple virtual servers, server virtualization will
authorize each virtual server to behave as a unique
device.
• Every Virtual Server is capable of running its own
application and operating systems.
Benefits
• Key Benefits of Server Virtualization
• Server Virtualization contains higher server
capability
• Organizations experience cheaper operational
cost
• It eliminates the complexity of the server
• It helps in developing the application
performance
• With Software Virtualization, users can deploy
their workload swiftly
Working
• In Server Virtualization, the virtual servers are
wholly dedicated to performing a specific task.
• Each virtual server behaves like a physical device
that is capable of running its Operating System.
• The administrator of the software is capable of
converting one physical server into various virtual
servers.
• Later these several servers are capable of using
the processing power of all machines.

• The computer’s CPU can run various processors,


which offer the capability to run many complex
tasks efficiently.
Advantages of Server Virtualization
1. Economic
• When the division takes place in the physical server is partitioned
into multiple virtual machines, they then further and then several
operating system instances can launch, operate, and be managed
inside the physical servers.
• Thus, using a less physical server will help in reducing the cost of
the server, and as a result, it will benefit the overall business.
2. Disaster Recovery
• The data virtually travels from one server to another quickly and
safely.
• Users can store the data at any location and retrieve it back from
anywhere. The following process takes less time, and also the
downtime is reduced.
3. Increased Productivity
• If the physical servers are fewer, then they are easy to
manage. So there are several tools available and will
convert the services smoothly.
4. Quick Deployment and Provisioning
• In some seconds, the user is capable of performing
provisioning and deployment tasks. Server
Virtualization permits replicating the existing Virtual
Machine.
5. Energy Consumption is reduced.
• Less Physical servers will lead to lower consumption
energy as they produce a lot of heat if it is not used
efficiently. It raises an important issue because of
environmental changes.
6. Affordable Web Hosting
• When multiple servers are adjusted on one computer, the servers
rise virtually, and there is no additional expenditure.
7. Increased Efficiency
• As there are fewer physical servers, the IT team will focus on those
specific servers and it will thereby benefit them to focus on critical
tasks and increase their efficiency.
8. Independent Restart of Each Server
• Every server can be restarted individually, which will not affect
other working servers.
9. Centralized Management
• Software Virtualization has centralized management, and there is
Full compatibility with the applications.
10. Migration
• In Server Virtualization, live Migration is possible from the servers,
and it can be carried out very quickly.
11. Easy to Update
• In Server Virtualization, installing, updating, and setting up the
software is done efficiently.
Disadvantages of Server Virtualization
• If any servers go offline because of technical issues, the
website hosted with its help will also be down.
• Users must manage the Virtual Machines accurately by
configuring and monitoring the movements.
• The RAM requirement is more as RAM consumption
increases as every Virtual Machine will occupy its
location.
• The disk space also increases during the increase of files
in virtual machines.
• Several links in a Single-chain must work together.
• When several virtual machines perform their operations
together under the same host, their performance might get
affected.
• The cost of software licenses may be an issue.
Virtualization software
• Virtualization software allows a single
host computer to create and run one or
more virtual environments.
• Virtualization software is most often used
to emulate a complete computer system in order
to allow a guest operating system to be run, for
example allowing Linux to run as a guest on top
of a PC that is natively running a Microsoft
Windows operating system (or the inverse,
running Windows as a guest on Linux).
• Storage virtualization refers to the process of
abstracting logical storage from physical storage.
• Some of the examples are VMware software,
Virtual Box etc.
• Software Visualization in Cloud
Computing allows the single computer server to
run one or more virtual environments.
• It is quite similar to virtualizations but here it
abstracts the software installation procedure and
creates a virtual software out of it.
• In software virtualizations, an application will be
installed which will perform the further task.
• One software is physical while others are virtual
as it allows 2 or more operating system using only
one computer.
Benefits of Software Virtualization
Here, is the list of Software Virtualization Advantages in Cloud
Computing :
1. Testing
• It is easier to test the new operating system and software on VMs as it
does not require any additional hardware and the testing can do within
the same software.
• After the testing, the VM can move or delete for the further testing.
2. Utilization
• In software virtualization, there is higher efficiency in resource
utilization if it tunes correctly.
• The VM can modify as per the requirement such as the user can
modify ram, drive space, etc.
• It requires very less amount of hardware as compared to the
equivalent number of physical machines.
3. Efficient
• It is efficient in a way such that it can run 12 virtual machines and
eliminates the use of 12 physical boxes.
• This is the power cost as well as the cost of maintaining the server.
4. Less Downtime
• The software is upgrading and the upgrade in the VMs can do when
the VM is working.
• VM can modify when it is working or it is not working which means
that the downtime of it is very less.
5. Flexible
• It provides flexibility to the user so that the user can modify the
software as per their demand.
• The modification can do within minutes and can adjust easily when
the workload changes.
6. Secure
• It can protect with many hantaviruses. Moreover, there are several
firewalls which prevent hacking and virus.
• The data in the software virtualization is safe as it stores in several
different places so if the disaster takes place the data can retrieve
easily.
Working
i. Backup
• With the help of software virtualization, the
entire operating system or server installation can
be backed up.
• This also benefits in a way that if the new server
hack just restoring the previous version will allow
running the server.
ii. Run multiple operating systems
• The different operating system can use in a single
computer with the partition in the hard drive.
• The only thing to keep in mind is to keep a
snapshot of everything. If the data drowns, it can
retrieve from some other place.
iii. Running a different version of applications
• With the help of software virtualization new
as well as the old operating system can use.
• So a program, if it is not working on a
particular operating system, we can check it
on another one.
iv. Templates
• After the configuration of VM as per the
demand, it can convert into a template and
this template can use to make multiple copies
of the original one.
Types of Software Virtualization
• Operating System Virtualization
• Application Virtualization
• Service Virtualization
i. Operating System Virtualization
• In operating system virtualization, the hardware is used which
consists of software on which different operating systems work.
• Here, the operating system does not interfere with each other so
that each one of them works efficiently.
ii. Application Virtualization
• Application virtualization is a technology, encapsulates the
computer program within the operating system.
• It can say that application virtualizations refer to running an
application on a thin client.
• This thin client runs an environment, which is different from what
refer to as encapsulating from the operating system which is the
location of it.
iii. Service Virtualization
• In the service virtualization, the DevOps team
can use the virtual servers rather than the
physical one.
• It emulates the behaviour of essential
components which will be present in the final
production environment.
Load balancing
• Most commonly, the term load balancing
refers to distributing incoming HTTP requests
across Web servers in a server farm, to avoid
overloading any one server.
• Because load balancing distributes the requests
based on the actual load at each server, it is
excellent for ensuring availability and
defending against denial of service attacks.
• Load balancing is a computer networking
methodology to distribute workload across multiple
computers or a computer cluster, network links,
central processing units, disk drives, or other
resources, to achieve optimal resource utilization,
maximize throughput, minimize response time, and
avoid overload.
• Using multiple components with load balancing,
instead of a single component, may increase
reliability through redundancy.
• The load balancing service is usually provided by
dedicated software or hardware, such as a multilayer
switch or a Domain Name System server.
Why is load balancing of servers
needed?
• Load balancing is especially important for
networks where it's difficult to predict the
number of requests that will be issued to a
server.
• Busy Web sites typically employ two or more
Web servers in a load balancing scheme.
• If one server starts to get swamped, requests are
forwarded to another server with more capacity.
• Load balancing can also refer to the
communications channels themselves.
• If there is only one web server responding to all
the incoming HTTP requests for your website,
the capacity of the web server may not be able to
handle high volumes of incoming traffic once
the website becomes popular.
• The website's pages will load slowly as some of
the users will have to wait until the web server is
free to process their requests.
• The increase in traffic and connections to your
website can lead to a point where upgrading the
server hardware will no longer be cost effective
• In order to achieve web server scalability, more
servers need to be added to distribute the load
among the group of servers, which is also known
as a server cluster.
• The load distribution among these servers is
known as load balancing.
• Load balancing applies to all types of servers
(application server, database server), however, we
will be devoting this section for load balancing of
web servers (HTTP server) only.
How?
• When multiple web servers are present in a server
group, the HTTP traffic needs to be evenly distributed
among the servers. In the process, these servers must
appear as one web server to the web client, for example
an internet browser.
• The load balancing mechanism used for spreading
HTTP requests is known as IP Spraying.
• The equipment used for IP spraying is also called the
'load dispatcher' or 'network dispatcher' or simply, the
'load balancer'.
• In this case, the IP sprayer intercepts each HTTP
request, and redirects them to a server in the server
• Depending on the type of sprayer involved, the
architecture can provide scalability, load balancing and
fail-over requirements.
Load Balancing Approaches
• Load balancing of servers by an IP sprayer can
be implemented in different ways.
• These methods of load balancing can be set up
in the load balancer based on available load
balancing types.
• There are various algorithms used to distribute
the load among the available servers.
1. Random Allocation
• In a random allocation, the HTTP requests are
assigned to any server picked randomly among
the group of servers.
• In such a case, one of the servers may be
assigned many more requests to process, while
the other servers are sitting idle.
• However, on average, each server gets its share of
the load due to the random selection.
• Pros: Simple to implement.
• Cons: Can lead to overloading of one server
while under-utilization of others.
2. Round-Robin Allocation
• In a round-robin algorithm, the IP sprayer assigns the
requests to a list of the servers on a rotating basis.
• The first request is allocated to a server picked randomly
from the group, so that if more than one IP sprayer is
involved, not all the first requests go to the same server.
• For the subsequent requests, the IP sprayer follows the
circular order to redirect the request. Once a server is
assigned a request, the server is moved to the end of the list.
• This keeps the servers equally assigned.
• Pros: Better than random allocation because the requests
are equally divided among the available servers in an
orderly fashion.
• Cons: Round robin algorithm is not enough for load
balancing based on processing overhead required and if
the server specifications are not identical to each other in
the server group.
3. Weighted Round Robin
• Weighted Round-Robin is an advanced version of the
round-robin that eliminates the deficiencies of the plain
round robin algorithm.
• In case of a weighted round-robin, one can assign a
weight to each server in the group so that if one server
is capable of handling twice as much load as the other,
the powerful server gets a weight of 2.
• In such cases, the IP sprayer will assign two requests to
the powerful server for each request assigned to the
weaker one.
• Pros: Takes care of the capacity of the servers in the
group.
• Cons: Does not consider the advanced load balancing
requirements such as processing times for each
individual request.
4. Dynamic Round Robin (Called
Dynamic Ratio on the BIG-IP)
• It is similar to Weighted Round Robin, however,
weights are based on continuous monitoring of
the servers and are therefore continually
changing.
• This is a dynamic load balancing method,
distributing connections based on various aspects
of real-time server performance analysis, such as
the current number of connections per node or the
fastest node response time.
• This Application Delivery Controller method is
rarely available in a simple load balancer.
• The configuration of a load balancing software or
hardware should be decided on the particular
requirement.
• For example, if the website wants to load balance
servers for static HTML pages or light database driven
dynamic webpages, round robin will be sufficient.
• However, if some of the requests take longer than the
others to process, then advanced load balancing
algorithms are used.
• The load balancer should be able to provide intelligent
monitoring to distribute the load, directing them to the
servers that are capable of handling them better than the
others in the cluster of server.
What is a Virtual Infrastructure?
• A virtual infrastructure allows you to utilize
the IT capabilities of physical resources as
software that can be used across multiple
platforms.
• These resources are shared across multiple
virtual machines (VMs) and applications for
maximum efficiency, creating a virtual
infrastructure.
• The main purpose of a virtual infrastructure is to
bring enterprise-level technology to organizations
that cannot afford the large capital required to pay
for the hardware, software licenses, setup and
continual maintenance of an actual data center
infrastructure.
• The technology involves virtualization, which is
the utilization of physical server resources to host
logical or virtual servers and networking hardware
in order to optimize resources and drive costs
down by hosting multiple virtual servers in a
single host server.
• The idea is that no single server is actually taxed
enough to the point that its resource limits are
reached so it would be more prudent to make use
of these resources by running multiple logical
servers that, together, can make use of the actual
capacity of the host.
• This lean approach allows for sharing and
distributing resources, which, in turn, promotes
flexibility, scalability and lower total cost of
ownership.
Virtual Infrastructure consists of the following
components:
• Bare-metal hypervisors to enable full
virtualization of each computer
• Virtual infrastructure services such as resource
management and consolidated backup to optimize
available resources among virtual machines
• Automation solutions that provide special
capabilities to optimize a particular IT process
such as provisioning or disaster recovery
Benefits of a virtual infrastructure:
• Scalable – Allows provisioning as many or as few logical
servers as required, and users only pay for what they use.
• Flexible – Allows for multiple server and networking
configurations as compared to a hardwired physical
infrastructure, which requires more capital and effort to
change.
• Secure – Allows more security to be layered on top of
whatever security is already present in the virtual
infrastructure because all traffic to the virtual infrastructure
goes through the actual physical infrastructure.
• Load balancing – Allows software-based servers to share
workloads easily and distribute them properly so that no
single logical server is taxed more than the others.
• Backup and recovery – Promotes easier backups because
everything can be saved somewhere, allowing for quick
recovery in other hosts if a few hosts are down. This is
almost impossible with physical servers, which have to be
revived before services can resume.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy