Virtualisation

You might also like

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 57

Cloud & Virtualization

Chapter 1: Virtualization types

1
Objectives
 Chapter 1: Virtualization Types
 Chapter 2 : Hypervisor Types(WS)
 Chapter 3 : Virtualization in the cloud
 Chapter 4 : IaaS solutions(WS)
 Chapter 5 : Network virtualization
 Chapter 6 : The Libvirt API
 Chapter 7 : Virtual Desktop Infrastructure (VDI)

2
Objectives
 Chapter 8: Sunray network terminal(WS)
 Chapter 9 : VMWare Vsphere&Vcenter(WS)
 Chapter 10 : Microsoft HyperV&SystemCenter(WS)
 Chapter 11 : Xen XCP (WS)
 Chapter 12 : KVM : OpenStack (WS)

3
Preface

Before we place a foot firmly into the realm of


virtualization technologies that exist today, it’s worthwhile
to take a step back into history to explore the origin of
virtualization within the mainframe environment. This is
important because virtualization in its current incarnation
is not a completely new technology and has roots in
some past efforts.

4
Introduction to virtualization

5
IBM
M4
4 1960

VM
wa r
e (X
8 6)

MS
1999
v irtu
al P
Cv
mw
History timeline

a re
E SX
X EN
2001
par
a virt
u al
is a t
io n

Ext
2003
e ns
io n
VT-
x AM
D-V
2005

KVM
2007
MS
Hyp
e rV
2008
6
Virtualization history

 The concept of virtual memory dates to the late 1950s when a


group at the University of Manchester introduced automatic page
replacement in the Atlas system, a transistorized mainframe
computer,

 The term virtual machine dates to the 1960s. Around 1967, IBM
introduced the System/360 model 67 (CP/CMS, VM/CMS), its first
major system with virtual memory. Integral to the model 67 was the
concept of a self-virtualizing processor instruction set, perfected in
later models into the virtual machine (VM) operating systems.

7
Virtualization history (…)

 In the 1970s, Hardware virtualization was pioneered on IBM


mainframes

 The 1990s saw an explosion of emulation on x86 architecture and


a remarkable growth in the number of servers used throughout the
enterprise,

 The 2000’s, Development of virtualization software to improve the


advancement of (AMD/INTEL) hardware solutions,

8
What is virtualization ?

9
Definition of virtualization

 Virtualization is a technique to abstract the physical


characteristics of computing resources to simplify the
way in which other systems, applications, or end users
interact with those resources,

 Virtualization present a logical view of these resources


which may be strikingly different from the physical one.

1
0
Virtualization Goals

The goal of virtualization is usually one of the following:

 Higher levels of performance,

 scalability,

 reliability/availability,

 agility,

 Create a Unified security And Management domain.


1
1
Virtualization types

There are three types of virtualization which are :

 System-level virtualization

 Process-level Virtualization

 OS Virtualization

1
2
System-level virtualization

 Emulates a computer similar to a real physical on,

 The virtual machine runs a full OS with CPU(s), memory,


disk(s), network interface(s), etc.

 Full Virtualization vs Paravirtualization

Examples: VMware, Xen, KVM

1
3
Process-level Virtualization

 Application has to be written specially for the VM

 Usually implemented on top of an operating system

Example: Java Virtual Machine

- Advantage
Application is portable among all platforms supporting the VM
 JVM on Windows, Linux, OS X, PDAs, phones . . .

- Disadvantage
Legacy applications have to be rewritten for the VM

1
4
Process-level Virtualization

 The virtual machine runs a set of userland processes

 Userland domains are separated

 Kernel is the same for all userland domains

Example: OpenVZ, Solaris zones, FreeBSD jails

1
5
Advantages of virtualization

1
6
What could we virtualize ?

1
7
Virtualization approaches

1
8
1. Compute / processing

1
9
Processing virtualization

What Does Processing Virtualization Do?

 Making many systems appear to be one

 Make many machines execute the same application or


application components

 Reduce the processing time of the application

 Make the applications extremely high available

 Fail recover
2
0
Parallel processing
Client Application
........
task1()
task2()
task3()
.......

System

Parallel processing monitor

Virtual System Virtual System Virtual System

task1()
task2() task3()

Database Engine Database Engine Database Engine

Operating System Operating System Operating System


21
Load Balancing monitors

(Workload management monitors)

Client

System

Load Balancing monitor

Virtual System Virtual System Virtual System

Application clone Application clone Application clone

Database Engine Database Engine Database Engine

