
When the RPC and Notify service are the same, the credentials must match - otherwise the tasks to create the user/password will overwrite with each other. If the two clusters are different, then the matching credentials and vhost will not be a problem. However, if the deployer really wishes to make sure they're different, then the vars can be overridden. Also, to ensure that the SSL value is consistently set in the conf file, we apply the bool filter. We also use the 'notify' SSL setting as the messaging system for Notifications is more likely to remain rabbitmq in our default deployment with qrouterd becoming the default for RPC messaging. Change-Id: I8e917033595660bf30c0b897f07db1bdfc2ff6d8
Team and repository tags
OpenStack-Ansible role for Bare Metal (ironic) service
This is an OpenStack-Ansible role to deploy the Bare Metal (ironic) service.
- Documentation for the project can be found at:
-
https://docs.openstack.org/openstack-ansible-os_ironic/latest
- Release notes for the project can be found at:
-
https://docs.openstack.org/releasenotes/openstack-ansible-os_ironic
- The project home is at:
Description
Languages
Jinja
60.8%
Python
26.3%
Shell
12.9%