valet/plugins
Chris fb512cd3ab Refactor valet_plugins
Part of support for nested stacks and updates story

To add nested stack support to Valet, make up for missing Heat resource
Orchestration IDs in nested resources by generating a subset of Heat
stack lifecycle scheduler hints for each resource in advance, store
them as opaque metadata in Valet, then leverage the metadata at Nova
scheduling time. Make additional accommodations in anticipation of
complexities brought about by adding support for stack updates.

To add a minimally viable amount of Heat `stack-update` support to
Valet, significantly restrict the number of update use cases using a
set of acceptance criteria. Skip holistic placement at `stack-update`
time in favor of Valet's existing re-plan mechanism, placing or
replacing resources one at a time, albeit still in consideration of
other resources in the same stack hierarchy.

Change-Id: I4654bcb4eacd5d64f76e262fe4c29553796e3f06
Story: #2001139
Task: #4858
2017-08-28 11:42:32 -05:00
..
common Refactor valet_plugins 2017-08-28 11:42:32 -05:00
heat Refactor valet_plugins 2017-08-28 11:42:32 -05:00
plugins Refactor valet_plugins 2017-08-28 11:42:32 -05:00
tests Refactor valet_plugins 2017-08-28 11:42:32 -05:00
__init__.py Refactor valet_plugins 2017-08-28 11:42:32 -05:00
exceptions.py Refactor valet_plugins 2017-08-28 11:42:32 -05:00
i18n.py Refactor valet_plugins 2017-08-28 11:42:32 -05:00