This document discusses managing multiple hypervisors in an IT environment. It introduces tips and tricks for virtualization administrators ("vAdmins") dealing with the challenges of overseeing different hypervisors. These include issues with terminology, management interfaces, licensing, capabilities, integration with other systems, and vendor support. The document suggests some strategies for vAdmins to effectively handle multi-hypervisor environments, such as learning about each hypervisor thoroughly. It also introduces several management tools that aim to provide a unified interface for multiple hypervisors.
Human Factors of XR: Using Human Factors to Design XR Systems
Becoming a vAdmin Rockstar! Managing multiple hypervisors in your datacenter
1. Becoming a vAdmin Rockstar! Tips &
Tricks for Managing Multiple
Hypervisors in Your Environment
Mike Nelson
Solutions Architect - nGenX
Level: Intermediate
2. Or…
Who Can Make Up The Longest
Session Title Ever & Get Away With
It!
Mike Nelson
Solutions Architect - nGenX
Level: Intermediate
3. Who Is This Guy?
• Solutions Architect – nGenX
• 25 years in tech
• CTP - vExpert - MCSE-PC
• mike.nelson@ngenx.com
• Twitter - @nelmedia
Mike Nelson 2014
4. What Are We Going to Talk About?
• Who are you?
• What, why, and how of what you do
• Are you the master of your domain? Really?
• Some Stats & Speculations
• Cover the basics
• Managing the mess
• Demo
Mike Nelson 2014
5. Updates
I like to draw ;-)
Updated slides, drawings, etc.
http://1drv.ms/1oHyNzP
Mike Nelson 2014
6.
7. Questions for You
• What’s the difference between Type1 and
Type2?
• Can anyone name all the Type1 Hypervisors?
• Do you have a single or multiple hypervisors in
your datacenter now? Do you even know?
• Does your IT have any role in decisions by the
business? Who owns the technology?
• How many admin’s? Who does what?
• Are you bias? Paranoid? Or both?
19. The Wikibon conclusions from their survey:
• Overall growth of x86 virtualization is healthy, and shows no sign of stalling or topping
out.
• VMware is the dominant force with 76% of the installed base. The workload analysis
shows that all workload types are migrating to VMware, including mission critical and
database workloads.
• Even though VMware is projected to grow at only 24%, VMware will still hold 68% of
the overall market in 18 months time.
• Microsoft Hyper-V is projected to grow at 61% over the next 18 months, with an
emphasis on smaller Microsoft IT shops, and desktop virtualization.
• KVM is growing very fast from a small base, and is the leading open-source contender
by far. It is particularly strong it Hyperscale IT infrastructures (not represented in this
survey), an with other IT service organizations such as Cloud Service providers, ISVs,
VARs and other distributers.
• OVM from Oracle is focused on large-scale Oracle database installations, and seems to
be growing fast in this niche.
• From the evidence of this survey, Citrix Xen is challenged to remain a viable
hypervisor.
Ref: Wikibon Multi-Hypervisor Survey, August 2013
33. • Code injection in Hypervisor
Layer
• Requires compatible
hardware & device drivers
• No security patches or
operating system required in
the Controlling Layer
• No code injection possible in
Hypervisor Layer
• Device drivers do not need
to be hypervisor aware
• Controlling Layer requires OS
= less secure
34. vSphere 5.5
Linux:
Asianux
SUSE
RedHat
Fedora
CentOS
OS X (Darwin) *
E-Com Station
Debian
FreeBSD
Mandrake
Java Desktop
Oracle desktop *
TurboLinux
Ubuntu
Solaris*
SCO
Netware
Windows:
Server 2012 / R2
Server 2008 / R2
Server 2003 / R2
Server 2000
Server NT
Windows 8.1
Windows 7
Windows Vista
Windows XP
Windows 98
Windows ME
Windows 95
Windows 3.1
DOS
Other?:
OS/2 Warp
35. Linux:
Asianux
SUSE
RedHat
Fedora
CentOS
OS X (Darwin)
E-Com Station
Debian
FreeBSD
Mandrake
Java Desktop
Oracle desktop
TurboLinux
Ubuntu
Solaris
SCO
Netware
Windows:
Server 2012 / R2
Server 2008 / R2
Server 2003 / R2
Server 2000
Server NT
Windows 8.1
Windows 7
Windows Vista
Windows XP
Windows 98
Windows ME
Windows 95
Windows 3.1
DOS
Other?:
OS/2 Warp
Hyper-V 2012 R2
39. vAdmin Challenges
• Terminology
• Management
• Licensing
• Capacities & limitations
• “Core 4” compatibility
• 3rd party integrations
• Scaling
• Vendor support
• DR / HA / Compliance
Mike Nelson 2014
40. How Do We Manage Today?
• Multiple windows
• Multiple machines
• Multiple admins
• Steep learning curves
Mike Nelson 2014
41. VMware’s Rant on SCVMM
VMware Whitepaper:
Opening line “Why trying to use SCVMM 2012 will frustrate
vSphere administrators”
Microsoft is trying to convince vSphere administrators to
manage their VMware environment using System Center Virtual
Machine Manager 2012 (SCVMM 2012). However, vSphere
administrators will find that SCVMM 2012 -
1. Increases Complexity While Adding Little Value
2. Is Not a “Single Pane Of Glass Interface”, vCenter Server Is Still
Required
3. Adds New Overheads, Delivers Little Benefit
4. Degrades Operational Efficiency, Frustrating Administrators
SCVMM 2012 offers only rudimentary management capabilities
for VMware environments and introduces unnecessary
complexity, overhead and frustration for vSphere
administrators.
70. What’s a vAdmin To Do?
• Pick your fights
• Learn about the hypervisors, what they can &
cannot do, how to configure & troubleshoot
• Read the best practices & capacity info
• Make your case & mark your territory, if you can.
• Learn the tools, try before you buy
• Deploy and play around, cop a feel
• Talk to some “smart” people, buy them beer
• Learn PowerShell!
The Microkernelized Hypervisor Design is used by Microsoft Hyper-V. This design does not require the device drivers to be part of the Hypervisor layer — the device drivers operate independently and run in the "Controlling Layer“.
The Microkernelized Hypervisor Design provides the following advantages:
Device drivers are not needed for each device to be incorporated in the "Hypervisor Layer" or VMM Kernel
Since Microsoft does not provide Application Programming Interfaces (APIs) to access the "Hypervisor Layer", the attack surface is minimized. No one can inject foreign code in the "Hypervisor Layer."
Device Drivers do not need to be hypervisor-aware. So a wide-range of devices can be used with the Microkernelized Hypervisor Design.
There is no need to shut down "Hypervisor Layer" to include the device drivers. The Device Drivers can be installed in the Operating System running in the "Controlling Layer" (Windows Server 2008, R2, and Windows Server 2012) and used by the Virtual Machines to access the hardware in the "Hardware Layer."
"Hypervisor Layer" has less overhead for maintaining and managing the Device Drivers.
The Microkernelized Hypervisor Design allows you to install any other server roles in the "Controlling Layer" apart from Server Virtualization role (Hyper-V).
There is less initialization time required. The Microsoft Hypervisor code is about just 600 KB in size. So the "Hypervisor Layer" does not require more time to initialize its components.
At the same time, there are a few disadvantages associated with the Microkernelized Hypervisor Design that are important to highlight:
The Microkernelized Hypervisor Design requires an operating system to be installed in the "Controlling Layer" before the "Hypervisor Layer" can operate. This is the biggest disadvantage.
If the operating system running in "Controlling Layer" crashes for any reason, then all other virtual machines will also crash.
More overhead is required for the operating system running in the "Controlling Layer" to manage the communications between the virtual machines and the "Hypervisor Layer."
Every organization maintains the security of Windows operating systems by means of applying security updates released by Microsoft. So the operating system running in the "Controlling Layer" must also be applied with the latest security updates. As part of the security updates, the Operating System will be rebooted, which in turn requires you to take all virtual machines offline — or move to another node in the cluster without any downtime with the help of Hyper-V Live Migration feature.
Possibilities with Hotlink type integration
Powershell across all
3rd party utilities across all
Backup?