Stack lifecycle scheduler hints missing orchestration UUID
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Low
|
Joe D'Andrea | ||
Kilo |
Fix Released
|
Low
|
Joe D'Andrea |
Bug Description
An "orchestration" UUID assigned to each resource, prior to the invocation of stack lifecycle plug points, allows for simple cross-referencing of heat resources before and after they are instantiated. This is most useful, for instance, in the case of holistic resource scheduling.
At one point, there was some discussion about adding these UUIDs to stack lifecycle scheduler hints, but it did not materialize.
With the debut of convergence in heat-kilo, such a UUID now exists and can be exposed through stack lifecycle scheduler hints.
Additionally, these hints can be added to other scheduled resources (e.g., Cinder Volumes).
For additional context, see the lone comment at:
https:/
description: | updated |
Changed in heat: | |
status: | New → In Progress |
Changed in heat: | |
milestone: | none → liberty-3 |
tags: | added: kilo-backport-potential |
Changed in heat: | |
status: | Fix Committed → Fix Released |
tags: | removed: kilo-backport-potential |
Changed in heat: | |
milestone: | liberty-3 → 5.0.0 |
I have a patch prepared for this, and will post it soon. I may need some help working through test cases though. :)