Open Stack

Hi Wenzhi,
     Looks like you are adding the new --rollback option to bay-update.  If
the user does not specify this new option,
then bay-update behaves the same as before;  in other words, if it fails,
then the state of the bay will be left
in the partially updated mode.  Is this correct?  If so, this does change
the API, but does not seem to break
backward compatibility.
Ton Ngo,



From:	"Wenzhi Yu (yuywz)" <wenzhi_yu at 163.com>
To:	"openstack-dev" <openstack-dev at lists.openstack.org>
Date:	07/27/2016 04:13 AM
Subject:	[openstack-dev] [magnum] Support for bay rollback may break
            magnum	API backward compatibility



 Hi folks,

 I am working on a patch [1] to add bay rollback machanism on update
 failure. But it seems to break magnum API
 backward compatibility.

 I'm not sure how to deal with this, can you please give me your
 suggestion? Thanks!

 [1]https://review.openstack.org/#/c/343478/

 2016-07-27

 Best Regards,
 Wenzhi Yu (yuywz)
 __________________________________________________________________________
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160727/424b605c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160727/424b605c/attachment.gif>