OpenStack Compute (nova)

  1. Bug #1910466
  2. Comment #21

Comment 21 for bug 1910466

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/wallaby)

Reviewed: https://review.opendev.org/c/openstack/nova/+/797653
Committed: https://opendev.org/openstack/nova/commit/c9826ca6eb10fc36fb563a42f55715ff5ac51684
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit c9826ca6eb10fc36fb563a42f55715ff5ac51684
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.

    Closes-Bug: #1910466
    Change-Id: Ia81a0fdbd950b51dbcc70c65ba492549a224ce2b
    (cherry picked from commit 387823b36d091abbaa37efb930fc98b94a5bbb93)