Bug 595378

Summary:	Add support for using libvirt drivers directly from fence-virt w/o need for fence-virtd
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:	cluster-maint, jwest, mgrac, ssaha, tao
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-07-02 13:47:39 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-24 13:49:58 UTC

Description of problem:
Right now fence-virt works by sending a fencing request to fence-virtd and then fence-virtd sends the request to the correct host.  This is fine for kvm based deployments.

But we need a way for fence-virt to use other libvirt drivers like ESX and on ESX hosts we can't use a fence-virtd.  So fence-virt should know to use libvirt driver for ESX/VirtualCenter when deployed on ESX hosts.

This is dependent on adding support for VirtualCenter into the libvirt driver.

Comment 1 Perry Myers 2010-05-24 13:54:10 UTC

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

Comment 2 Perry Myers 2010-07-02 13:47:39 UTC


*** This bug has been marked as a duplicate of bug 590696 ***