Description of problem:
fence_vmware uses a proprietary perl API that is not in RHEL. But the libvirt client in RHEL6 supports URIs to connect to both ESX and VirtualCenter/vSphere mgmt servers.
We should be able to point fence_virt on a virtual cluster node to point to the vSphere/VirtualCenter server for all other guests so that it can just ask the mgmt server to do the fencing for it.
This does not affect fence_virtd at all since in ESX deployments we have no host access so there will be no fence_virtd running.
This may also require backporting fence_virt or a similar agent to RHEL5 to support the RHEL5 use case.
*** Bug 595378 has been marked as a duplicate of this bug. ***
Instead of integrating into fence-virt, fence_vmware will be reworked to use the SOAP API exposed by VMware. Marking as duplicate of bug # 624673
*** This bug has been marked as a duplicate of bug 624673 ***