<div dir="ltr">+1 for ha-pacemaker-improvements</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">--<br>
Best regards,<br>
Sergii Golovatiuk,<br>
Skype #golserge<br>
IRC #holser<br></div></div></div>
<br><div class="gmail_quote">On Fri, Nov 14, 2014 at 11:51 PM, Dmitry Borodaenko <span dir="ltr"><<a href="mailto:dborodaenko@mirantis.com" target="_blank">dborodaenko@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Good plan, but I really hate the name of this blueprint. I think we<br>
should stop lumping different unrelated HA improvements into a single<br>
blueprint with a generic name like that, especially when we already<br>
had a blueprint with essentially the same name<br>
(ha-pacemaker-improvements). There's nothing wrong with having 4<br>
trivial but specific blueprints instead of one catch-all.<br>
<div><div class="h5"><br>
On Wed, Nov 12, 2014 at 4:10 AM, Aleksandr Didenko<br>
<<a href="mailto:adidenko@mirantis.com">adidenko@mirantis.com</a>> wrote:<br>
> HI,<br>
><br>
> in order to make sure some critical Haproxy backends are running (like mysql<br>
> or keystone) before proceeding with deployment, we use execs like [1] or<br>
> [2].<br>
><br>
> We're currently working on a minor improvements of those execs, but there is<br>
> another approach - we can replace those execs with puppet resource providers<br>
> and move all the iterations/loops/timeouts logic there. Also we should fail<br>
> catalog compilation/run if those resource providers are not able to ensure<br>
> needed Haproxy backends are up and running. Because there is no point to<br>
> proceed with deployment if keystone is not running, for example.<br>
><br>
> If no one objects, I can start implementing this for Fuel-6.1. We can<br>
> address it as a part of pacemaker improvements BP [3] or create a new BP.<br>
><br>
> [1]<br>
> <a href="https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/osnailyfacter/manifests/cluster_ha.pp#L551-L572" target="_blank">https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/osnailyfacter/manifests/cluster_ha.pp#L551-L572</a><br>
> [2]<br>
> <a href="https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/openstack/manifests/ha/mysqld.pp#L28-L33" target="_blank">https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/openstack/manifests/ha/mysqld.pp#L28-L33</a><br>
> [3] <a href="https://blueprints.launchpad.net/fuel/+spec/pacemaker-improvements" target="_blank">https://blueprints.launchpad.net/fuel/+spec/pacemaker-improvements</a><br>
><br>
> Regards,<br>
> Aleksandr Didenko<br>
><br>
><br>
</div></div>> _______________________________________________<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>
><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
Dmitry Borodaenko<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>
</font></span></blockquote></div><br></div>