I think the discussion about whether or not this needs a microversion is missing the bigger question of whether or not this should be in the API to begin with. If it's safe to rollback from this error state why not just do that automatically in Nova? If it's proposed for the API because it's not considered safe I don't agree it should be in the API. This is not an API that's restricted to admins by default.
However if this is going to be exposed in the API I lean towards this not needing a microversion. It's a new policy in the usage of the API, not a change to the API. To me it seems like adding a microversion because a policy rule was changed. I know we should have some sort of signal here for users, but I think we need to look at different ways to signal this type of change. -Andrew On Tue, Aug 2, 2016, at 02:11 AM, [email protected] wrote: > patchset url: https://review.openstack.org/#/c/334747/ > > > > > Allow "revert_resize" to recover error instance after resize/migrate. > > When resize/migrate instance, if error occurs on source compute node, > instance state can rollback to active currently. But if error occurs > in "finish_resize" function on destination compute node, the instance > state would not rollback to active. > > This patch is to rollback instance state from error to active when > resize or migrate action failed on destination compute node.. > > > > > Best, > Rong Han > ____________________________________________________________________- > ________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev- > [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
