I'd like to open the proverbial floor for feedback regarding a problem I'm trying to tackle. It concerns Heat's assignment of stack resource UUIDs prior to a stack's instantiation. (Note that this is not the same as physical UUIDs assigned by Nova, Cinder, et. al; one ID is upstream/heat-specific, the other is downstream/service-specific.)
For a summary of the use case, problem, and three (high level) proposals to solve it, please refer to Heat bug 1516807 [1]. My thinking so far: The first two proposals are non-starters, while the third one sounds the most plausible. I imagine there are others I haven't thought of. Questions/feedback welcomed and appreciated, especially if it can help me draw a better bead on the scope of this change and what would need altering. I will then use that to help inform an initial blueprint and shepherd it forward. Thank you! jd -- Joe D’Andrea Cloud Services and Technology Research Lab AT&T Advanced Technology and Architecture [1] https://bugs.launchpad.net/heat/+bug/1516807 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
