How it can help your organisation

History

Types of Virtualisation & Hypervisors

Virtualisation Features

Why Virtualisation?

Virtualising Oracle◦ Performance

◦ Licensing

◦ Support

Cloud

1998 ◦ VMware founded by Diane Greene, Dr. Mendel

Rosenblum and Ed Bugnion

1999◦ Workstation 1.0 released for Windows & Linux

2000◦ Workstation 2.0 released

2001◦ ESX 1.0 (Elastic Sky X) & GSX 1.0 (Ground Storm

X) released◦ Workstation 3.0 released

2004◦ 1st VMworld conference in San Diego, CA (1,400

attendees)◦ ESX 2.5 released◦ GSX Server 3.0 released◦ VMTN technical communities launched◦ EMC Acquires VMware

2005◦ 2nd VMworld conference (3,500 attendees)◦ Player 1.0 released◦ P2V Assistant 2.0 released◦ Workstation 5.0 & 5.5 released

2006

◦ 3rd VMworld conference (6,700 attendees)

◦ VI3 released with ESX 3.0 & VirtualCenter 2.0

◦ Server 1.0 released (replaced GSX Server)

2007

◦ 4th VMworld conference (10,800 attendees)

◦ ESX 3i released

◦ Fusion 1.0 for Mac released

◦ ESX 3.5 & VirtualCenter 2.5 released

◦ Workstation 6.0 released

2008

◦ 5th VMworld conference (14,000 attendees)

◦ Fusion 2.0 released

◦ VMware Server 2.0 released

◦ Workstation 6.5 released

◦ ESXi becomes available for free

◦ Paul Maritz takes over as CEO from Diane Greene

2009

◦ vSphere ESX 4 released

Server Virtualisation

Desktop Virtualisation

Presentation Virtualisation

Application Virtualisation

What is a hypervisor?

A hypervisor, also called a virtual machine manager (VMM), is a program that allows multiple operating systems to share a single hardware host.

Each operating system appears to have the host's processor, memory, and other resources all to itself.

Type 1 Hypervisor (Bare Metal)

Runs directly on a given hardware platform controlling the operating system environment. Eg: VMware's ESX Server, Hyper-V and Xen.

Type 2 hypervisor (Hosted)

Runs inside an operating system environment. Eg: VMware Server, Microsoft Virtual Server and PC Virtualisation products like VMware Fusion, Parallels for Mac and Virtual PC.

Client hypervisor (New)

1. Traditional 1.

2. Hosted Virtualisation

3. Bare-metal Virtualisation

2. 3.

Overhead of a full general-purpose operating system between the virtual machines and the physical hardware results in performance 70-90-% of native

ESX install right on the bare metal and therefore offers higher performance but runs on a narrower range of hardware.

Used for server consolidation for Data Centers

High performance and scalability

Many advanced features for resource management, high availability and security

Centralized administration with vCenter Server

Supports more VMs per physical CPU then hosted products do.

The hypervisor or VMM is referred to as the VMKernel in ESX & ESXi

Because there is no overhead from a full host operating system performance is 83-98% of native. There is a small bit of overhead from the Virtualisation layer of the VMKernel.

VMFS is VMware's unique clustering file system which allows for multiple hosts to read and write from the same storage location concurrently.

It has adaptive block sizing and uses both large block sizes favored by virtual disk I/O and sub-block allocation for small files and directories.

Uses on-disk disk file locking to ensure that the same virtual machine is not powered on by multiple servers at the same time.

The virtual SMP (vSMP) feature allows you to assign more than one virtual CPU to a virtual machine. Up to 8 virtual CPUs can be assigned to any virtual machines.

VMotion allows you to quickly move an entire running virtual machine from one host to another without any downtime or interruption to the virtual machine This is also known as a “hot” or “live” migration.

1. Migration request is made to move the virtual machine from ESX1 to ESX2.

2. vCenter Server verifies that the virtual machine is in a stable state on ESX1 and

checks the compatibility of ESX2 (CPU, networking, etc.) to ensure that it

matches that of ESX1.

3. The virtual machine is registered on ESX2.

4. The virtual machine state information (including memory, registers and network

connections) is copied to ESX2. Additional changes are copied to a memory

bitmap on ESX1.

5. The virtual machine is quiesced on ESX1 and the memory bitmap is copied to

ESX2.

6. The virtual machine is started on ESX2 and all requests for the virtual machine are

now directed to ESX2.

7. A final copy of the virtual machines memory is done from ESX1 to ESX2.

8. The virtual machine is un-registered from ESX1.

9. The virtual machine resumes operation on ESX2.

Storage VMotion allows you to migrate a running virtual machine and its disk files from one datastore to another on the same ESX host

The difference between VMotion and Storage VMotion is that VMotion simply moves a virtual machine from one ESX host to another but keeps the storage location of the VM the same, Storage VMotion on the other hand changes the storage location of the virtual machine while it is running and moves it to another datastore on the same ESX host

1. New virtual machine directory is created on the target datastore, virtual machine configuration files and all non-virtual disk files are copied to the target directory.

2. ESX host does a “self” VMotion to the target directory.

3. A snapshot (without memory) is taken of the virtual machines disks in the source directory.

4. Virtual machine disk files are copied to the target directory.

5. Snapshot that is located in the source directory is consolidated into the virtual machine disk files located in the target directory.

6. Source disk files and directory are deleted.

Continuously monitors all hosts in a cluster and restarts virtual machines affected by a host failure on other hosts

Can also monitor guest OS's for a failure via a heartbeat and restart them on the same host in case of a failure

DRS enables your virtual environment to automatically balance itself across your host servers in an effort to eliminate resource contention.

Distributed Power Management (DPM) (experimental) can consolidate workloads and power off hosts during periods of low activity. When activity increases DPM brings hosts back online so service levels can be met.

Update Manager

Consolidated Backup

Fault Tolerance

So what exactly is a virtual machine?

A virtual machine is defined as a representation of a physical machine by software that has its own set of virtual hardware upon which an operating system and applications can be loaded.

Virtual machines provide:

◦ Hardware independenceVM sees the same hardware regardless of the host hardware

◦ IsolationVM’s operating system is isolated from the host operating system

◦ EncapsulationEntire VM encapsulated into a single file

A virtual machine is comprised of a number of files that are located in it's home directory.

Low utilization metrics in servers across the organization…

Too many servers for too little work

Aging hardware reaching end of usable life

High infrastructure requirements

Limited flexibility in shared environments

High costs and infrastructure needs◦ Maintenance

◦ Leases

◦ Networking

◦ Floor space

◦ Cooling

◦ Power

◦ Disaster Recovery

Reduced costs through server consolidation that uses fewer servers

Higher availability through automatic restart of critical servers

Better load balancing

No downtime for maintenance through the use of VMotion to evacuate servers when fixes are required

Portability

Easier planning and implementation of disaster recovery

One-to-One phase is over

Nothing technical that stop people from deploying Oracle

RISK/SPARC/SOLARIS - Big VMware customers moving to x86 platform and happy with results

Technology has changed (Intel Nehalem & VT)

Best Practices & tunning was critical, not the case anymore

2 – 10% overhead with a fully loaded database in vSphere

Treat virtual instance as you would treat physical database.

“98% of the content contained in Oracle optimisation and tuning books directly

transfer over to the virtual world”

Oracle on VMware – Expert tips for database virtualisation (by Bert Scalzo)

Virtualizing Performance-Critical Database Applications in VMware® vSphere™http://www.vmware.com/pdf/Perf_ESX40_Oracle-eval.pdf

Very Confusing? Biggest Issue?

Oracle x86: you license the entire box

per user (not many people use it)

New servers with 32 cores would have to be fully licensed

Oracle sub-license cores in the Sparc/Solaris space

Oracle will do best effort support on virtualized environments

Since Jan 13, 2010, Oracle supports SAP production landscapes on Oracle DB single instance (no RAC) virtualized with VMware ESX 3.5 and higher.

No support for Oracle RAC

Virtual Machines on-Demand

Encapsulation and on-demand deployment of multiple VMs as a single entity

Encapsulation and on-demand deployment of whole software stacks (e.g. LAMP, Ruby on Rails, .NET, etc.)

Encapsulation and on-demand deployment of entire multi-tiered apps

Cloud-to-Cloud VMotion & sVMotion

Blog: http://myvirtualcloud.net

andre_leibovici@yahoo.com

Twitter: @andreleibovici

http://www.vmware.com/oracle

http://communities.vmware.com/community/viops