f2a3c8ed69
Currently 3 sets of credentials are generated for MQ, per service: - rabbitmq_password - oslomsg_rpc_password - oslomsg_notify_password In each service, we should use x_oslomsg_rpc_password and x_oslomsg_notify_password, and not rabbitmq. However there is no wiring as of today. This could lead to a username like nova, on a vhost nova, with 3 different passwords. Only one would work. This patch ensures the wiring is done by default, for all the roles to be able to use x_oslomsg_notify_password and x_oslomsg_rpc_password. This is done by always referencing, in the notify part, the credentials to the rpc part. The RPC part is then a reference to the rabbitmq_password, so it's easy to upgrade from queens to Rocky without changes. If a deployer wants to override the credentials, he can do so by uncommenting the appropriate line in the user_secrets. This would then override the existing group_vars and wire the secrets appropriately. A new user should be used in that case, as written in the comments. Change-Id: I834bdc5a33f6b3c49452a9948c889caa79659f3c |
||
---|---|---|
deploy-guide/source | ||
doc | ||
etc | ||
inventory | ||
osa_toolkit | ||
playbooks | ||
releasenotes | ||
scripts | ||
tests | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
ansible-role-requirements.yml | ||
ansible-role-requirements.yml.example | ||
bindep.txt | ||
global-requirement-pins.txt | ||
LICENSE.txt | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
Vagrantfile |
Team and repository tags
OpenStack-Ansible
OpenStack-Ansible is an official OpenStack project which aims to deploy production environments from source in a way that makes it scalable while also being simple to operate, upgrade, and grow.
For an overview of the mission, repositories and related Wiki home page, please see the formal Home Page for the project.
For those looking to test OpenStack-Ansible using an All-In-One (AIO) build, please see the Quick Start guide.
For more detailed Installation and Operator documentation, please see the Deployment Guide.
If OpenStack-Ansible is missing something you'd like to see included, then we encourage you to see the Developer Documentation for more details on how you can get involved.
Developers wishing to work on the OpenStack-Ansible project should always base their work on the latest code, available from the master GIT repository at Source.
If you have some questions, or would like some assistance with
achieving your goals, then please feel free to reach out to us on the OpenStack Mailing Lists
(particularly openstack-operators or openstack-dev) or on IRC in
#openstack-ansible
on the freenode network.
OpenStack-Ansible Roles
OpenStack-Ansible offers separate role repositories for each individual role that OpenStack-Ansible supports. For individual role configuration options, see the Role Documentation.
An individual role's source code can be found at: https://git.openstack.org/cgit/openstack/openstack-ansible-<ROLENAME>.