Jean-Philippe Evrard 9df04fed70 Fixing haproxy-playbook fails when installing on multiple hosts ... This bug is triggered when haproxy is deployed on multiple hosts and external_lb_vip is different than the internal one. As all host receive the same configuration, and are expected to restart the haproxy service more than once (once during role and once post_tasks), the playbook will fail, because the restart of the service fails. The restart of the service fails on some hosts because haproxy tries to start/bind to an ip the host doesn't have (avoiding ip conflicts) This allows haproxy to bind on non_local addresses by addng a sysctl change in the playbook: net.ipv4.ip_nonlocal_bind = 1 The sysctl is changed for the containers/systems when external_lb_vip is different than internal address and the number of haproxy hosts is more than one thanks to a group_var. Side-effect: other services are able to bind on non-local addresses if the sysctl is changed. This could be overriden by setting the variable haproxy_bind_on_non_local in your user_* variables. If set to false, then the ip_non_local_bind sysctl won't be changed. Closes-Bug: #1487409 Change-Id: I41b3a5a4ba2d48192b505e3720456a77484aa92b		2015-09-02 12:40:20 +00:00
..
group_vars	Fixing haproxy-playbook fails when installing on multiple hosts	2015-09-02 12:40:20 +00:00
dynamic_inventory.py	Change to set the container network MTU	2015-07-22 19:25:01 -05:00