hardware: stop using instance cell topology in CPU pinning logic
Currently we consider the existing topology of the instance NUMA cell when
deciding on the proper way to fit instance CPUs onto host. This is
actually wrong after https://review.openstack.org/#/c/198312/. We don't
need to consider the requested topology in the CPU fitting any more as
the code that decides on the final CPU topology takes all of this into
account.
We still need to expose the topology so that the spawning process can
use that to calculate the final CPU topology for the instance, but we
should not consider this information relevant on any of the subsequent
CPU pinning fit recalculations.
Reviewed: https:/ /review. openstack. org/229574 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=cc500b2c988 0ceb62686e9f1f5 db8e6d0e7613d1
Committed: https:/
Submitter: Jenkins
Branch: master
commit cc500b2c9880ceb 62686e9f1f5db8e 6d0e7613d1
Author: Nikola Dipanov <email address hidden>
Date: Wed Sep 30 17:21:49 2015 +0100
hardware: stop using instance cell topology in CPU pinning logic
Currently we consider the existing topology of the instance NUMA cell when /review. openstack. org/#/c/ 198312/. We don't
deciding on the proper way to fit instance CPUs onto host. This is
actually wrong after https:/
need to consider the requested topology in the CPU fitting any more as
the code that decides on the final CPU topology takes all of this into
account.
We still need to expose the topology so that the spawning process can
use that to calculate the final CPU topology for the instance, but we
should not consider this information relevant on any of the subsequent
CPU pinning fit recalculations.
Change-Id: I9a947a984bf8ec 6413e9b4c45d61e 8989bf903a1
Co-Authored-By: Stephen Finucane <email address hidden>
Related-bug: 1501358
Related-bug: 1467927