openstack/openstack-ansible-os_neutron
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: Id7a52f7e7ebb658b7a5af914d4101be4632022c8
This commit is contained in:
Dmitriy Rabotyagov 2024-05-25 15:28:14 +02:00
parent cda387dd90
commit 399c83618d
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/neutron.conf.j2
View File

@ -251,6 +251,9 @@ rabbit_quorum_queue = {{ neutron_oslomsg_rabbit_quorum_queues }}
rabbit_transient_quorum_queue = {{ neutron_oslomsg_rabbit_transient_quorum_queues }}
rabbit_qos_prefetch_count = {{ neutron_oslomsg_rabbit_qos_prefetch_count }}
use_queue_manager = {{ neutron_oslomsg_rabbit_queue_manager }}
{% if neutron_oslomsg_rabbit_queue_manager %}
hostname = {{ [ansible_facts['hostname'], neutron_service_name] | join('-') }}
{% endif %}
rabbit_stream_fanout = {{ neutron_oslomsg_rabbit_stream_fanout }}
rabbit_quorum_delivery_limit = {{ neutron_oslomsg_rabbit_quorum_delivery_limit }}
rabbit_quorum_max_memory_bytes = {{ neutron_oslomsg_rabbit_quorum_max_memory_bytes }}