<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla-ansible.git/ansible/roles/rabbitmq/tasks/bootstrap.yml, branch stable/2026.1</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.1</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.1'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/'/>
<updated>2025-12-04T10:07:01+00:00</updated>
<entry>
<title>ansible-lint: Add noqa to existing no-handler violations</title>
<updated>2025-12-04T10:07:01+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2025-12-03T13:59:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=c868e52a776fa1299d849dcd9c8177e72bc05472'/>
<id>urn:sha1:c868e52a776fa1299d849dcd9c8177e72bc05472</id>
<content type='text'>
Change-Id: Ifc788b1f3f4fee23745e4a88bba208ff21366263
Signed-off-by: Michal Nasiadka &lt;mnasiadka@gmail.com&gt;
</content>
</entry>
<entry>
<title>ansible-lint: Fix yaml[truthy] in rabbitmq role</title>
<updated>2025-11-24T15:52:34+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2025-11-12T13:56:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=c51c42adc9e8554e90134730a8fac8ae31b867af'/>
<id>urn:sha1:c51c42adc9e8554e90134730a8fac8ae31b867af</id>
<content type='text'>
Change-Id: I4d4bfd90124e61bdd3fc68be0b6211d8d8f64849
Signed-off-by: Michal Nasiadka &lt;mnasiadka@gmail.com&gt;
</content>
</entry>
<entry>
<title>Rename kolla_docker to kolla_container</title>
<updated>2023-11-15T12:54:57+00:00</updated>
<author>
<name>Martin Hiner</name>
<email>m.hiner@partner.samsung.com</email>
</author>
<published>2023-11-08T13:17:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=a13d83400f126d7d9f9fc6a4c9fef8df27968959'/>
<id>urn:sha1:a13d83400f126d7d9f9fc6a4c9fef8df27968959</id>
<content type='text'>
Changes name of ansible module kolla_docker to
kolla_container.

Change-Id: I13c676ed0378aa721a21a1300f6054658ad12bc7
Signed-off-by: Martin Hiner &lt;m.hiner@partner.samsung.com&gt;
</content>
</entry>
<entry>
<title>Introduce oneshot docker_restart_policy</title>
<updated>2023-11-14T15:17:50+00:00</updated>
<author>
<name>Michal Nasiadka</name>
<email>mnasiadka@gmail.com</email>
</author>
<published>2023-04-27T09:41:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=cea076f3795010f3b870371d2ebd5d906ec81202'/>
<id>urn:sha1:cea076f3795010f3b870371d2ebd5d906ec81202</id>
<content type='text'>
docker_restart_policy: no causes systemd units to not get created
and we use it in CI to disable restarts on services.

