Milestone: vmotion support

[hickeng]

Permit vMotion of:

• containerVMs
• applianceVM

The appliance VM is actually the less critical as we control everything in that and it's explicitly designed to be killed and brought back up without impacting anything other than management operations.

The mechanisms available to us for enabling vMotion are documented here. The initial set of sub-issues are anything and everything directly related to getting vMotion support for containerVMs and may well not be the route taken depending on time constraints.

Children all moved to icebox, and chosen path will be added to backlog.

This will require VIB deployment of either firewall configuration or ESX agent unless we implement guestinfo based signal delivery and explicitly toggle the attach mechanism - this approach would allow us to avoid any dependence on an agent while still having vMotion for any VMs that do not have an attach session active.

UPDATE (26/7/2016): we're using the guest-tools mechanism to deliver signals and #858 is for explicit toggling of the attach mechanism therefore no VIBs required.

[hickeng]

Removed this from GA - the sub issues for basic support and testing using the initial implementation (on-demand attach connection) are left in GA.

[mdubya66]

Removing from VIC GA Release as all remaining issues are outside of that milestone

[hickeng]

Closing - with the integration of vSPC for release 1.1 the only outstanding issue is the file back serial ports for output.log (docker logs) and tether.debug getting disconnected after vmotion.
There is a ESX hotfix for that which will be included in the next update.