Fix attaching config drive issue on Hyper-V when migrate instances
After instance resized or migrated on Hyper-V hypervisor.
The configdrive iso or vhd is copied to resized or migrated
instance, but is not attached to instance.
Because there are configurations for config drive like
config_drive_cdrom, config_drive_format, and the configurations
on different Hyper-V compute node may be different. it will need
to convert configdrive format after resized or migrated.
It is easy to convert from iso9660 or vfat to vhd, but it seems
impossible to convert from vhd to iso9660 or vfat.
So this commit just ignore the target Hyper-V compute node's
config drive configurations, leave the original config drive format.
Reviewed: https:/ /review. openstack. org/94556 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=513c6bbd365 63e57a85d33f9c9 4f4a20ab7c00f4
Committed: https:/
Submitter: Jenkins
Branch: master
commit 513c6bbd36563e5 7a85d33f9c94f4a 20ab7c00f4
Author: jufeng <email address hidden>
Date: Wed May 21 16:24:53 2014 +0800
Fix attaching config drive issue on Hyper-V when migrate instances
After instance resized or migrated on Hyper-V hypervisor.
The configdrive iso or vhd is copied to resized or migrated
instance, but is not attached to instance.
Because there are configurations for config drive like drive_cdrom, config_ drive_format, and the configurations
config_
on different Hyper-V compute node may be different. it will need
to convert configdrive format after resized or migrated.
It is easy to convert from iso9660 or vfat to vhd, but it seems
impossible to convert from vhd to iso9660 or vfat.
So this commit just ignore the target Hyper-V compute node's
config drive configurations, leave the original config drive format.
Change-Id: I349e3b2221fff0 ae217a71a91895a fd21ff7d18d
Closes-Bug: #1321640