openstack/openstack-ansible-os_tacker
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: I6e96570067d2a703ac4075f16a9e6f39ca32a6d2
This commit is contained in:
Dmitriy Rabotyagov 2024-05-25 15:35:58 +02:00
parent f629a968ac
commit 6f3c2ef620
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/tacker.conf.j2
View File

@ -100,6 +100,9 @@ rabbit_quorum_queue = {{ tacker_oslomsg_rabbit_quorum_queues }}
rabbit_transient_quorum_queue = {{ tacker_oslomsg_rabbit_transient_quorum_queues }}
rabbit_qos_prefetch_count = {{ tacker_oslomsg_rabbit_qos_prefetch_count }}
use_queue_manager = {{ tacker_oslomsg_rabbit_queue_manager }}
{% if tacker_oslomsg_rabbit_queue_manager %}
hostname = {{ [ansible_facts['hostname'], tacker_service_name] | join('-') }}
{% endif %}
rabbit_stream_fanout = {{ tacker_oslomsg_rabbit_stream_fanout }}
rabbit_quorum_delivery_limit = {{ tacker_oslomsg_rabbit_quorum_delivery_limit }}
rabbit_quorum_max_memory_bytes = {{ tacker_oslomsg_rabbit_quorum_max_memory_bytes }}