9f4534ab58
Instead of implementing availability zones in the service table, availability zones are implemented using general aggregate metadata. This patch does not remove availability zones from the service table, a latter patch will do that. * In theory supports a single compute node in multiple availability zones * Drop availability_zone column from Aggregate table (is now a property) * map aggregate metadata 'availability_zone' so API does not change Implements blueprint aggregate-based-availability-zones Change-Id: I2a2ac5bfaa526d639dff5efa392c051347dbd9bb |
||
---|---|---|
.. | ||
aggregate-add-host-post-req.json | ||
aggregate-add-host-post-req.xml | ||
aggregate-metadata-post-req.json | ||
aggregate-metadata-post-req.xml | ||
aggregate-post-req.json | ||
aggregate-post-req.xml | ||
aggregate-post-resp.json | ||
aggregate-post-resp.xml | ||
aggregate-remove-host-post-req.json | ||
aggregate-remove-host-post-req.xml | ||
aggregate-update-post-req.json | ||
aggregate-update-post-req.xml | ||
aggregate-update-post-resp.json | ||
aggregate-update-post-resp.xml | ||
aggregates-add-host-post-resp.json | ||
aggregates-add-host-post-resp.xml | ||
aggregates-get-resp.json | ||
aggregates-get-resp.xml | ||
aggregates-list-get-resp.json | ||
aggregates-list-get-resp.xml | ||
aggregates-metadata-post-resp.json | ||
aggregates-metadata-post-resp.xml | ||
aggregates-remove-host-post-resp.json | ||
aggregates-remove-host-post-resp.xml | ||
server-post-req.json | ||
server-post-resp.json |