tripleo-heat-templates/releasenotes/notes/hw-machine-type-6a0bd7bc3973c15a.yaml
Rajesh Tailor f770724740 Explicitly set KVM machine_type for migration compatibility
Currently when nova launches a guest instance, libvirt uses
current default KVM/QEMU machine type for guest.
If compute node is running on RHEL-7.3.0, then the guest will
be given rhel-7.3.0 machine type. If in future, deployment has
added additional compute nodes which uses a newer RHEL version,
the guests launched on those compute nodes will get a newer
machine type. eg. rhel-7.4.0

It is now impossible to migrate guests from RHEL-7.4 based compute
nodes to a RHEL-7.3 based compute nodes, since RHEL-7.3 won't
know about RHEL-7.4 machine type.

To deal with this problem, the proposed change will explicitly
set machine type across all compute nodes during deployment.
Now even if additional compute nodes are added to deployment with
newer OS version, instances spawned on those will get the default
machine type explicitly set during initial deployment,
allowing migrating instances from higher machine type compute
nodes to lower machine type compute nodes.

Closes-Bug: 1806529
Change-Id: Ib57bfbb94e2acdfb3bb3a828ee3b085bf68d3b4c
2018-12-20 11:50:32 +05:30

8 lines
283 B
YAML

---
features:
- |
Add parameter `NovaHWMachineType` which allows to explicitly
set machine_type across all compute nodes during deployment,
to allow migration compatibility from compute nodes with higher
host OS version to compute nodes with lower host OS version.