openstack/kolla-ansible.git/ansible/roles/trove/templates/trove.conf.j2, branch stable/2026.1

Fix trove-api queue manager process name

2026-11-04T15:58:50+00:00

Set a unique processname for trove-api to prevent shared-memory file collisions when running under uWSGI. Closes-Bug: #2170958 Change-Id: Iee2c76fd8ba11446688b61a9b109c8bdba0fc820 Signed-off-by: Piotr Milewski (cherry picked from commit 0931b528df42dbd1b9c32feba09ee30716156f32)

Add TLS support for MariaDB Connections

2025-07-09T11:41:04+00:00

Since Kolla-Ansible now supports TLS for MariaDB, this patch adds support for services that can use this feature. This feature can be used only when ProxySQL is used as LB. Signed-off-by: Michal Arbet Change-Id: I052c763073c5da29cb8e78004a01a22217dde5da

Don't allow quorum queues to be disabled

2025-04-09T14:20:59+00:00

We will be upgrading RabbitMQ to version 4.0 in Epoxy. This will not work without quorum queues being enabled. Change-Id: Ic6ad64bf8c62bbff175e15029eb121814032c40e

Remove om_enable_rabbitmq_high_availability

2025-04-03T08:02:34+00:00

We're going to upgrade RabbitMQ to 4.0, so this option will not longer be supported. Change-Id: Ide75a8c9086798bf4bdf5bc02d4a1be17017884f

rabbitmq: Add support for using stream queues for fanout

2025-04-02T10:59:07+00:00

The global configuration of rabbit_qos_prefetch_count = 1 in oslo.messaging is a deliberate choice that balances compatibility, fairness, and reliability across all OpenStack services. While some services (particularly those using quorum queues) could theoretically benefit from a higher or even unlimited prefetch count for performance reasons, this is not universally safe. Specifically, RabbitMQ stream queues - which are used in certain OpenStack components do not support a prefetch_count of 0. Setting this value to 0 would result in runtime errors or stalls, as the stream protocol requires a positive credit window to function properly. Oslo.messaging enforces this by raising an error if prefetch_count = 0 is set while using stream queues. A value of 1 is the lowest legal and universally compatible setting. It works safely with both stream and quorum queues. It also improves fairness in message distribution across worker processes. In distributed services like Nova, Neutron, or Cinder, this helps avoid uneven load where one worker might prefetch many messages while others remain idle. A low prefetch count ensures that messages are pulled only when the worker is ready, promoting better load balancing and more predictable performance. Although a higher prefetch value could increase throughput in certain scenarios, it comes at the cost of memory usage, risk of overloading specific nodes, and potential starvation of others. Until oslo.messaging supports queue-type-specific or per-service tuning, the value of 1 remains the safest and most predictable option that works well in mixed OpenStack environments. In summary, rabbit_qos_prefetch_count = 1 is not about optimizing raw throughput for any one service, but about ensuring stable, fair, and reliable behavior across all services that rely on oslo.messaging, regardless of the queue type or broker backend used. Change-Id: I541f704bfa2e98068096331afbdb591659cbc40b

Rabbitmq: enable quorum for transient queues

2025-03-27T08:35:35+00:00

This helps to improve the reliability of openstack services when a rabbitmq node has issues. See also: https://bugs.launchpad.net/oslo.messaging/+bug/2031497 Adjust the upgrade tests similar to what was done during the introduction of quorum queues in I6c033d460a5c9b93c346e9e47e93b159d3c27830 Closes-Bug: #2078339 Partial-Bug: #2077448 Depends-On: https://review.opendev.org/c/openstack/oslo.messaging/+/888479 Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/924623 Signed-off-by: Sven Kieske Change-Id: Idb8a8d2e560206f7697c0771c9ae3913268fa6dd

Merge "Remove Swift role"

2025-03-24T14:13:46+00:00

Add oslo.messaging Queue Manager

2025-03-24T09:17:25+00:00

Adds the variable ``om_enable_queue_manager`` to configure enabling oslo.messaging Queue Manager for all services which use RabbitMQ. This is enabled by default. This is required before we can move away from transient queues (``rabbit_transient_quorum_queue``) as Queue Manager is needed to avoid consuming all erlang atoms after some time. It is also a useful feature for debugging, as queues are now named with hostnames and services included. Also setting ``lock_path`` and mounting ``dev/shm`` is dependent on ``om_enable_queue_manager``, these are now enabled too. This will allow us to backport these features to Caracal and Dalamation without enforcing the changes right away. Why is -t added for exec commands? When using Podman, behavior differs from Docker regarding exec commands. If -t (which allocates a pseudo-terminal) is not used, the process runs as a child of podman exec without a PTY. This causes Python inside the container to assign PGID=0 because the pseudo-terminal is missing, leading to issues with non-existent paths like /proc/0/.... Adding -t ensures proper PGID assignment, preventing these issues and ensuring consistent behavior across Docker and Podman. Side-notes: The quorum queue precheck needed to be updated as queue manager puts "_fanout" on the end of the name instead. We need to override the ``[oslo_messaging_rabbit] processname`` for services running udner wsgi, as they will otherwise all use the same processname ``mod_wsgi``. This will cause Permission Errors trying to access the same file in shared memory as services run with different users. Change-Id: Iae5f268e778fbbd2b744dc71a84253ec9e758a99

Remove Swift role

2025-03-21T16:30:59+00:00

Since Swift is broken and since deprecation nobody did pick up the work to make it working - let's remove swift role and associated integrations/CI scripts. Change-Id: I08e92aaeea644053fd25f80ce1f276a495cebbfc

Ensure consistent lock_path across all services

2025-02-04T11:33:29+00:00

This patch removes the conditional check `om_enable_queue_manager` for `oslo_concurrency` as it was inconsistently applied across services and is actually unrelated to the queue manager. Simply said somewhere the conditional was present and somewhere it wasn't. While `oslo.concurrency` itself does not require a specific path, the implementation of the queue manager expects locks to be placed under `/var/lib//tmp`, making it necessary to define this path explicitly. Therefore, the lock path is set accordingly across all services, regardless of whether the queue manager is used. Additionally, this patch adds missing `lock_path` configurations where they were absent to ensure uniformity. Change-Id: I93bbaa61b2d8b5cb0d1a11783086b37a860173b6