We use VCenter 2 to manage HostLocal1 and HostLocal2, but we don't cluster them together and we don't vMotion among them, because all the vMotion traffic would have to go to vCenter and Then to the second host, is that right? Is there a way to prevent that?
Let me rephrase that: The VMotion traffic would be like this:
HostLocal1 --> VCenter 2 ---> HostLocal2
HostLocal1 --> HostLocal2.
vMotion traffic only flows directly between the source and destination ESX(i) host. The assumption that vMotion traffic flows through vCenter is flat-out wrong. vCenter is merely needed to initiate/control the vMotion between the hosts, but it's completely left out from the data that is transferred between hosts for moving the VM.
The assumption that you need a cluster object for vMotion or that clustering automatically implies vMotion is wrong as well.
Actually, when writing the question that hit me as a truck. It would be completely dumb doing that way.
Thanks for the clarification/confirmation anyways.