In recent times many companies are in the condition to plan the introduction of a second virtualization platform or even to have already the need to manage more than one.
Causes may be the most disparate: licensing costs, independence from a single vendor, processes optimization, etc.
Approaches to cross-virtualization also can be of different types.
There are three approaches that you can take to having one cross platform virtualization management strategy:
- Assemble as management stack from best of breed third party solutions that support both of your virtualization platforms. For example, performance and capacity monitoring vendors like VKernel (now part of Quest Software), SolarWinds, VMTurbo, and Zenoss all support multiple virtualization platforms. Application Performance Management vendors like AppDynamics, New Relic, BlueStripe, Correlsense, and ExtraHop Networks tend to be agnostic of the underlying virtualization platform. Most backup vendors like Veeam support more than one hypervisor as well.
- Standardize upon Microsoft SCOM as your management console, and then use plug-ins to SCOM (management packs) to support other virtualization platforms. For example you can use the Veeam nworks product to manage your VMware environment from within Micrsosoft SCOM. You can use the BlueStripe plugin to SCOM to manage all of the applications deployed across both VMware and Hyper-V virtualization platforms.
- Use Hotlink, to extend the reach of vCenter to Hyper-V, KVM, and XenServer.