VIRTUALIZATION 101. Brainstorm Conference 2013 PRESENTER INTRODUCTIONS

Transcription

1 VIRTUALIZATION 101 Brainstorm Conference 2013 PRESENTER INTRODUCTIONS Timothy Leerhoff Senior Consultant TIES 21+ years experience IT consulting 12+ years consulting in Education experience 1

2 THE QUESTION What is Virtualization, and Why Should You Care? WHAT IS VIRTUALIZATION? Wikipedia: A technique for hiding the physical characteristics of computing resources from the way in which other systems of end users interact with those resources 2

3 ALSO WHAT IS THIS CLOUD THING? Enterprises The Cloud is a way of doing computing Bridging Cloud Service Providers Private Cloud Operated Solely for an organization typically within a firewall Hybrid Cloud Composition of 2 or more interoperable clouds, enabling data and application portability Public Cloud Accessible over the Internet for general consumption TYPES OF VIRTUALIZATION Desktop Application Server 3

4 DESKTOP VIRTUALIZATION DEFINITION Server-centric computing model that borrows from the traditional thin-client model but is designed to give system administrators and end-users the best of both worlds: the ability to host and centrally manage desktop virtual machines in the data center while giving end users a full PC desktop experience. The user experience is intended to be identical to that of a standard computer. You gain access to the desktop (console) from most any device, as if you are using a KVM over Ethernet.. APPLICATION VIRTUALIZATION DEFINITION Umbrella term that describes software technologies that improve portability, manageability and compatibility of applications by encapsulating them from the underlying operating system on which they are executed. ' A fully yirtualized application is not installed in the traditional sense, although it is still executed as if it is. The application is fooled at runtime into believing that it is directly interfacing with the original operating system and all the resources managed by it, when in reality it is not. 4

5 SERVER VIRTUALIZATION DEFINITION Masking of server resources (including the number and identity of individual physical servers, processors and operation systems} from server users. The intent is to spare the user from having to understand and manage complicated details of server resources, while increasing resource sharing and average utilization while maintaining the capacity to expand later. FOR THOSE MORE VISUALLY INCLINED. Traditional Architecture Virtual Architecture 5

6 WHY SHOULD YOU CARE? Virtualization can help you shift your IT focus Save money. Save energy. Save time. DO YOU HAVE ONE OR MORE OF THESE ISSUES? Too many physical servers doing too little work Aging hardware reaching end of usable life High infrastructure requirements Limited flexibility in shared environments Need to run multiple OS for needed services 6

7 PROBLEM ASSESSMENT High costs and infrastructure needs Maintenance Leases Networking Floor space Cooling Power Disaster Recovery LABOR IS 1/3 OF THE COSTS OF A SERVER Cooling and Cost of Space - 10% Administrative - 33% Storage and Network - 12% Server Amoritization - 44% 7

8 PROBLEM ASSESSMENT Low utilization metrics in servers across the organization Server CPU utilization normally runs at a high of 5-15% HOW DOES VIRTUALIZATION HELP WITH THESE ISSUES? Consolidation of physical servers Run legacy software Sandbox untrusted software Run multiple OS on same hardware simultaneously Debug and performance monitoring Fault containment Migrating OS 8

9 SERVER VIRTUALIZATION ADOPTION 2007 Virtualization Adoption 2011 Virtualization Adoption 4.90% 1.75% 0.35% Non-virtualized servers VMware 8% 10% Non- Virtualized Servers VMware 93.00% Microsoft Other 19% 63% Microsoft Other VIRTUALIZATION TERMS AND ACRONYMS Host The physical hardware VM or Virtual Machine the logical representation of a server Guest - a system that is operating in a virtual machine Hypervisor - presents to the guest operating systems a virtual operating platform and manages the execution of the guest operating systems. Abstraction Layer a way of hiding the actual hardware details from the VMs vswitch Virtual Switch vcenter Virtual Center, management center for all hosts/vms in VMware VDI Virtual Desktop Interface vapp Virtualized Application 9

