339ea2bdeb
The RabbitMQ role supports namespacing the service via the project_name. For example, if you change the project_name, the container name and config directory will be renamed accordingly. However the log folder is currently fixed, even though the service tries to write to one named after the project_name. This change fixes that. Whilst you might generally use vhosts, running multiple RabbitMQ services on a single node is useful at the very least for testing, or for running 'outward RabbitMQ' on the same node. This change is part of the work to support Cells v2. Partially Implements: blueprint support-nova-cells Change-Id: Ied2c24c01571327ea532ba0aaf2fc5e89de8e1fb
36 lines
1008 B
Django/Jinja
36 lines
1008 B
Django/Jinja
{
|
|
"command": "/usr/sbin/rabbitmq-server",
|
|
"config_files": [
|
|
{
|
|
"source": "{{ container_config_directory }}/rabbitmq-env.conf",
|
|
"dest": "/etc/rabbitmq/rabbitmq-env.conf",
|
|
"owner": "rabbitmq",
|
|
"perm": "0600"
|
|
},
|
|
{
|
|
"source": "{{ container_config_directory }}/rabbitmq.conf",
|
|
"dest": "/etc/rabbitmq/rabbitmq.conf",
|
|
"owner": "rabbitmq",
|
|
"perm": "0600"
|
|
},
|
|
{
|
|
"source": "{{ container_config_directory }}/definitions.json",
|
|
"dest": "/etc/rabbitmq/definitions.json",
|
|
"owner": "rabbitmq",
|
|
"perm": "0600"
|
|
}
|
|
],
|
|
"permissions": [
|
|
{
|
|
"path": "/var/lib/rabbitmq",
|
|
"owner": "rabbitmq:rabbitmq",
|
|
"recurse": true
|
|
},
|
|
{
|
|
"path": "/var/log/kolla/{{ project_name }}",
|
|
"owner": "rabbitmq:rabbitmq",
|
|
"recurse": true
|
|
}
|
|
]
|
|
}
|