openstack/kolla-ansible.git/doc/source/reference/message-queues, branch stable/2024.1

Docs: update RabbitMQ HA instructions

2025-04-30T08:55:27+00:00

``kolla-ansible genconfig`` includes some tasks [1] that require containers to still be running. Move the config generation to be done before containers are stopped. Also make it clearer that containers should not be restarted with the new config until after RabbitMQ state has been reset. 1. https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/octavia/tasks/get_resources_info.yml#L2 Change-Id: I1d4fc32e5963a8e8fa4a8fc7c467cadf0f26fd5f (cherry picked from commit 44aa76cf2a5144fe7d3b148d897096cccb09604d)

Upgrade RabbitMQ docs for the Caracal release

2025-04-16T08:29:54+00:00

Updates the HA section to account for the change to quorum queues and streams by default. Also adds a note to the SLURP section as it's not needed for Epoxy. Change-Id: I3d6f8a13319b9789c07e21a2122f11c77b629ead

Merge "Add a precheck to catch RMQ SLURP upgrades" into stable/2024.1

2024-10-09T09:10:57+00:00

Merge "Fix typo in RabbitMQ versions pinning" into stable/2024.1

2024-10-09T07:46:55+00:00

Add a precheck to catch RMQ SLURP upgrades

2024-09-19T12:04:22+00:00

Given we bump the RabbitMQ version each release, there is a manual upgrade to an intermediary RabbitMQ version needed before a skip-level upgrade can be performed. Change-Id: Id8a5ebe19a50ebdc59d12667889472c803b8d7c8

Be clear that rabbitmq-upgrade is not idempotent

2024-09-18T14:45:00+00:00

This isn't obvious from reading of the docs, let's make sure users are aware. Change-Id: I0da1ad16bfab00bed7e935cca118551a6c5860c6 (cherry picked from commit ef26c7e1e65dc3b985fd443922b4edb9e9e24195)

Fix typo in RabbitMQ versions pinning

2024-09-18T14:43:22+00:00

We don't use dots in the image name Change-Id: I29172448c14a1ca9a5fa23abe701366f875959e0 (cherry picked from commit 07312e61b2c370360db8f554b477718fe657a2a0)

Add command to upgrade to a target version of RMQ

2024-08-23T08:38:46+00:00

Required before a SLURP upgrade Change-Id: I09a45d26a6075554b204e007f64122f23de5f53c (cherry picked from commit 249c1e89de0bef6a00f3abecdd8dfc820a5719fb)

RabbitMQ: correct docs on Quorum Queue migrations

2023-12-06T16:10:52+00:00

RabbitMQ does not need to be reconfigured when migrating from non-HA queues to quorum queues. Change-Id: I69d409732ff8eb7ae736e95f8a5d290efd33fa32

enable quorum queues

2023-11-30T13:53:00+00:00

This implements a global toggle `om_enable_rabbitmq_quorum_queues` to enable quorum queues for each service in RabbitMQ, similar to what was done for HA[0]. Quorum Queues are enabled by default. Quorum queues are more reliable, safer, simpler and faster than replicated mirrored classic queues[1]. Mirrored classic queues are deprecated and scheduled for removal in RabbitMQ 4.0[2]. Notice, that we do not need a new policy in the RabbitMQ definitions template, because their usage is enabled on the client side and can't be set using a policy[3]. Notice also, that quorum queues are not yet enabled in oslo.messaging for the usage of reply_ and fanout_ queues (transient queues). This will change once[4] is merged. [0]: https://review.opendev.org/c/openstack/kolla-ansible/+/867771 [1]: https://www.rabbitmq.com/quorum-queues.html [2]: https://blog.rabbitmq.com/posts/2021/08/4.0-deprecation-announcements/ [3]: https://www.rabbitmq.com/quorum-queues.html#declaring [4]: https://review.opendev.org/c/openstack/oslo.messaging/+/888479 Signed-off-by: Sven Kieske Change-Id: I6c033d460a5c9b93c346e9e47e93b159d3c27830