Standalone heat has no way of specifying what region to orchestrate within
Bug #1223068 reported by
Steve Baker
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Qi Zhang |
Bug Description
This is related to bug #1213291. For normal heat operation, the heat_region_name config option is used.
For standalone heat operation, middleware will need to set the region from the X-Region-Name header.
heatclient should only set the X-Region-Name header if --os-no-client-auth is specified.
Changed in heat: | |
status: | New → Triaged |
Changed in heat: | |
milestone: | havana-rc1 → next |
Changed in heat: | |
assignee: | Steve Baker (steve-stevebaker) → nobody |
Changed in heat: | |
assignee: | nobody → Matthew Oliver (matt-0) |
Changed in heat: | |
status: | Triaged → In Progress |
Changed in heat: | |
milestone: | next → juno-1 |
Changed in heat: | |
milestone: | juno-1 → juno-2 |
Changed in heat: | |
milestone: | juno-3 → juno-rc1 |
Changed in heat: | |
status: | In Progress → Triaged |
milestone: | juno-rc1 → kilo-1 |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | kilo-1 → 2015.1.0 |
To post a comment you must log in.
Matthew, any update on this? Bumping to J3 as no patch has been proposed.