Bug 590696

Summary:	Add support for fence-virt to connect directly to libvirt ESX or vSphere/VirtualCenter server
Product:	Red Hat Enterprise Linux 6	Reporter:	Perry Myers <pmyers>
Component:	fence-virt	Assignee:	Lon Hohberger <lhh>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	berrange, cluster-maint, degts, mgrac, tao, veillard
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	590697 (view as bug list)		Environment:
Last Closed:	2010-11-27 13:33:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	595380, 610811
Bug Blocks:

Description Perry Myers 2010-05-10 13:59:52 UTC

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 13:47:39 UTC

*** Bug 595378 has been marked as a duplicate of this bug. ***

Comment 2 Perry Myers 2010-11-27 13:33:09 UTC

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 ***