Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility

2016-07-27 Thread Adrian Otto
AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility Hi Wenzhi, Looks like you are adding the new --rollback option to bay-update. If the user does not specify this new option,

Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility

2016-07-27 Thread Adrian Otto
AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility Hi Wenzhi, Looks like you are adding the new --rollback option to bay-update. If the user does not specify this new option,

Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility

2016-07-27 Thread Hongbin Lu
ngbin From: Ton Ngo [mailto:t...@us.ibm.com] Sent: July-27-16 9:36 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility Hi Wenzhi, Looks like you are adding the new -

Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility

2016-07-27 Thread Ton Ngo
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