Introducing oneshot policy to not create systemd unit for oneshot
containers (those that are running bootstrap tasks, like db
bootstrap and don't need a systemd unit), but still create systemd
units for long lived containers but with Restart=No.

Change-Id: I9e0d656f19143ec2fcad7d6d345b2c9387551604
</content>
</entry>
<entry>
<title>Fix handling of docker restart policy</title>
<updated>2019-07-18T13:39:06+00:00</updated>
<author>
<name>Radosław Piliszek</name>
<email>radoslaw.piliszek@gmail.com</email>
</author>
<published>2019-07-12T15:15:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=6a737b19686c821c32778bb847c6548d51eef002'/>
<id>urn:sha1:6a737b19686c821c32778bb847c6548d51eef002</id>
<content type='text'>
Docker has no restart policy named 'never'. It has 'no'.
This has bitten us already (see [1]) and might bite us again whenever
we want to change the restart policy to 'no'.

This patch makes our docker integration honor all valid restart policies
and only valid restart policies.
All relevant docker restart policy usages are patched as well.

I added some FIXMEs around which are relevant to kolla-ansible docker
integration. They are not fixed in here to not alter behavior.

[1] https://review.opendev.org/667363

Change-Id: I1c9764fb9bbda08a71186091aced67433ad4e3d6
Signed-off-by: Radosław Piliszek &lt;radoslaw.piliszek@gmail.com&gt;
</content>
</entry>
<entry>
<title>Updating Jinja filters to conform to Ansible 2.5+</title>
<updated>2019-05-02T13:58:09+00:00</updated>
<author>
<name>Raimund Hook</name>
<email>openstack@sting-ray.za.net</email>
</author>
<published>2019-05-02T11:55:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=84ea42bd7cf3c9931bab4729d6d7ef13940108ac'/>
<id>urn:sha1:84ea42bd7cf3c9931bab4729d6d7ef13940108ac</id>
<content type='text'>
Since Ansible 2.5, the use of jinja tests as filters has been
deprecated.

I've run the script provided by the ansible team to 'fix' the
jinja filters to conform to the newer syntax.

This fixes the deprecation warnings.

Change-Id: I844ecb7bec94e561afb09580f58b1bf83a6d00bd
Closes-bug: #1827370
</content>
</entry>
<entry>
<title>Specify 'become' for all tasks that use kolla_docker module</title>
<updated>2018-06-08T12:39:24+00:00</updated>
<author>
<name>Ha Manh Dong</name>
<email>donghm@vn.fujitsu.com</email>
</author>
<published>2018-05-30T04:25:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=30be04ea91f8a266ccc66aafd86391af79a79fa5'/>
<id>urn:sha1:30be04ea91f8a266ccc66aafd86391af79a79fa5</id>
<content type='text'>
Add become to all tasks that use the module "kolla_docker"

Change-Id: I4309c4011687b88ec31d739fd8f834fe2326ff10
Partial-Implements: blueprint ansible-specific-task-become
</content>
</entry>
<entry>
<title>Rabbitmq bootstrap enhancement</title>
<updated>2018-06-01T05:49:11+00:00</updated>
<author>
<name>MinSun</name>
<email>minsu@cisco.com</email>
</author>
<published>2018-06-01T02:22:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=ddc564d21f0fcabde3795a7d496b249133b36684'/>
<id>urn:sha1:ddc564d21f0fcabde3795a7d496b249133b36684</id>
<content type='text'>
Using rabbitmq service defined in default when
boot rabbitmq_bootstrap.
Not a bug here, just an enhancement.

Change-Id: I79f0f7efe3308ed4eb898b85a6370be1bd637d9a
</content>
</entry>
<entry>
<title>Add a new 'outward' rabbitmq instance</title>
<updated>2017-06-15T11:12:22+00:00</updated>
<author>
<name>Paul Bourke</name>
<email>paul.bourke@oracle.com</email>
</author>
<published>2017-04-05T15:57:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=d8fe3ea780c188b6e937ab6f08a8475d2330a9fa'/>
<id>urn:sha1:d8fe3ea780c188b6e937ab6f08a8475d2330a9fa</id>
<content type='text'>
Certain services such as Murano and trove require access to a rabbitmq
instance from tenant networks. [0]

Exposing the internal rabbitmq to end users is a security hole, hence
there are two options, 1) use vhosts in the existing rabbitmq, or two a
separate rabbitmq instances. Given the importance of rabbitmq to the
OpenStack deployment, we have decided to go with a separate instance.
Refer to [1] for more detail on the various options.

This change makes the rabbitmq role generic so that it can be reused, in
this case to start 'outward_rabbitmq'. It needs to be exposed via
haproxy both for network isolation and also because this is what Murano
configuration requires.

Follow on patches will be added to add a vhost in this outward instance
for Murano and other services which require access.

Based on the original work by bdaca[2]

[0] http://murano.readthedocs.io/en/stable-liberty/intro/architecture.html
[1] http://lists.openstack.org/pipermail/openstack-dev/2016-December/109091.html
[2] https://review.openstack.org/#/c/374525

Change-Id: Ib2bcc7ed4bf4f883a7cd1dfad3db89201e3cfd8d
Partial-Bug: #1620374
Depends-On: I020eb6219f89a310451becde41f6f1c7f54baadd
Co-Authored-By: Bartłomiej Daca &lt;bartek.daca@gmail.com&gt;
</content>
</entry>
<entry>
<title>Move rabbitmq precheck from start</title>
<updated>2016-08-26T15:18:04+00:00</updated>
<author>
<name>Paul Bourke</name>
<email>paul.bourke@oracle.com</email>
</author>
<published>2016-08-26T15:18:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=6c238ca3bfc082813252098735e3fd6062ad952e'/>
<id>urn:sha1:6c238ca3bfc082813252098735e3fd6062ad952e</id>
<content type='text'>
rabbitmq's start task contains a precheck. This should be part of the
other prechecks for consistency

TrivialFix

Change-Id: I7728ec3f5be3248424d74a4387925b72114b8943
</content>
</entry>
</feed>
