Isn’t just handling the exception instance_not_found enough? By this time
source would’ve been cleaned up. Destination VM resources will get cleaned up
by the periodic task since the VM is not associated with this host. Am I
missing something here?
From: 王宏 [mailto:w.wangho...@gmail.com]
I would block it in the API or have the API cancelling the migration first.
I don't see a reason why to start an operation that is meant to fail, which
also has a complex chain of event, following it failure.
Regardless of the above, I think that the suggested exception handling is
could we use Taskflow https://wiki.openstack.org/wiki/TaskFlow to manage
task state and resource for this kind of tasks in Nova? Cinder has been an
pilot to use Taskflow for volume backup tasks. anyone interested in this
suggestion or has done some research to improve the live migration
Actually, I have already filed cancel of LiveMigration with using taskflow
But my approach to blueprint was not so good at that time.
So, I rewrote this blueprint from also point of russelb.
I want to repush and wanted to approved.
If you have any suggestions, ideas etc...