Embed Size (px)
DESCRIPTION
Citation preview
Agenda
• Problems with servers• Machine Virtualisation• Hyper-V• Licensing• Clustering• Management• Windows Server 2008 R2• The Future?
About Aidan Finn• Systems & IT Infrastructure Manager• C Infinity• Microsoft Partner• Data Protection Services, e.g. Secure Online
Backup and Data Encryption – Iron Mountain• Outsourced Monitoring• Managed Server Hosting
• MCSE & MVP (ConfigMgr)• Email: [email protected]• Web: http://www.cinfinity.ie• Blog: http://joeelway.spaces.live.com• Windows User Group: http://ws-ugi-
spaces.live.com
Problems With Servers
Traditional Server Deployment• 1 piece of hardware, 1 operating
system, 1 machine• Worldwide average CPU utilisation of
8%• CPU is greatest power consumer• Fans not far behind• Wasted hardware, rack space and
cooling• Slow time to acquire and deploy• Machines tied to hardware• Not very green AKA wasted money
Machine Virtualisation
What Is It?
• Use software to carve up hardware resources into simulated machines
• Each virtual machine is independent machine
• 1 operating system per virtual machine
• Host based or hypervisor
Consolidate The Data Centre
Hyper-V
Microsoft’s Hyper-V
• Microkernelised Hypervisor• A role in Windows Server 2008*• Tiny footprint• Enterprise solution• Focus on integrated and complete
management
*Do not use the installer on the RTM/SP1 media
Hardware Requirements
• Windows Server 2008 supported hardware
• x64 Processor (Windows Server x64 only)
• Can enable in the BIOS:• CPU assisted virtualisation• Data Execution Prevention (DEP)• Both are usually rebranded by OEM’s
Hypervisor Types• Monolithic hypervisor
• Simpler than a modern kernel, but still complex
• Contains its own drivers model
• Microkernelised hypervisor• Simple partitioning functionality• Increase reliability and minimise TCB• No third-party code
VM 1(“Admin”)
VM 3
Hardware
Hypervisor
VM 2(“Child”)
VM 3(“Child”)
VM 1(“Parent”)
DriversDriversDriversHypervisor
VM 2
Hardware
DriversDriversDrivers
Microkernelised Hypervisor has an inherently secure architecture with minimal attack surface
Traditional Approach Hyper-V Approach
Architecture
Applications Applications Applications
Non-Hypervisor Aware OS
Windows Server 2008, 2003
Windows Kernel VSC
VMBus Emulation VMBus
“Designed for Windows” Server Hardware
Windows Server 2008, x64
Windows Kernel
Xen-Enabled Linux Kernel
Linux VSC
Hypercall Adapter
Parent Partition Child Partitions
VMBus
Hyper-V
VSP
VM Service
WMI Provider
VM Worker Processes
OS
ISV / IHV / OEM
Hyper-V
MS/ XenSource
User Mode
Kernel Mode
Windows Server 2008, x64
Windows KernelWindows
Drivers
Windows Drivers
Components
• Parent Partition: AKA Host OS• Child Partition: Virtual machine• Virtual Hard Disk (VHD): File that
simulates a hard disk• Virtual Network: Soft device like a
switch and binds to physical network. VM NIC binds to virtual network.
• Snapshot: Capture a VM’s state
Virtual Disk Options• Pass Through: VM uses a raw LUN.
Best performance.• Fixed Size: Fully expanded file with
near physical disk speed.• Dynamic: File grows as space is
required. Slow.• Differential: Points to a template VHD.
Grows to include differences to template.
• SCSI and IDE controllers.• Boot only from IDE – almost no speed
loss.
Networking
• No NIC teaming included by MS• OEM’s are working on this, e.g. HP• VLAN ID tagging can be done:
• At virtual network: All VM’s on the VLAN• At virtual machine: Fewer physical NIC’s and
virtual networks required
Licensing
Licensing
• Any copy of Windows Server except “Windows Server Without Hyper-V”
• Standard: no Failover Clustering & 1 free child license
• Enterprise: Failover Clustering & 4 free child licenses
• Data Center: Failover Clustering & unlimited free child licenses
• Hyper-V Server 2008: Free & no Failover Clustering
Clustering
Failover Clustering
• Uses Windows 2008 Failover Clustering for hardware fault tolerance
• Easier than ever – honestly!• Virtual machine treated as cluster
resource• Each VM should (not must) be on a
dedicated LUN: VMM 2008 requirement
• Quick Migration, not Live Migration (aka VMotion)
Quick Migration
• Simple process:• VM saves its state• Disk fails over to destination host• VM restores its saved state
• Takes 8 seconds on 4GB Fibre Channel SAN with 15K SCSI disks, e.g HP EVA SAN
• Supported with Fibre Channel and iSCSI
• Test labs will work with W2008 file shares
• Live Migration coming in W2008 R2!
Failover Scenarios
• You want to work on a host• Quick Migration*
• A host fails• Failover and VM boots up
• VMM 2008 Pro Tips (coming up next)• Quick Migration*
* Live Migration in W2008 R2
Management
Management
• Microsoft’s strategy for differentiation• Basic management using Hyper-V and
Failover Clustering MMC’s• Advanced virtualisation management
using System Center Virtual Machine Manager (VMM) 2008
• VMM 2008 integrates with OpsMgr 2007
• Purchase per host System Center Enterprise CAL: includes all VM’s
VMM 2008
• Based on PowerShell• Easier cluster management• Hardware templates• Library for VHD’s, PowerShell scripts,
ISO• Self Service web console• Can managed ESX and many Virtual
Center installations• Integrates with OpsMgr 2007 SP1• Use hardware OEM Pro Tips for
hardware view of performance
Windows Server 2008 R2
Versions
• Windows Server Standard, Enterprise and Data Center: Same as before
• Hyper-V Server 2008 R2: Adds Cluster Shared Volumes and Live Migration
Clustered Shared Volumes
• Clustered Shared Volumes (CSV) implements hybrid sharing for LUNs• One node owns the storage namespace (e.g. directory
structure) and metadata• Other nodes can own the storage backing an individual
file’s data (e.g. VHD)
• Benefits of CSV:• Can store all VM VHDs on one LUN• High-performance access to VHDs from owning nodes• All nodes have read/write access to file data
• Seamless VM movement between nodes • Any node can read from VHD, so no need to change LUN
ownership• Seamless LUN ownership transition• Persistent handles allow cluster to move LUN without
interruption to VM operation
Live Migration1. Create VM on target server
Host 1 Host 2Blue = StoragePurple = Networking
Shared Storage
3. Final state transfera) Pause virtual machineb) Move storage connectivity from source host to target host via Ethernet
4. Run new VM on target; Delete VM on source
2. Copy memory pages from the source to the target via Ethernet
Live Migration State Transfer
Server 1 Server 2
Config
ura
tio
n
Memory
Config
ura
tio
n
Sta
teSta
te
Other New Features
• Virtual Machine Queue: offload NW processing
• Power management: Core Parking• Second Level Address Translation
(SLAT): CPU and RAM improvements for memory management
• Native VHD: boot from a VHD
The Future?
Lots Of Guess Work Here!• VHD
• Strategic direction• Boot from VHD: P2V and V2P?• All servers using Native VHD?
• Guest OS Support• Microsoft busy forming support relationships• SUSE Enterprise in place• RedHat on the way• More TBA – sorry, NDA!
• RAM oversubscription: Not in W2008 R2
• Microsoft already asking people for Windows 8 suggestions
