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
..
cinder	Properly check failed status	2015-09-06 11:21:44 +00:00
common	Remove start.yml abstraction for kolla-ansible	2015-08-19 02:52:43 +00:00
glance	Properly check failed status	2015-09-06 11:21:44 +00:00
haproxy	First keepalived container is started with wrong priority	2015-09-10 13:22:00 +03:00
heat	Make heat stack-create work	2015-09-06 21:24:56 -07:00
horizon	Add ansible support for Horizon	2015-08-24 18:19:34 +00:00
keystone	Properly check failed status	2015-09-06 11:21:44 +00:00
mariadb	Permit larger database connection count	2015-09-06 04:53:28 -07:00
memcached	Add Ansible role for memcached	2015-08-21 13:52:06 +00:00
murano	Add ansible support for Murano	2015-09-07 09:30:07 +01:00
neutron	Properly check failed status	2015-09-06 11:21:44 +00:00
nova	Properly check failed status	2015-09-06 11:21:44 +00:00
rabbitmq	Fix rabbitmq from failure during startup	2015-09-08 20:38:11 -07:00
swift	Add rsyncd image and related Ansible for Swift	2015-09-07 12:16:35 +00:00
config.yml	Ansible Glance support	2015-07-09 15:29:55 +00:00