kolla-ansible

missing messaging configuration for murano agent

Bug #1649858 reported by Vladislav Belogrudov on 2016-12-14

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	kolla-ansible	Fix Released	High	Unassigned	kolla-ansible pike-3 "pike"

Bug Description

murano agents are running inside of deployed instances. They need rabbitmq connection to murano-engine, e.g. for reporting state of deployment. Corresponding section in murano.conf for murano-engine is:

[rabbitmq]
host = rabbitmq_address
port = rabbitmq port
virtual_host = murano_vhost_name_here
login = murano_user
password = murano_password
ssl = False
ca_certs =

this is copied during instance launch into /etc/murano/agent.conf . Note that we should not use here user/password for the existing cluster messaging, instead one should use separate rabbitmq cluster or at least different user/password/vhost . Also rabbitmq_address should be reached via external network

Related bug - https://bugs.launchpad.net/kolla/+bug/1620374