So I have a serious problem with the new priority since I will attend the OpenStack Summit next week and will be back on May 25th. Just to make sure I'm not making things wrong, could you please confirm that the file to port to Python is https://github.com/beekhof/osp-ha-deploy/blob/master/pcmk/fence_compute ? The deadlist is at risk for me but I can provide a first draft for using the Nova python client.
(In reply to Sylvain Bauza from comment #3) > So I have a serious problem with the new priority since I will attend the > OpenStack Summit next week and will be back on May 25th. > > Just to make sure I'm not making things wrong, could you please confirm that > the file to port to Python is > https://github.com/beekhof/osp-ha-deploy/blob/master/pcmk/fence_compute ? > Yes and it´s receiving regular updates as bugs are fixed. > The deadlist is at risk for me but I can provide a first draft for using the > Nova python client.
I just provided a pull request https://github.com/beekhof/osp-ha-deploy/pull/10
With only minor modification, fence agent is in upstream now. In order to add it to the RHEL7, I would prefer to have package python-novaclient in dependencies. Is it possible? I can see it in Fedora but not in RHEL
(In reply to Marek Grac from comment #6) > With only minor modification, fence agent is in upstream now. which modification? > > In order to add it to the RHEL7, I would prefer to have package > python-novaclient in dependencies. Is it possible? I can see it in Fedora > but not in RHEL No it´s not possible, that why the nova client is try: at import and should fail for help or metadata (and work in our build system) Fabio
I am "OtherQA". Andrew and I have been testing fence_compute in combination with NovaCompute (#1214360) and it works as expected. A node fail, NovaCompute is notified, calls into fence_compute and nova will evacuate the OSP instances as planned.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2384.html