Joe D'Andrea 1e146b1499 Add locations to POST /v1/plans API ... When determining placements for a related set of resources via OpenStack Heat, there's no a priori knowledge of specific location candidates. Thus the /v1/plans API never accounted for them. However, when it comes to ad hoc placement of a single resource (e.g., via OpenStack Nova), such knowledge *does* exist. This is one piece of a three-part change (same issue tracking ID). Change-Id: I327b87a1a1104019239547d03600cdd849ea6501		2017-05-04 21:43:50 -05:00
..
api	Add locations to POST /v1/plans API	2017-05-04 21:43:50 -05:00
cli	Resolve affinity group with flavor id	2017-05-04 17:32:46 -05:00
common	Fix erroneous Engine bootstrap	2017-05-01 21:46:30 -05:00
engine	Lazy resource status update to db	2017-05-04 21:29:24 -05:00
tests	Lazy resource status update to db	2017-05-04 21:29:24 -05:00
__init__.py	Initial commit	2016-12-12 08:50:24 -06:00