Properly handle shared storage during live migration
After a live migration is performed, we always try to delete the
instance files.
If the migration fails, the destination node is not cleaned up as
the HyperVLiveMigrateData object is not used at the moment and the
nova compute manager won't know whether a cleanup is needed or not.
Also, in order to support using CSVs for storing instance files, we
need to explicitly specify whether image files will be migrated or not
when requesting os-win to migrate the VM.
Reviewed: https:/ /review. openstack. org/374857 /git.openstack. org/cgit/ openstack/ compute- hyperv/ commit/ ?id=e2d304810fb 4eac15f73959abc 3a434975904ff5
Committed: https:/
Submitter: Jenkins
Branch: master
commit e2d304810fb4eac 15f73959abc3a43 4975904ff5
Author: Lucian Petrut <email address hidden>
Date: Thu Sep 22 15:46:45 2016 +0300
Properly handle shared storage during live migration
After a live migration is performed, we always try to delete the
instance files.
If the migration fails, the destination node is not cleaned up as teData object is not used at the moment and the
the HyperVLiveMigra
nova compute manager won't know whether a cleanup is needed or not.
Also, in order to support using CSVs for storing instance files, we
need to explicitly specify whether image files will be migrated or not
when requesting os-win to migrate the VM.
This change addresses those issues.
Depends-On: I48dc6da29534bf 0c477c742311ac1 5438d8b63ad
Change-Id: Icf2f258ef8900b 5970ff153a7b981 ee53e58dd2d
Partial-Bug: #1565895