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

..

.idea

Fix pep8 and docstring violations

2017-05-01 19:24:57 -05:00

ostro_listener.md

Fix pep8 and docstring violations

2017-05-01 19:24:57 -05:00

ostro_release.md

Fix pep8 and docstring violations

2017-05-01 19:24:57 -05:00

ostro.md

Valet Documentation

2017-05-01 19:07:42 -05:00

rest_api.md

Add locations to POST /v1/plans API

2017-05-04 21:43:50 -05:00

valet_api.md

Fix pep8 and docstring violations

2017-05-01 19:24:57 -05:00

valet_os.md

Fix pep8 and docstring violations

2017-05-01 19:24:57 -05:00