openstack/openstack-ansible-os_blazar
Code Issues Proposed changes

Define unique hostname for QManager

Browse Source 
Due to the shortcoming of QManager implementation [1], in case of uWSGI
usage on metal hosts, the flow ends up with having the same
hostname/processname set, making services to fight over same file
under SHM.

In order to avoid this, we prepend the hostname with a service_name.
We can not change processname instead, since it will lead to the fight
between different processes of the same service.

[1] https://bugs.launchpad.net/oslo.messaging/+bug/2065922

Change-Id: I1897ce5fa0322b9effbbed3e7e2eb526d85cc215
This commit is contained in:
Dmitriy Rabotyagov 2024-05-25 13:04:12 +02:00
parent 962229f2c6
commit c43742f450
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
templates/blazar.conf.j2
View File

@ -29,6 +29,9 @@ rabbit_quorum_queue = {{ blazar_oslomsg_rabbit_quorum_queues }}
rabbit_transient_quorum_queue = {{ blazar_oslomsg_rabbit_transient_quorum_queues }}
rabbit_qos_prefetch_count = {{ blazar_oslomsg_rabbit_qos_prefetch_count }}
use_queue_manager = {{ blazar_oslomsg_rabbit_queue_manager }}
{% if blazar_oslomsg_rabbit_queue_manager %}
hostname = {{ [ansible_facts['hostname'], blazar_service_name] | join('-') }}
{% endif %}
rabbit_stream_fanout = {{ blazar_oslomsg_rabbit_stream_fanout }}
rabbit_quorum_delivery_limit = {{ blazar_oslomsg_rabbit_quorum_delivery_limit }}
rabbit_quorum_max_memory_bytes = {{ blazar_oslomsg_rabbit_quorum_max_memory_bytes }}