[openstack-dev] [Fuel] Waiting for Haproxy backends

Aleksandr Didenko adidenko at mirantis.com
Wed Nov 12 12:10:35 UTC 2014


in order to make sure some critical Haproxy backends are running (like
mysql or keystone) before proceeding with deployment, we use execs like [1]
or [2].

We're currently working on a minor improvements of those execs, but there
is another approach - we can replace those execs with puppet resource
providers and move all the iterations/loops/timeouts logic there. Also we
should fail catalog compilation/run if those resource providers are not
able to ensure needed Haproxy backends are up and running. Because there is
no point to proceed with deployment if keystone is not running, for example.

If no one objects, I can start implementing this for Fuel-6.1. We can
address it as a part of pacemaker improvements BP [3] or create a new BP.

[3] https://blueprints.launchpad.net/fuel/+spec/pacemaker-improvements

Aleksandr Didenko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141112/da9e6b0b/attachment.html>

More information about the OpenStack-dev mailing list