Eric Sloof - NTPRO.NL

The SRM Essentials free elearning (self-paced, 3 Hours) training course equips experienced VMware vSphere administrators with the knowledge to install, configure, and manage VMware vCenter Site Recovery Manager (SRM) 5.1. This elearning also equips vSphere administrators with the knowledge to assist in disaster planning and test disaster recovery plans with SRM. This course introduces different storage replication options and focuses on vSphere Replication.

Mike_Laverick says Multi-Hypervisor Manager (MHM), as you might know there’s been a “Fling” on the VMware Labs for sometime, that allows you to manage Windows HyperV hosts from vCenter. That fling is going to be discontinued and supported in the web-client. It will be a free component with Standard vCenter and support Windows HyperV 2008, and will support Windows HyperV 2012 when it finally ships. It will have a little bit more functionality that the original fling – it will be able to create new VMs on the Windows HyperV host and will more seamlessly integrate with vCenter. PMHM will ship as service that you add to your environment if you need it.

VMware vCenter Multi-Hypervisor Manager 1.0 Release Notes

VMware vCenter Multi-Hypervisor Manager 1.0 | 19 Nov 2012 | Build 901315 | Product Download

This video was recorded at the VMworld 2012 Europe Barcelona and shows the Multi-Hypervisor Manager in action. (I'm the guy holding the microphone asking nasty questions :-))

Cloud computing services have experienced rapid growth over the past few years because they can keep costs down by allowing multiple tenants to share system resources. One requirement of making this multiple tenancy possible is to provide each tenant with network isolation. Segmenting the traffic using VLAN is a typical solution to this problem. However, service providers also need to keep up with customer demand by being able to move workloads to those servers that have spare resources.

To do so, network traffic needs to be encapsulated so that the workload is not tied to the underlying hardware. This can be a problem because the networking architecture ties the workloads to the underlying hardware, which restricts the movements of these workloads and limits where these workloads can be placed. In addition, segmenting the physical LAN using VLANs does not scale beyond a certain limit.

Virtual extensible LAN (VXLAN) is a network encapsulation mechanism that enables virtual machines to be deployed on any physical host, regardless of the host’s network configuration. It solves the problems of mobility and scalability in two ways: