cfb1c28151
My assumption is that this restart only exists for historical reasons or in order to force client re-connection and re-definition of queues to match this policy. Unfortunately the current task only executes on a single RabbitMQ node when part of a cluster, so it is ineffective in forcing reconnection. From a brief review at least when shifting from non-HA to HA this also isn't required as queues are immediately updated to reflect the new policy. Given no clear reason for the task to be present, I'm removing it ahead of making changes to the default HA policy. Change-Id: I956abe68d4d7921a4e87ae5a7694d49546bdde94 |
||
---|---|---|
defaults | ||
doc | ||
examples | ||
files | ||
meta | ||
releasenotes | ||
tasks | ||
templates | ||
tests | ||
vars | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
Vagrantfile | ||
bindep.txt | ||
manual-test.rc | ||
run_tests.sh | ||
tox.ini |
README.rst
Team and repository tags
OpenStack-Ansible RabbitMQ server
Ansible role to install OpenStack RabbitMQ server.
- Documentation for the project can be found at:
-
https://docs.openstack.org/openstack-ansible-rabbitmq_server/latest/
- Release notes for the project can be found at:
-
https://docs.openstack.org/releasenotes/openstack-ansible-rabbitmq_server/
- The project source code repository is located at:
-
https://opendev.org/openstack/openstack-ansible-rabbitmq_server/
- The project home is at:
- The project bug tracker is located at: