nova/releasenotes/notes/hyper-v-vnuma-support-ffedfaadac91bbac.yaml
Claudiu Belu 2195e4d684 Hyper-V: Adds vNUMA implementation
vNUMA can improve the performance of workloads running on virtual machines
that are configured with large amounts of memory. This feature is useful
for high-performance NUMA-aware applications, such as database or web
servers.

Returns Hyper-V host NUMA node information during get_available_resource
Adds validation for instances requiring NUMA topology (no asymmetric
topology and no CPU pinning supported).
Creates NUMA aware instances, if necessary.

The compute-cpu-topologies page in the admin-guide will have to be
updated to include Hyper-V NUMA topologies usage and configuration.

DocImpact

Change-Id: Iba2110e95e80b9511698cb7df2963fd218264c8e
Implements: blueprint hyper-v-vnuma-enable
2017-01-11 20:54:56 -05:00

16 lines
891 B
YAML

---
features:
- The nova Hyper-V driver now supports symmetric NUMA topologies. This means
that all the NUMA nodes in the NUMA topology must have the same amount of
vCPUs and memory. It can easily be requested by having the flavor
extra_spec "hw:numa_nodes", or the image property "hw_numa_nodes".
An instance with NUMA topology cannot have dynamic memory enabled. Thus,
if an instance requires a NUMA topology, it will be spawned without
dynamic memory, regardless of the value set in the "dynamic_memory_ratio"
config option in the compute node's "nova.conf" file.
In order to benefit from this feature, the host's NUMA spanning must be
disabled.
Hyper-V does not guarantee CPU pinning, thus, the nova Hyper-V driver will
not spawn instances with the flavor extra_spec "hw:cpu_policy" or image
property "hw_cpu_policy" set to "dedicated".