Async bay operations

[Drago]

There were efforts to make container operations asynchronous, but were abandoned because containers are now out of scope for Magnum. Bay operations are currently synchronous. Fortunately, they are pretty fast and the bulk of the work is done by Heat asynchronously. This would be a future enhancement for Magnum to allow for better scalability for super busy Magnum deployments.

[Wenzhi Yu (yuywz)]

Hi @Drago, just like you said "the bulk of the work is done by Heat asynchronously". So I am not convinced that making bay operations asynchronous at Magnum side makes sense. Can you please explain in detail why do you think this work is meaningful?

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/330771

[Vijendar Komalla (vijendar-komalla)]

Hi yuywz, In my opinion changing bay operations to async makes bay-operation APIs more responsive/quick.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/330771
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=bf30b9b4cb51fb4c09cfc1b1c099f3773a5ace33
Submitter: Jenkins
Branch: master

commit bf30b9b4cb51fb4c09cfc1b1c099f3773a5ace33
Author: Vijendar Komalla <email address hidden>
Date: Tue Jul 19 11:20:25 2016 -0500

    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

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/magnum 3.0.0 release.