Murano needs dedicated rabbitmq
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Fix Released
|
High
|
Bartłomiej Daca |
Bug Description
When using separate networks for api calls and for VMs traffic, the murano agents installed on VMs are unable to communicate to the murano engine. This way none of the environments can be properly deployed.
Communication between murano agents and murano engine is realised by the rabbitmq. Kolla configures murano to use the rabbitmq that carries all the communication between OpenStack components. This rabbitmq is limited to work only in api network and api network is isolated from the network that VMs use. This is good in terms of security.
There are two options to allow murano agents to communicate with murano engine:
1. Expose rabbitmq to the external network
2. Install separate rabbitmq and expose it to the external network to handle the communication for murano.
Option 1. is considered unsafe, option 2. is suggested by the murano installation instructions.
Changed in kolla: | |
milestone: | none → newton-rc2 |
status: | New → Triaged |
Changed in kolla: | |
importance: | Undecided → Low |
importance: | Low → Medium |
importance: | Medium → Critical |
Changed in kolla: | |
status: | Won't Fix → Opinion |
milestone: | newton-rc2 → ocata-1 |
Changed in kolla: | |
assignee: | nobody → Bartłomiej Daca (bartek-daca) |
Changed in kolla: | |
milestone: | ocata-1 → ocata-2 |
Changed in kolla: | |
importance: | Low → High |
Changed in kolla: | |
milestone: | ocata-2 → ocata-3 |
Changed in kolla: | |
milestone: | ocata-3 → ocata-rc1 |
Changed in kolla: | |
milestone: | ocata-rc1 → pike-1 |
Changed in kolla: | |
milestone: | pike-2 → pike-3 |
Changed in kolla: | |
status: | In Progress → Fix Released |
You can refer to this link. www.gossamer- threads. com/lists/ openstack/ operators/ 57816
http://