magnum/releasenotes/notes/async-bay-operations-support-9819bd06122ea9e5.yaml
Vijendar Komalla bf30b9b4cb Support for async bay operations
Current implementation of magnum bay operations are synchronous
and as a result API requests are blocked until response from HEAT
service is received. With this change bay-create, bay-update and
bay-delete calls will be asynchronous.
Please note that with this change bay-create/bay-update api calls
will return bay uuid instead of bay object and also microversion
1.2 is added for new behavior.

Change-Id: I4ca1f9f386b6417726154c466e7a9104b6e6e5e1
Closes-Bug: #1588425
2016-08-11 09:28:34 -05:00

17 lines
709 B
YAML

---
features:
- Current implementation of magnum bay operations are
synchronous and as a result API requests are blocked
until response from HEAT service is received. This release
adds support for asynchronous bay operations (bay-create,
bay-update, and bay-delete). Please note that with this
change, bay-create, bay-update API calls will return bay uuid
instead of bay object and also return HTTP status code 202
instead of 201. Microversion 1.2 is added for new behavior.
upgrade:
- Magnum bay operations API default behavior changed from
synchronous to asynchronous. User can specify
OpenStack-API-Version 1.1 in request header for synchronous
bay operations.