Compartmentalizing RabbitMQ
Presently all services use the single root virtual host within RabbitMQ and while this is “OK” for small to mid sized deployments however it would be better to divide services into logical resource groups within RabbitMQ which will bring with it additional security. This change set provides OSAD better compartmentalization of consumer services that use RabbitMQ. UpgradeImpact DocImpact Change-Id: I6f9d07522faf133f3c1c84a5b9046a55d5789e52 Implements: blueprint compartmentalize-rabbitmq
This commit is contained in:
parent
2f56558c6d
commit
a1c29df707
@ -144,7 +144,7 @@ use = egg:swift#xprofile
|
|||||||
paste.filter_factory = ceilometermiddleware.swift:filter_factory
|
paste.filter_factory = ceilometermiddleware.swift:filter_factory
|
||||||
control_exchange = swift
|
control_exchange = swift
|
||||||
driver = messagingv2
|
driver = messagingv2
|
||||||
url = rabbit://openstack:{{ rabbitmq_password }}@{{ groups['rabbitmq_all'][0] }}
|
url = rabbit://{{ ceilometer_rabbitmq_userid }}:{{ ceilometer_rabbitmq_password }}@{{ hostvars[groups['rabbitmq_all'][0]]['ansible_ssh_host'] }}:5672{{ ceilometer_rabbitmq_vhost }}
|
||||||
topic = notifications
|
topic = notifications
|
||||||
log_level = WARN
|
log_level = WARN
|
||||||
{% endif %}
|
{% endif %}
|
||||||
|
Loading…
x
Reference in New Issue
Block a user