10 CORE TECHNOLOGY The Hypervisor A computing layer which allows multiple operating systems to run on a host computer at the same time. Originally developed in the 1970s as part of the IBM S/360 Many modern day variants from different developers THE HYPERVISOR Conceptual diagram of typical server configuration without virtualization 10

11 THE HYPERVISOR The role of the Hypervisor in supporting Guest Operating Systems on a single machine. ADDING SERVERS More physical servers More power consumption More cooling More space in the data center More hardware maintenance Single server single load Singular OS on a hardware platform Slow to deploy new servers... 11

12 VIRTUALIZED SERVERS Less physical servers Less power to run Less cooling needed Less space in the data center Less hardware maintenance Load sharing Multiple OS on same hardware SOME THINGS TO CONSIDER Since virtualization makes it easy to set up new virtual servers, you may end up with a lot of new VM servers to manage. Virtualization isn t a magic bullet for everything. For all of the upside virtualization isn t magic, and it can introduce some new challenges. You may need new shared storage 12

13 SERVER VIRTUALIZATION SETS THE STAGE Faster Project implementation Save up to 50% on storage, power, cooling, and datacenter space Scale your virtualized environment and accommodate data growth without degrading performance or investing in additional storage. Strategic planning is critical to your complete data center transformation. VIRTUAL MACHINES Virtual machines properties: Partitioning Hardware independence Isolation Encapsulation 13

14 VIRTUALIZATION OPTIONS TODAY VMware ESXi Microsoft HyperV XEN KVM VMWARE ESXI 5 Present version ESXi 5 Majority of market share ESXi is free vcenter is the management utility cost by CPU Licensing levels decides which features are available License Level Enterprise Plus Enterprise Standard Essentials Plus Essentials Feature added Distributed Switches, Storage DRS DRS, Storage vmotion, Distributed Power Management Higher vram entitlement vmotion, High Availability Hypervisor 14

15 HIGH AVAILABILITY (HA) 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 Continuously monitors and chooses the optimal physical servers within a resource pool on which to restart virtual machines (if used in conjunction with DRS) DISTRIBUTED RESOURCE SCHEDULER (DRS) DRS enables your virtual environment to automatically balance itself across your host servers in an effort to eliminate resource contention. It utilizes the VMotion feature to provide automated resource optimization and automatic migration of virtual machines across hosts in a cluster. 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. 15

16 VMOTION Ability to move a running VM to another host with the end user not noticing VMOTION - HOW IT WORKS 1. Migration request is made to move the virtual machine from one ESXi server to another ESXi server. 2. vcenter Server verifies that the virtual machine is in a stable state and checks the compatibility of the destination ESXi server (CPU, networking, etc.) 3. The virtual machine is registered on the destination server. 4. The virtual machine state information (including memory, registers and network connections) is copied to the destination server 5. The virtual machine is quiesced on originating ESXi server and the memory bitmap is copied to the destination server. 6. The virtual machine is started on the destination server and all requests for the virtual machine are now directed to it. 7. A final copy of the virtual machines memory is copied from the originating ESXi server to the destination server. 8. The virtual machine is un-registered from the originating server. 9. The virtual machine resumes operation on the destination server. 16

17 STORAGE VMOTION Storage VMotion was a new feature introduced in ESX 3.5, it 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. The virtual machine can be moved to any datastore on the ESX host which includes local and shared storage. STORAGE VMOTION - HOW IT WORKS 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. 17

18 MICROSOFT HYPER-V Hyper-V 28 Screen shot MICROSOFT HYPER-V Role and technology description The Hyper-V role enables you to create and manage a virtualized computing environment by using virtualization technology that is built in to Windows Server Installing the Hyper-V role installs the required components and optionally installs management tools. The required components include Windows hypervisor, Hyper-V Virtual Machine Management Service, the virtualization WMI provider, and other virtualization components such as the virtual machine bus (VMbus), virtualization service provider (VSP) and virtual infrastructure driver (VID). The management tools for the Hyper-V role consist of: GUI-based management tools: Hyper-V Manager, a Microsoft Management Console (MMC) snap-in, and Virtual Machine Connection, which provides access to the video output of a virtual machine so you can interact with the virtual machine. Hyper-V-specific cmdlets for Windows PowerShell. Windows Server 2012 includes a Hyper-V module, which provides command-line access to all the functionality available in the GUI, as well functionality not available through the GUI. For more information about the Hyper-V module, see Hyper-V Module for Windows PowerShell. 18