Operating System Operating System Operating System


22
High availability/fail over/disaster recovery monitors

Client

System

High availability/fail over/disaster recovery monitors

Virtual System Virtual System Virtual System

Application clone Application clone Application clone

Database Engine Database Engine Database Engine

Operating System Operating System Operating System

23
What Does Processing Virtualization Do?

 Making one system appear to be many

 Optimizing CPU usage

 Share the system between many users

 Considerably reduce power consumption

2
4
Virtual machine software

Client Client Client

Virtual System Virtual System Virtual System

Application clone Application clone Application clone

Database Engine Database Engine Database Engine

Operating System Operating System Operating System

Type 1 or Type 2 Hypervisor

(Virtual machine software)


25
Virtual machine software

Client Client Client

Isolation
Virtual System Virtual System Virtual System

Application clone Application clone Application clone

Database Engine Database Engine Database Engine

Operating System Operating System Operating System

Type 1 or Type 2 Hypervisor

(Virtual machine software)


Processing Virtualization suppliers

 Citrix

 Microsoft

 VMware

 Oracle

 Open source community

2
7
virtualization

2. Storage

2
8
What Does Storage Virtualization Do?

 Allowing distributed file systems

 Remote storage devices are made to look like they


were directly attached to the system

!! The local system does not know where they are located
or what type of storage device they are.

2
9
What Does Storage Virtualization Do? (…)

 Creating artificial storage volumes

 Multiple storage devices can be harnessed together


to create the image of a single, much larger storage
device.
 Allowing incompatible systems to share storage
devices

 Enable mainframes, Windows, Linux, UNIX systems


to share the same storage devices
3
0
What Does Storage Virtualization Do? (…)

 Creating arrays of storage volumes

 Applications and data can be spread over a number


of storage devices and storage servers to improve
overall storage performance

 Improve storage reliability, data can be reconstructed


in case of failure

3
1
Distributed file systems
/
----/root
----/lib
----/usr
----/etc
----/home

/usr /etc /home


3
2
Artificial storage volumes

Artificial storage volume


Creating artificial storage volumes

File A 50% File A 50%

File B 50% File B 50%

File A File A

File B File B

34
Why do we use Storage Virtualization ?

 High availability/fail over/disaster recovery


 The storage server fails, storage virtualization can
press another device, network, or storage server
into service.

 Improve storage performance


 If the workload is spread over many different storage
devices, theworkload can be handled

 Making the same storage resource serve everyone

3
5
2. Networking

3
6
What does network Virtualization do ?

By using network virtualization solutions, network


resources can be deployed and managed as logical
services, rather than physical resources. As a result, we
can :
 Improve network efficiency.
 Increase Flexibility
 Reduce capital and operational costs.
 Maintain high standards of security, scalability,
manageability, and availability throughout the
campus design.

3
7
What does network Virtualization do ? (…)

Network virtualization also allows network aggregation


and provisioning, combining different physical networks
into a single virtual network, or breaking a physical
network into multiple virtual networks that are isolated
from each other. This is sometimes called "external
network virtualization.“

A good example of an external virtual network would be


VLAN technology

3
8
Virtual network Components

Various equipment and software vendors offer network virtualization


by combining any of the following:

 Network hardware, such as switches and network adapters, also


known as network interface cards (NICs)
 Network elements such as firewalls and load balancers
 Networks, such as virtual LANs (VLANs) and containers such as
virtual machines (VMs)
 Network storage devices
 Network M2M elements such as telecommunications 4G HLR
and SLR devices
 Network mobile elements such as laptops, tablets, and cell
phones
 Network media, such as Ethernet and Fibre Channel

3
9
Common network virtualization scenario

 Network virtualization allows network aggregation and


provisioning, combining different physical networks into a single
virtual network, or breaking a physical network into multiple virtual
networks that are isolated from each other. This is sometimes
called "external network virtualization.“

 A good example of an external virtual network would be VLAN


technology

 Network virtualization can also be applied within virtual servers to


create synthetic networks between virtual machines (VMs); this is
often dubbed "internal network virtualization.“

 A good example of an internal virtual network would be


VnetworkStack (Vyatta, Citrix) or opensolaris
4
0
Server/network virtualization view

4
1
Network Virtualization suppliers
 Cisco offers a number of network servers that perform
network virtualization functions.

 HP offers network virtualization functions as part of its


general-purpose server operating systems and also
offers network servers providing those functions.

 IBM offers network virtualization functions as part of its


