Red Hat Bugzilla – Bug 634567
Rework fence_vmware fence agent to use SOAP API to connect to Virtual Center instead of VMware Perl API
Last modified: 2011-07-21 03:15:50 EDT
+++ This bug was initially created as a clone of Bug #624673 +++
Description of problem:
Existing fence_vmware uses 3rd party RPM dependency from VMware (VMware Perl API). libvirt VMware/ESX driver implemented a SOAP method to connect to Virtual Center.
libvirt usage is fairly different than what we want for a general fence agent, so it's been recommended by libvirt team that we lift their SOAP code (just the parts of it that we need for the fence agent) and use it to rework the fence_vmware agent.
--- Additional comment from firstname.lastname@example.org on 2010-08-30 14:13:27 EDT ---
Doing this will allow us to remove fence_vmware_helper.pl and fence_vware can be exclusively Python code. This will likely create a dependency on a SOAP module to be pulled into Pyton, such as SOAPy.
The vmware web site has a "VMware Infrastructure SDK Programming Guide" that seems helpful, too. Basic power on/off operations are PowerOnVM_Task and PowerOffVM_Task. Also look at libvirt, which uses a C API but has some python code to generate the SOAP code. This is more than we need for fence_vmware, but might be a handy reference.
--- Additional comment from email@example.com on 2010-09-16 07:53:33 EDT ---
*** Bug 486207 has been marked as a duplicate of this bug. ***
*** Bug 590697 has been marked as a duplicate of this bug. ***
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
This request was erroneously denied for the current release of
Red Hat Enterprise Linux. The error has been fixed and this
request has been re-proposed for the current release.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.