19 Maximums for running Hyper-V Server running Hyper-V. Component Maximum Notes Logical processors 320 Both of the following must be available and enabled in the BIOS: Hardware-assisted virtualization Hardware-enforced Data Execution Prevention (DEP) Virtual processors per logical processor Running virtual machines per server Virtual processors per server Memory No ratio imposed by Hyper-V TB Storage Limited by what is supported by the management operating system. No limits imposed by Hyper-V. Maximums for running Hyper-V Component Maximum Notes Virtual storage area networks (SANs) No limits imposed by Hyper-V None. Physical network adapters Network adapter teams (NIC Teaming) Virtual switches No limits imposed by Hyper-V. No limits imposed by Hyper-V. Varies; no limits imposed by Hyper-V. None. For more information about NIC Teaming in Windows Server 2012, see NIC Teaming Overview. The practical limit depends on the available computing resources. Virtual network switch ports per server Varies; no limits imposed by Hyper-V. The practical limit depends on the available computing resources. 19

20 Failover Clusters and Hyper-V The following table lists the maximums that apply to highly available servers running Hyper-V. It is important to do capacity planning to ensure that there will be enough hardware resources to run all the virtual machines in a clustered environment. For more information about requirements for failover clusters, see Failover Clustering Hardware Requirements and Storage Options. Component Maximum Notes Nodes per cluster 64 Consider the number of nodes you want to reserve for failover, as well as maintenance tasks such as applying updates. We recommend that you plan for enough resources to allow for 1 node to be reserved for failover, which means it remains idle until another node is failed over to it. (This is sometimes referred to as a passive node.) You can increase this number if you want to reserve additional nodes. There is no recommended ratio or multiplier of reserved nodes to active nodes; the only specific requirement is that the total number of nodes in a cluster cannot exceed the maximum of 64. Running virtual machines per cluster and per node 8,000 per cluster Several factors can affect the real number of virtual machines that can be run at the same time on one node, such as: Amount of physical memory being used by each virtual machine. Networking and storage bandwidth. Number of disk spindles, which affects disk I/O performance. XEN Released in 2002 More established than KVM supports x86, x86_64, Itanium, and ARM architectures Two flavors, open source and developed by Citrix 20

21 KVM KVM - Kernel-based Virtual Machine New guy on the block - catching up quickly with XEN Linux based Open Source To make it work, you need to get the right version for three components: Linux Module kvm kvm kvm-22 User Space Application Guest Virtio Driver 21

22 DISASTER ARTICLE 4 PARTS QUESTIONS? 22

23 VMWARE ESXI 5 Present version ESXi 5 Majority of market share ESXi is free vcenter is the management utility cost by CPU Licensing levels decides which features are available License Level Enterprise Plus Enterprise Standard Essentials Plus Essentials Feature added Distributed Switches, Storage DRS DRS, Storage vmotion, Distributed Power Management Higher vram entitlement vmotion, High Availability Hypervisor HIGH AVAILABILITY (HA) 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 Continuously monitors and chooses the optimal physical servers within a resource pool on which to restart virtual machines (if used in conjunction with DRS) 23

24 DISTRIBUTED RESOURCE SCHEDULER (DRS) DRS enables your virtual environment to automatically balance itself across your host servers in an effort to eliminate resource contention. It utilizes the VMotion feature to provide automated resource optimization and automatic migration of virtual machines across hosts in a cluster. 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. VMOTION Ability to move a running VM to another host with the end user not noticing 24

