Open Stack

All

I inherited the task of producing an upstream spec for querying and
aborting ongoing migrations from a co-worker and submitted a new spec
https://review.openstack.org/#/c/228828//.  A related spec for pausing
an instance being migrated to enable the migration to complete is also
proposed https://review.openstack.org/#/c/229040/.

However I am now wondering if building these capabilities around the
migration object is the right way to go.  I'm now wondering if this is
right way to approach this or whether it would be better to implement
some additional operations on hte instance object?

I'm become aware that details of the progress of a migration operation
is already available to both cloud admins and instance owners via the
server get details operation, which reports the progress of migration.

Cancelling a migration could be implemented as a reset-task operation
on an instance?

The proposal in https://review.openstack.org/#/c/229040/ relates to
providing the facility to pause an instance that is being migrated
so that the migration can complete (i.e. in the case where the instance
is dirtying memory quicker than the migration processing can copy it).
This could be implemented by simply allowing the existing pause
operation on a migrating instance.  The existing implementation of
live migration means that the instance will automatically resume again
when the migration completes.  We could amend instance pause so that it
issues a warning if a pause operation is performed on an instance that
has a task state of migrating so the user is made aware that the pause
will only be temporary.

Thoughts?

-- 
Paul Carlton
Software Engineer
Cloud Services
Hewlett Packard
BUK03:T242
Longdown Avenue
Stoke Gifford
Bristol BS34 8QZ

Mobile:    +44 (0)7768 994283
Email:    mailto:paul.carlton2 at hpe.com
Hewlett-Packard Limited registered Office: Cain Road, Bracknell, Berks RG12 1HN Registered No: 690597 England.
The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error, you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as "HP CONFIDENTIAL".


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4722 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151110/c66cb96a/attachment.bin>