Open Stack

Hi all,

Just FYI, the WIP patch-set is now available here:

https://review.openstack.org/241476
https://review.openstack.org/241477
https://review.openstack.org/241478
https://review.openstack.org/241479
https://review.openstack.org/241480

Thanks.

On 10/14/2015 10:05 AM, Tang Chen wrote:
> Hi, all,
>
> Please help to review this BP.
>
> https://blueprints.launchpad.net/nova/+spec/live-migration-state-machine
>
>
> Currently, the migration_status field in Migration object is 
> indicating the
> status of migration process. But in the current code, it is represented
> by pure string, like 'migrating', 'finished', and so on.
>
> The strings could be confusing to different developers, e.g. there are 3
> statuses representing the migration process is over successfully:
> 'finished', 'completed' and 'done'.
> And 2 for migration in process: 'running' and 'migrating'.
>
> So I think we should use constants or enum for these statuses.
>
>
> Furthermore, Nikola has proposed to create a state machine for the 
> statuses,
> which is part of another abandoned BP. And this is also the work I'd 
> like to go
> on with. Please refer to:
> https://review.openstack.org/#/c/197668/ 
> <https://review.openstack.org/#/c/197668/>
> https://review.openstack.org/#/c/197669/ 
> <https://review.openstack.org/#/c/197669/>
>
>
> Another proposal is: introduce a new member named "state" into Migration.
> Use a state machine to handle this Migration.state, and leave 
> migration_status
> field a descriptive human readable free-form.
>
>
> So how do you think ?
>
> Thanks.
>
>
> __________________________________________________________________________
> 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/20151104/7f48ebc3/attachment.html>