Open Stack

Hey Fuelers,

We have been using our own fork of the haproxy module within fuel-library
for some time. This also includes relying on a MOS specific version of
haproxy that carries the conf.d hack.  Unfortunately this has meant that
we've needed to leverage the MOS version of this package when deploying
with UCA.  As far as I can tell, there is no actual need to continue to do
this anymore. I have been working on switching to the upstream haproxy
module[0] so we can drop this custom haproxy package and leverage the
upstream haproxy module.

In order to properly switch to the upstream haproxy module, we need to
collapse the haproxy tasks into a single task. With the migration to
leveraging classes for task functionality, this is pretty straight forward.
In my review I have left the old tasks still in place to make sure to not
break any previous dependencies but they old tasks no longer do anything.
The next step after this initial merge would be to cleanup the haproxy code
and extract it from the old openstack module.

Please be aware that if you were relying on the conf.d method of injecting
configurations for haproxy, this will break you. Please speak up now so we
can figure out an alternative solution.

Thanks,
-Alex


[0] https://review.openstack.org/#/c/307538/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160512/9eb9a3df/attachment.html>