config section name [rabbitmq] is very generic and is misleading

Bug #1627705 reported by Kirill Zaitsev on 2016-09-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Murano
Medium
Russell Tweed

Bug Description

Murano uses 2 separate rabbit configs for internal communications between components and one for interaction between murano-engine and agents on VMs. This leads to much confusion. We need to rename [rabbitmq] section (the one responsible for engine <=> VM communication) into something more obvious, like [engine_agent_rabbitmq] or simply [agent_rabbitmq] or [murano_rabbitmq] or smth different

old configs should obviously not break

zhurong (zhu-rong) on 2016-09-26
Changed in murano:
assignee: nobody → zhurong (zhu-rong)

Fix proposed to branch: master
Review: https://review.openstack.org/377761

Changed in murano:
status: Confirmed → In Progress
Changed in murano:
milestone: 3.1.0 → pike-2
Changed in murano:
assignee: zhurong (zhu-rong) → nobody
status: In Progress → Triaged
importance: Low → Medium
Changed in murano:
milestone: pike-2 → pike-rc1

Change abandoned by zhurong (<email address hidden>) on branch: master
Review: https://review.openstack.org/377761
Reason: Patch has Merge Conflict and hasn't been updated for a long time. Feel free to restore this if you want.

Changed in murano:
assignee: nobody → Russell Tweed (russell-tweed)

Fix proposed to branch: master
Review: https://review.openstack.org/550815

Changed in murano:
status: Triaged → In Progress
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers