VMware adds vim and vigor to vMotion between different vCenter servers

VMware has added a new and simpler way to move virtual machines between private clouds, or private clouds and the public cloud. “vMotion” – the practice of moving VMs to hosts and/or different private clouds with little disruption – has been one of VMware’s best tricks for years. But in practice it has not always been easy …

[Joe W]

Disappointed

(a bit), as I immediately thought of http://vigor.sourceforge.net/

[amanfromMars 1]

An Orgy of Opportunity in which to Play. Thanks, VMware senior staff solution architect William Lam

So he fixed the limitations of the UI, first with a script and then with a cmdlet that VMware issued as a “Fling” – an unsupported but probably-production-ready piece of code that VMware offers as downloads for the adventurous.

An accurate analogy explaining and exhorting the "Fling" and the sharing and transfer of VMware across all manner of clouds, both private and public and root basic and highly sophisticated, is honestly reflected in the uninhibited world of satisfying pastimes and exhausting desires popular in Swinging.

Such is readily available to any virtual machine but not all will find it addictively attractive and empoweringly captivating although the hellish heavenly temptation may permanently persist to torture and/or excite the immortal soul. :-) ........ as will certain depressing resistance to its erotic, exotic allure.