openstack/openstack-ansible
Code Issues Proposed changes

Merge "Enable oslomsg_rabbit_queue_manager by default"

Browse Source
This commit is contained in:
Zuul 2024-05-31 16:40:10 +00:00 committed by Gerrit Code Review
commit 868d410e1b
2 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
inventory/group_vars/all/oslo-messaging.yml
View File

@ -14,9 +14,7 @@
# Quorum Queues
oslomsg_rabbit_quorum_queues: "{{ rabbitmq_queue_replication }}"
# NOTE(noonedeadpunk): Disabled due to broken behaviour for metal setups
# See https://bugs.launchpad.net/oslo.messaging/+bug/2065922
oslomsg_rabbit_queue_manager: False
# RPC
oslomsg_rpc_transport: "{{ (groups[qdrouterd_host_group] | length > 0) | ternary('amqp', 'rabbit') }}"

6
releasenotes/notes/quorum_queues_default-2f633cd0d5ee2037.yaml
View File

@ -14,10 +14,8 @@ features:
is `True`
- oslomsg_rabbit_qos_prefetch_count: Must be set to a positive value if
``oslomsg_rabbit_stream_fanout`` is `True`
- oslomsg_rabbit_queue_manager: Disabled by default. It is recommended to
enable only for containerized deployments.
Please check `oslo.messaging bug report <https://bugs.launchpad.net/oslo.messaging/+bug/2065922>`_
for more details of why it should not be used for metal deployments.
- oslomsg_rabbit_queue_manager: Enabled if ``oslomsg_rabbit_quorum_queues``
is also set to `True`
Each service also has corresponsive variables prefixed with service name, like
``<service>_oslomsg_rabbit_stream_fanout`` to control them separately.