While for Xen it is a necessary safty feature to prevent migration between incompatible versions. For kvm, it is a bit more complicated; already in stable-2.8, the machine_version feature was added to the kvm hypervisor. So restore the old (unchecked) behavior for kvm in order to avoid regressions when so far valid use cases would start to fail. To achieve this, make the version-compatibility check hypervisor specific.
Klaus Aehlig (4): Extend the Hypervisor interface by VersionsSafeForMigration Use HV-specific version comparison function Move Xen-specific version test hv_xen Be optimistic for kvm migration lib/cmdlib/instance_migration.py | 4 +++- lib/hypervisor/hv_base.py | 13 +++++++++++++ lib/hypervisor/hv_kvm/__init__.py | 10 ++++++++++ lib/hypervisor/hv_xen.py | 21 +++++++++++++++++++++ lib/utils/version.py | 21 --------------------- test/py/ganeti.hypervisor.hv_xen_unittest.py | 12 ++++++++++++ test/py/ganeti.utils.version_unittest.py | 18 ------------------ 7 files changed, 59 insertions(+), 40 deletions(-) -- 2.1.0.rc2.206.gedb03e5
