<div dir="ltr"><div><div>HI,<br><br></div>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].<br><br></div><div>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.<br></div><div><br>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.<br></div><div><br>[1] <a href="https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/osnailyfacter/manifests/cluster_ha.pp#L551-L572">https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/osnailyfacter/manifests/cluster_ha.pp#L551-L572</a><br>[2] <a href="https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/openstack/manifests/ha/mysqld.pp#L28-L33">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">https://blueprints.launchpad.net/fuel/+spec/pacemaker-improvements</a><br><br></div><div>Regards,<br></div><div>Aleksandr Didenko<br></div><div><br></div></div>