429cccca35
Live migration is currently totally broken if a NUMA topology is present. This affects everything that's been regrettably stuffed in with NUMA topology including CPU pinning, hugepage support and emulator thread support. Side effects can range from simple unexpected performance hits (due to instances running on the same cores) to complete failures (due to instance cores or huge pages being mapped to CPUs/NUMA nodes that don't exist on the destination host). Until such a time as we resolve these issues, we should alert users to the fact that such issues exist. A workaround option is provided for operators that _really_ need the broken behavior, but it's defaulted to False to highlight the brokenness of this feature to unsuspecting operators. The related nova change is I217fba9138132b107e9d62895d699d238392e761 The proposed change exposes the 'enable_numa_live_migration' workarounds option for TripleO deployment. By default this feature will be disabled for NUMA topology instances. Change-Id: I16794fbfef0e6e83d3fcebb9e6bc2fcf478ebf72
10 lines
274 B
YAML
10 lines
274 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
Add support to enable/disable live-migration for NUMA topology instances
|
|
|
|
Add configuration parameter `workarounds/enable_numa_live_migration`
|
|
(defaults to false) which allows to enable/disable live-migration
|
|
for NUMA topology instances.
|
|
|