Upcoming new vMotion features:
vMotion across vCenter Servers (VCs)
vMotion across virtual switches: Virtual Standard Switch (VSS), Virtual Distributed Switches (VDSs)
vMotion using routed vMotion networks
Long-distance vMotion for use cases such as:
Permanent migrations (often for Datacenter expansions, acquisitions, consolidations)
Disaster avoidance
SRM and disaster avoidance testing
Multi-site capacity utilization
Follow-the-sun scenarios
Onboarding onto vSphere-based public clouds (including VMware vCloud Air)
Crossing Data Centers
As a vSphere engineer, we’re usually limited to vMotion domains that are limited by a vCenter Server construct (or more specifically, the data center in many cases due to network configurations). vSphere 6 will allow VMs to vMotion across Datacenter and VC boundaries using a new workflow. You’ll also be able to take advantage of a workflow that lets you hop from one network (source) to another network (destination), eliminating the need to have a single vSwitch construct spanning the two locations.
vMotion Enhancements for vSphere 6 Announced
Posted by Chris Wahl on August 26, 2014 in General Tech | 4 Responses
Sharing is caring:
201Click to share on LinkedIn (Opens in new window)201Click to share on Twitter (Opens in new window)28Click to share on Facebook (Opens in new window)28Click to share on Reddit (Opens in new window)Click to share on Google+ (Opens in new window)Click to share on Pocket (Opens in new window)More
During the Day 2 keynote at VMworld (August 26th, 2014), Raghu Raghuram, Executive Vice President, Software-Defined Data Center Division, went ahead and announced the upcoming improvements to vMotion that are bundled in vSphere 6. Here’s a look at the details around this announcement:
Upcoming new vMotion features:
vMotion across vCenter Servers (VCs)
vMotion across virtual switches: Virtual Standard Switch (VSS), Virtual Distributed Switches (VDSs)
vMotion using routed vMotion networks
Long-distance vMotion for use cases such as:
Permanent migrations (often for Datacenter expansions, acquisitions, consolidations)
Disaster avoidance
SRM and disaster avoidance testing
Multi-site capacity utilization
Follow-the-sun scenarios
Onboarding onto vSphere-based public clouds (including VMware vCloud Air)
It’s magic time
It’s magic time
Crossing Data Centers
As a vSphere engineer, we’re usually limited to vMotion domains that are limited by a vCenter Server construct (or more specifically, the data center in many cases due to network configurations). vSphere 6 will allow VMs to vMotion across Datacenter and VC boundaries using a new workflow. You’ll also be able to take advantage of a workflow that lets you hop from one network (source) to another network (destination), eliminating the need to have a single vSwitch construct spanning the two locations.
vMotion Diagram
The configurations targeted are:
from VSS to VSS
from VSS to VDS
from VDS to VDS
Routed vMotion and Increased RTT Tolerance
And while you can request a RFQ (request for qualification) to use Layer 3 for vMotion, most of us are limited (or comfortable) with Layer 2 vMotion domains. Essentially, this means one large subnet and VLAN stretched between compute nodes for migrating workloads. An upcoming feature will allow VMs to vMotion using routed vMotion networks without need for special qualification. In addition, another useful feature planned will revolve around the ability to vMotion or clone powered off VMs over NFC networks.
And finally, the latency requirements for vMotion are being increased by 10x. Enterprise Plus customers today can tolerate vMotion RTTs (round trip times) of 10 ms or less. In the new release, vMotion can withstand 100 ms of RTT.
Recent Comments