Document vMotion support

[stuclem]

Document vMotion support, as defined in #770.

[stuclem]

See also #859.

#858 might also require some user-facing doc (TBD).

[stuclem]

Requires updates in the topic on vSphere interop. The descriptions of #859 and #858 list what will be supported once those issues are implemented.

[stuclem]

We currently say the following in the topic on vSphere interop:

vSphere High Availability, Fault Tolerance, and vSphere vMotion

IT teams can assure service-level agreements for container workloads with VMware vSphere Distributed Resource Scheduler as well as reduce planned and unplanned downtime with VMware vSphere High Availability and VMware vSphere vMotion.

You can apply vSphere High Availability and Fault Tolerance to both the container VMs and the virtual container host, so that containers and the virtual container host can power on or off independently of each other.

You can also restart or upgrade the virtual container host without needing to take the containers offline during the process. You do not require a native agent on the ESXi host. The appliance VM does not need to be running for vMotion to occur. Clusters with non-container VMs can also vMotion with fully automated DRS.

NOTE: In the current builds of vSphere Integrated Containers Engine, support for HA, Fault Tolerance, and vMotion is not yet fully implemented.

@mhagen-vmware and @hickeng is this OK?

[mhagen-vmware]

I might move that note to the top actually, as some people might stop reading at some point and not see that we don't actually work at all, but otherwise the language sounds fine.

[stuclem]

Done! Thanks @mhagen-vmware.