Auto confirm the admin action migrate to eliminate the confusion in V3 api

Registered by GuoHui Liu

Currently the admin action migrate share the same code path with the user action resize, so the user might get confused after migrate finished but need confirm_resize or revert_resize command to confirm or revert, the migrate action should transparent to user, he/she do not need to worry about the location of the migrate, this bp change the migrate action to auto confirm it when the migration succeeds in v3.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
GuoHui Liu
Definition:
Drafting
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Are you proposing that all migrates that "succeed" should be auto-confirmed if they are initiated from v3 API? I am very much opposed to that and it runs contrary to the whole reason we have a two-phase commit for migrates, AFAIK. --dansmith

Deferred to icehouse-3 as the blueprint was not approved by the icehouse-2 blueprint approval deadline. --russellb

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguyAre you proposing that all migrates that "succeed" should be auto-confirmed if they are initiated from v3 API? I am very much opposed to that and it runs contrary to the whole reason we have a two-phase commit for migrates, AFAIK. --dansmith

Deferred to icehouse-3 as the blueprint was not approved by the icehouse-2 blueprint approval deadline. --russellb

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy

Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.