general-purpose server operating systems and also
offers network servers providing those functions.

 Juniper Systems offers a number of network servers


that perform network virtualization functions. 4
2
Understanding Desktop Virtualisation

 In traditional desktop models, the computer runs an


operating system where individual applications are executed with
their user interface displayed on the computer screen.

 By introducing virtualization however, you break the direct


connection between physical hardware, operating system,
application and display.
43
Understanding Desktop Virtualisation

Display

Data and Settings

Apps Server
or Client

OS

Hardware

Traditional Desktop Model Virtualized Desktop Model


44
Desktop Virtualisation Principals

 With desktop virtualization, each user gets a virtual machine that


contains a separate instance of the desktop operating system and
whatever applications have been installed.

 VDI is different in that the user accesses a dedicated machine


(virtual machine) for their own use and not a shared desktop from
a server, as is the case with Terminal Services type solutions.

45
Client hypervisor
 A client hypervisor is a hypervisor that is installed on end user
laptops or desktop computers to provide the ability to run virtual
desktops locally in an Intelligent Desktop Virtualization (IDV)
solution.

 Server hypervisors don't have to worry as much about device


support because servers are relatively simple when it comes to
devices. Client hypervisors must support a much wider array of
devices as well as support a variety of buttons and unique
hardware on laptop computers. 46
Desktop Virtualisation benefits

+ It's completely secure and separate from whatever else may be


running on that desktop (such as a Trojan some clueless user
accidentally downloaded).

+ Get all the virtualization management advantages, including VM


snapshots, portability, easy recovery, and so on. Client hypervisors
also make VDI more practical.

47
Desktop Virtualisation benefits

+ Run off virtual machine on a laptop and compute without a


connection; then when the connection is established again, the
client VM syncs with the server VM.

48
Understanding hypervisors

 The hypervisor, also known as a Virtual Machine Monitor


(VMM) is the software layer which enables virtualization.

 It is responsible for creating the virtual environment on which


the guest virtual machines operate.

 It supervises the guest systems and makes sure resources


are allocated to the guests as necessary.

49
Type 1 hypervisor
 The Type 1 hypervisor is considered a native or bare metal
hypervisor. This type of hypervisor is the lowest level
hypervisors, running directly on the host hardware

 It is responsible for allocation of all resources (disk, memory,


CPU, and peripherals) to its guests.

50
Type 1 hypervisor

Performance improvement because they are self-hosted with


embedded OSs that are optimized for virtualization.

The bare metal machine becomes dedicated for the sole


purpose of being a hypervisor. They are not able to provide other
roles; simply they are dedicated to the task of being a hypervisor
and a hypervisor alone.

51
Type 2 hypervisor

 The Type 2 hypervisor requires a full host operating system in


order to operate. That is to say that it is installed on top of the
host operating system.

 Guest operating systems then run within virtual machines


above the hypervisor

 This type of virtualization is typically referred to as hosted


virtualization. 52
Type 2 hypervisor

It has fewer hardware/driver issues as the host operating system is


responsible for interfacing with the hardware.

Weak in reliability and security because they inherit the


vulnerabilities of the user- controlled host operating system. 53
Monolithic hypervisor

 Monolithic hypervisor design involves using hypervisor-aware


device drivers that are hosted within and managed by the hypervisor

54
Monolithic hypervisor

Monolithic hypervisors do not need a controlling, or parent,


operating system because all guest operating systems interact directly
with the underlying physical hardware of the host computer by using
hypervisor-aware device drivers. This is an example of the benefit of
the monolithic design.

Vendors of monolithic hypervisor platforms are dependent on


manufacturers of hardware devices to supply such drivers for their
products. The result is that the number of devices that can be used in
virtualized operating system environments running on monolithic
hypervisor platforms can be more limited than when those same
operating system environments are run directly on physical
computers. 55
MicroKernel hypervisor
 Microkernel hypervisors do not require hypervisor-aware device
drivers because they have an operating system acting as the root, or
parent, partition. This parent partition then provides the execution
environment needed for device drivers to access the underlying
physical hardware of the host computer.

56
Microkernel hypervisor

Because microkernel hypervisors do not need hypervisor-aware


drivers, they can immediately use the wide range of existing drivers
that are available from device manufacturers

The attack surface is minimized because foreign code is not


loaded in the hypervisor.

The only downside of the microkernel design is that a special


partition, the parent partition, is required. This adds measurable (but
usually minimal) overhead to your system because of
the communication between parent and child partitions that is required
to allow the child partitions to access the hardware through the parent.
57

You might also like