Skip to content

Document RabbitMQ queue migrations in 2025.1 #1655

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 21, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 27 additions & 1 deletion doc/source/operations/upgrading-openstack.rst
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,33 @@ RabbitMQ 4.0
RabbitMQ is being upgraded to 4.0 in Epoxy. Existing transient queues must be
migrated on Caracal prior to upgrading.

.. TODO(mattcrees): Add link to docs when they exist
.. warning::

This migration will stop all services using RabbitMQ and cause an extended
API outage while queues are migrated. It should only be performed in a
pre-agreed maintenance window.

If you are using Azimuth or the ClusterAPI driver for Magnum, you should
make sure to pause reconciliation of all clusters before the API outage
window. See the `Azimuth docs
<https://azimuth-config.readthedocs.io/en/stable/operations/01-maintenance/>`__
for instructions.

Set the following variables in your kolla globals file (i.e.
$KAYOBE_CONFIG_PATH/kolla/globals.yml or $KAYOBE_CONFIG_PATH/environments/$KAYOBE_ENVIRONMENT/kolla/globals.yml):

.. code-block:: yaml

om_enable_queue_manager: true
om_enable_rabbitmq_quorum_queues: true
om_enable_rabbitmq_transient_quorum_queue: true
om_enable_rabbitmq_stream_fanout: true

Then execute the migration script:

.. code-block:: bash

$KAYOBE_CONFIG_PATH/../../tools/rabbitmq-queue-migration.sh

stackhpc.linux collection
-------------------------
Expand Down
Loading