release, customers will now have the ability to optionally specify a target Resource Pool and/or VM Folder by enabling an Advanced settings option at the upper right hand corner of the tool as shown in the screenshot below.īelow is a screenshot of vMotion'ing 3 running PhotonOS VMs from onPrem environment to my VMC's SDDC. VMC has a restrictive permission model and customer workloads must be placed in a specific VM Folder and Resource Pool, both of which was not initially supported with the Cross vCenter vMotion Utility. These two stand alone feature are quite useful on their own, but they are also a building block to allow us to support migrating workloads to and from VMware Cloud on AWS (VMC) which we have received requests for as well.
Customers often use VM Folders for organization purposes but also as a way to manage permissions and of course resource management with the use of Resource Pools (not for organization purposes )). Most recently, we had a few customers ask for supporting additional placement targets such as vSphere VM Folders and Resource Pools. Not only are the number of production VMs significant, but I also learned the duration of customer migration projects, such as datacenter evacuation, was able to complete significantly faster with the help of this tool.Īlthough v2.1 was just recently released, Vishal, the lead developer is constantly looking for ways to improve the tool. In fact, a number of you have even shared your VM migration numbers, many of which are quite impressive (e.g. Many of you are already familiar with the Cross vCenter vMotion Utility, which was released as a Fling last year.
0 kommentar(er)
