commit 387823b36d091abbaa37efb930fc98b94a5bbb93
Author: Sean Mooney <email address hidden>
Date: Wed Jan 6 19:49:56 2021 +0000
Fix max cpu topologies with numa affinity
Nova has never supported specifying per numa node
cpu toplogies. Logically the cpu toplogy of a guest
is independent of its numa toplogy and there is no
way to model different cpu toplogies per numa node
or implement that in hardware.
The presence of the code in nova that allowed the generation
of these invalid configuration has now been removed as it
broke the automatic selection of cpu topologies based
on hw:max_[cpus|sockets|threads] flavor and image properties.
This change removed the incorrect code and related unit
tests with assert nova could generate invalid topologies.
Reviewed: https:/ /review. opendev. org/c/openstack /nova/+ /769614 /opendev. org/openstack/ nova/commit/ 387823b36d091ab baa37efb930fc98 b94a5bbb93
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 387823b36d091ab baa37efb930fc98 b94a5bbb93
Author: Sean Mooney <email address hidden>
Date: Wed Jan 6 19:49:56 2021 +0000
Fix max cpu topologies with numa affinity
Nova has never supported specifying per numa node
cpu toplogies. Logically the cpu toplogy of a guest
is independent of its numa toplogy and there is no
way to model different cpu toplogies per numa node
or implement that in hardware.
The presence of the code in nova that allowed the generation [cpus|sockets| threads] flavor and image properties.
of these invalid configuration has now been removed as it
broke the automatic selection of cpu topologies based
on hw:max_
This change removed the incorrect code and related unit
tests with assert nova could generate invalid topologies.
Closes-Bug: #1910466 1dbcc70c65ba492 549a224ce2b
Change-Id: Ia81a0fdbd950b5