25 VMOTION - HOW IT WORKS 1. Migration request is made to move the virtual machine from one ESXi server to another ESXi server. 2. vcenter Server verifies that the virtual machine is in a stable state and checks the compatibility of the destination ESXi server (CPU, networking, etc.) 3. The virtual machine is registered on the destination server. 4. The virtual machine state information (including memory, registers and network connections) is copied to the destination server 5. The virtual machine is quiesced on originating ESXi server and the memory bitmap is copied to the destination server. 6. The virtual machine is started on the destination server and all requests for the virtual machine are now directed to it. 7. A final copy of the virtual machines memory is copied from the originating ESXi server to the destination server. 8. The virtual machine is un-registered from the originating server. 9. The virtual machine resumes operation on the destination server. STORAGE VMOTION Storage VMotion was a new feature introduced in ESX 3.5, it 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. The virtual machine can be moved to any datastore on the ESX host which includes local and shared storage. 25

26 STORAGE VMOTION - HOW IT WORKS 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. MICROSOFT HYPER-V 26

27 WINDOWS HYPER-V REQUIREMENTS Description Hypervisor based virtualization platform Windows Server 2008 x64 Edition technology Standard, Enterprise and Datacenter Editions Hardware Requirements x64 server with hardware assisted virtualization AMD AMD-V or Intel VT Hardware enabled Data Execution Prevention (DEP) required AMD (NX no execute bit) Intel (XD execute disable) Note: Enabling these BIOS features requires powering down (not rebooting) the server to take effect HYPER-V Capabilities 32-bit (x86) & 64-bit (x64) VMs Large memory support (64 GB) per VM SMP VMs (up to 4 cores) Integrated cluster support for HA & Quick Migration BitLocker: Seamless, secure data encryption Live Backup: Volume Shadow Service integration Pass-through disk access for VMs Virtual Machine snapshots New hardware sharing architecture (VSP/VSC/VMBus) Disk, networking, input, video Robust networking: VLANs and NLB DMTF standard for WMI management interface Support for Full or Server Core installations 27

28 HYPER-V NETWORKING Two physical network adapters at minimum One for management One (or more) for VM networking Dedicated NIC(s) for iscsi Connect parent to back-end management network Only expose guests to internet traffic Windows Server 2008 R2 Hyper-V Enhancements Storage Processor Networking 28

29 Hot Add/Remove Storage Overview Add and remove VHD and pass-through disks to a running VM without requiring a reboot. Benefits Enables storage growth in VMs without downtime Enables additional datacenter backup scenarios Enables new SQL/Exchange scenarios Windows Server 2008 R2 Hyper-V Enhancements Continues - CPU Second Level Address Translation (SLAT) Core Parking Support for 64 logical processors on host computer 29

30 Windows Server 2008 R2 Hyper-V Enhancements Continues - Network Extending TCP Offload support for Virtual machines Jumbo Frame Support Virtual Machine Queue (VMQ) Support INCREASING AVAILABILITY - LIVE MIGRATION Overview Migrate virtual machines between hosts with no interruption of service! Benefits No dropped network connections High availability for production workloads Flexible management 30

31 WHAT ABOUT Heterogeneous Virtualization Management Physical to Virtual Conversion (P2V) Virtual to Virtual Conversion (V2V) Virtual Server to Hyper-V VMware to Hyper-V Virtual Machine Library PowerShell Scripting Delegated Administration Virtual Machine Authoring VM Templates/Cloning Failover Cluster Integration HYPER-V ARCHITECTURE Parent Partition Child Partitions Provided by: OS ISV / IHV / OEM Microsoft Hyper-V Microsoft / XenSource VM Worker Processes Applications WMI Provider VM Service Applications Applications Applications User Mode Windows Server 2008 Windows Server 2003, 2008 Non-Hypervisor Aware OS Xen-Enabled Linux Kernel Windows Kernel IHV Drivers VMBus VSP Windows Kernel VMBus VSC Emulation Linux VSC VMBus Hypercall Adapter Kernel Mode Windows hypervisor Ring -1 Designed for Windows Server Hardware 31

32 XEN Released in 2002 More established than KVM supports x86, x86_64, Itanium, and ARM architectures Open source XEN VMM 32

33 KVM KVM - Kernel-based Virtual Machine New guy on the block - catching up quickly with XEN Linux based Open Source