Open Stack

Bogdan,

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
On Dec 30, 2014 3:39 AM, "Bogdan Dobrelya" <bdobrelia at mirantis.com> wrote:

> Hello.
> There is a long living blueprint [0] about HA fencing of failed nodes
> in Corosync and Pacemaker cluster. Happily, in 6.0 release we have a
> pluggable architecture supported in Fuel.
>
> I propose the following implementation [1] (WIP repo [2]) for this
> feature as a plugin for puppet. It addresses the related blueprint for
> HA Fencing in puppet manifests of Fuel library [3].
>
> For initial version,  all the data definitions for power management
> devices should be done manually in YAML files (see the plugin's
> README.md file). Later it could be done in a more user friendly way, as
> a part of Fuel UI perhaps.
>
> Note that the similar approach - YAML data structures which should be
> filled in by the cloud admin and passed to Fuel Orchestrator
> automatically at PXE provision stage - could be used as well for Power
> management blueprint, see the related ML thread [4].
>
> Please also note, there is a dev docs for Fuel plugins merged recently
> [5] where you can find how to build and install this plugin.
>
> [0] https://blueprints.launchpad.net/fuel/+spec/ha-fencing
> [1] https://review.openstack.org/#/c/144425/
> [2]
>
> https://github.com/bogdando/fuel-plugins/tree/fencing_puppet_newprovider/ha_fencing
> [3]
> https://blueprints.launchpad.net/fuel/+spec/fencing-in-puppet-manifests
> [4]
>
> http://lists.openstack.org/pipermail/openstack-dev/2014-November/049794.html
> [5]
>
> http://docs.mirantis.com/fuel/fuel-6.0/plugin-dev.html#what-is-pluggable-architecture
>
> --
> Best regards,
> Bogdan Dobrelya,
> Skype #bogdando_at_yahoo.com
> Irc #bogdando
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141231/74ca8c97/attachment.html>