
Enable the RabbitMQ managment plugin. RabbitMQ managment will listen on localhost (127.0.0.1) only. NOTE: This depend on this upstream change: https://github.com/voxpupuli/puppet-rabbitmq/pull/777 Also to optimize for performance: - Disables message rates in the management plugin. - Raises the collect_statistics_interval from 5000ms to 30000ms. Related-Bug: #1815675 Change-Id: I5e73660e23fef15d1cae4c89d8b45b2456b0a110
TripleO Deployments
This directory contains files that represent individual service deployments, orchestration tools, and the configuration tools used to deploy them.
Directory Structure
Each logical grouping of services will have a directory. Example: 'timesync'. Within this directory related timesync services would exist to for example configure timesync services on baremetal or via containers.
Filenaming conventions
As a convention each deployments service filename will reflect both the deployment engine (baremetal, or containers) along with the config tool used to deploy that service.
The convention is <service-name>-<engine>-<config management tool>.
Examples:
deployment/aodh/aodh-api-container-puppet.yaml (containerized Aodh service configured with Puppet)
deployment/aodh/aodh-api-container-ansible.yaml (containerized Aodh service configured with Ansible)
deployment/timesync/chrony-baremetal-ansible.yaml (baremetal Chrony service configured with Ansible)
deployment/timesync/chrony-baremetal-puppet.yaml (baremetal Chrony service configured with Puppet)