Bug 590696 - Add support for fence-virt to connect directly to libvirt ESX or vSphere/VirtualCenter server
Add support for fence-virt to connect directly to libvirt ESX or vSphere/Virt...
Status: CLOSED DUPLICATE of bug 624673
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: fence-virt (Show other bugs)
6.0
All Linux
low Severity medium
: rc
: ---
Assigned To: Lon Hohberger
Virtualization Bugs
:
: 595378 (view as bug list)
Depends On: 595380 610811
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-10 09:59 EDT by Perry Myers
Modified: 2011-04-28 21:48 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 590697 (view as bug list)
Environment:
Last Closed: 2010-11-27 08:33:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Perry Myers 2010-05-10 09:59:52 EDT
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.
Comment 1 Perry Myers 2010-07-02 09:47:39 EDT
*** Bug 595378 has been marked as a duplicate of this bug. ***
Comment 2 Perry Myers 2010-11-27 08:33:09 EST
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 ***

Note You need to log in before you can comment on or make changes to this bug.