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

Merge "Make RabbitMQ stream retention policy configurable"

2026-04-27T09:23:16+00:00

Make RabbitMQ stream retention policy configurable

2026-04-24T08:21:14+00:00

When fanout queues are set to be RabbitMQ stream, number of ready messages in stream queues grow large. This is because retention policy of stream is only applied when stream segments hit the maximum size. This change make the maximum size of RabbitMQ stream segment and the retention time configurable by new variables ``rabbitmq_stream_max_segment_size_bytes`` and ``rabbitmq_stream_segment_max_age`` respectively. NOTE: These are only applied when ``om_enable_rabbitmq_stream_fanout`` is set to ``true``. Change-Id: Iade5e525f0de8981a0e03e3340ad7552c2f40121 Signed-off-by: Seunghun Lee

Merge "Fix: Update outdated documentation"

2026-04-16T14:54:58+00:00

Fix: Update outdated documentation

2026-04-12T15:31:35+00:00

Change-Id: I5dc53f74afd9a5b565201dc9d3039d82cb65dabc Signed-off-by: Piotr Milewski

kolla-ansible: Add RabbitMQ 4.2 support and dynamic upgrade paths

2026-03-27T14:00:46+00:00

The RabbitMQ version check currently hardcodes allowed version jumps. This makes supporting new major/minor releases (like 4.2) rigid and requires modifying the core task file. This commit introduces the `rabbitmq_allowed_upgrades` variable in the role's defaults. This allows operators to define explicit version jumps (e.g., 3.13 to 4.2) and makes the upgrade logic more flexible. The version validation logic now: 1. Checks for standard minor increments (e.g., 4.1 -> 4.2). 2. Checks for explicitly defined jumps in `rabbitmq_allowed_upgrades`. By moving these definitions to defaults, operators can easily override them in globals.yml if necessary. Depends-On: https://review.opendev.org/c/openstack/kolla/+/966017 Change-Id: I0e19cf109eb5665045806b7d925779e82164c2dc Signed-off-by: Piotr Milewski

RabbitMQ: document handling stream replicas

2026-02-18T13:11:27+00:00

Closes-Bug: #2138290 Change-Id: Ic5fc1b7e801b28a2bb20b4a60146ac443ffe5ef0 Signed-off-by: Matt Crees

Add RabbitMQ management interface SSL

2025-10-17T13:34:01+00:00

This change implements RabbitMQ management interface SSL configuration when ``rabbitmq_enable_tls`` is enabled. Change-Id: Iaedad0e13f81b546af3a8e0c1e6ae7ca9da994a4 Signed-off-by: fprzewozn

Merge "Drop RabbitMQ SLURP docs"

2025-08-19T13:46:24+00:00

Drop RabbitMQ SLURP docs

2025-08-19T13:17:14+00:00

We don't need to handle extra version upgrades from Caracal -> Epoxy, so these docs can be dropped. Signed-off-by: Bartosz Bezak Change-Id: I122821b6aaf11cbf3d8695340d23c168b3373b58

Docs: update RabbitMQ HA instructions

2025-04-29T12:28:08+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