yahoo-eng-team team mailing list archive

[Nikola Đipanov <ndipanov@xxxxxxxxxx>]

Public bug reported:

Looking at this branch of the NUMA fitting code

https://github.com/openstack/nova/blob/51de439a4d1fe5e17d59d3aac3fd2c49556e641b/nova/virt/libvirt/driver.py#L3738

We do not account for allowed cpus when choosing viable cells for the
given instance. meaning we could chose a NUMA cell that has no viable
CPUs which we will try to pin to.

We need to consider allowed_cpus when calculating viable NUMA cells for
the instance.

** Affects: nova
     Importance: High
         Status: Confirmed


** Tags: libvirt

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1372845

Title:
  libvirt: Instance NUMA fitting code fails to account for vpu_pin_set
  config option properly

Status in OpenStack Compute (Nova):
  Confirmed

Bug description:
  Looking at this branch of the NUMA fitting code

  https://github.com/openstack/nova/blob/51de439a4d1fe5e17d59d3aac3fd2c49556e641b/nova/virt/libvirt/driver.py#L3738

  We do not account for allowed cpus when choosing viable cells for the
  given instance. meaning we could chose a NUMA cell that has no viable
  CPUs which we will try to pin to.

  We need to consider allowed_cpus when calculating viable NUMA cells
  for the instance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1372845/+subscriptions