64575519aa
This implements a global toggle `om_enable_rabbitmq_quorum_queues` to enable quorum queues for each service in RabbitMQ, similar to what was done for HA[0]. Quorum Queues are enabled by default. Quorum queues are more reliable, safer, simpler and faster than replicated mirrored classic queues[1]. Mirrored classic queues are deprecated and scheduled for removal in RabbitMQ 4.0[2]. Notice, that we do not need a new policy in the RabbitMQ definitions template, because their usage is enabled on the client side and can't be set using a policy[3]. Notice also, that quorum queues are not yet enabled in oslo.messaging for the usage of reply_ and fanout_ queues (transient queues). This will change once[4] is merged. [0]: https://review.opendev.org/c/openstack/kolla-ansible/+/867771 [1]: https://www.rabbitmq.com/quorum-queues.html [2]: https://blog.rabbitmq.com/posts/2021/08/4.0-deprecation-announcements/ [3]: https://www.rabbitmq.com/quorum-queues.html#declaring [4]: https://review.opendev.org/c/openstack/oslo.messaging/+/888479 Signed-off-by: Sven Kieske <kieske@osism.tech> Change-Id: I6c033d460a5c9b93c346e9e47e93b159d3c27830 |
||
|---|---|---|
| .. | ||
| designate-api.json.j2 | ||
| designate-backend-bind9.json.j2 | ||
| designate-central.json.j2 | ||
| designate-mdns.json.j2 | ||
| designate-producer.json.j2 | ||
| designate-sink.json.j2 | ||
| designate-worker.json.j2 | ||
| designate.conf.j2 | ||
| named.conf.j2 | ||
| pools.yaml.j2 | ||
| rndc.conf.j2 | ||
| rndc.key.j2 | ||