<p dir="ltr">Bogdan, </p>
<p dir="ltr">Do you think that the existing post deployment hook is sufficient to implement this or does additional plugins development need to be done to support this</p>
<div class="gmail_quote">On Dec 30, 2014 3:39 AM, "Bogdan Dobrelya" <<a href="mailto:bdobrelia@mirantis.com">bdobrelia@mirantis.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello.<br>
There is a long living blueprint [0] about HA fencing of failed nodes<br>
in Corosync and Pacemaker cluster. Happily, in 6.0 release we have a<br>
pluggable architecture supported in Fuel.<br>
<br>
I propose the following implementation [1] (WIP repo [2]) for this<br>
feature as a plugin for puppet. It addresses the related blueprint for<br>
HA Fencing in puppet manifests of Fuel library [3].<br>
<br>
For initial version,  all the data definitions for power management<br>
devices should be done manually in YAML files (see the plugin's<br>
README.md file). Later it could be done in a more user friendly way, as<br>
a part of Fuel UI perhaps.<br>
<br>
Note that the similar approach - YAML data structures which should be<br>
filled in by the cloud admin and passed to Fuel Orchestrator<br>
automatically at PXE provision stage - could be used as well for Power<br>
management blueprint, see the related ML thread [4].<br>
<br>
Please also note, there is a dev docs for Fuel plugins merged recently<br>
[5] where you can find how to build and install this plugin.<br>
<br>
[0] <a href="https://blueprints.launchpad.net/fuel/+spec/ha-fencing" target="_blank">https://blueprints.launchpad.net/fuel/+spec/ha-fencing</a><br>
[1] <a href="https://review.openstack.org/#/c/144425/" target="_blank">https://review.openstack.org/#/c/144425/</a><br>
[2]<br>
<a href="https://github.com/bogdando/fuel-plugins/tree/fencing_puppet_newprovider/ha_fencing" target="_blank">https://github.com/bogdando/fuel-plugins/tree/fencing_puppet_newprovider/ha_fencing</a><br>
[3] <a href="https://blueprints.launchpad.net/fuel/+spec/fencing-in-puppet-manifests" target="_blank">https://blueprints.launchpad.net/fuel/+spec/fencing-in-puppet-manifests</a><br>
[4]<br>
<a href="http://lists.openstack.org/pipermail/openstack-dev/2014-November/049794.html" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2014-November/049794.html</a><br>
[5]<br>
<a href="http://docs.mirantis.com/fuel/fuel-6.0/plugin-dev.html#what-is-pluggable-architecture" target="_blank">http://docs.mirantis.com/fuel/fuel-6.0/plugin-dev.html#what-is-pluggable-architecture</a><br>
<br>
--<br>
Best regards,<br>
Bogdan Dobrelya,<br>
Skype #<a href="http://bogdando_at_yahoo.com" target="_blank">bogdando_at_yahoo.com</a><br>
Irc #bogdando<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>