config section name [rabbitmq] is very generic and is misleading
Bug #1627705 reported by
Kirill Zaitsev
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Murano |
In Progress
|
Medium
|
Unassigned | ||
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_
old configs should obviously not break
| Changed in murano: | |
| assignee: | nobody → zhurong (zhu-rong) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to murano (master) | #1 |
| 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 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on murano (master) | #2 |
| Changed in murano: | |
| assignee: | nobody → Russell Tweed (russell-tweed) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to murano (master) | #3 |
| Changed in murano: | |
| status: | Triaged → In Progress |
| Changed in murano: | |
| assignee: | Russell Tweed (russell-tweed) → nobody |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on murano (master) | #4 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/