Vladislav Belogrudov 9d156eb005 First keepalived container is started with wrong priority ... First keepalived container is started with priority 0 but the latter should be in range 1-255. This gives error and keepalived resumes with default priority 100. Change-Id: Ib11d0072a96b818d86c81a32e78118c0c82b74d8 Closes-Bug: #1494237		2015-09-10 13:22:00 +03:00
..
haproxy.cfg.j2	Add Ansible support for Heat	2015-08-29 23:58:54 -07:00
keepalived.conf.j2	First keepalived container is started with wrong priority	2015-09-10 13:22:00 +03:00