yahoo-eng-team team mailing list archive

[Chris Friesen <chris.friesen@xxxxxxxxxxxxx>]

Public bug reported:

There seems to be a bug in the NUMATopologyFilter where it doesn't
properly account for cpu_allocation_ratio.  (Detected on stable/kilo,
not sure if it applies to current master.)

To reproduce:

1) Create a flavor with a moderate number of CPUs (5, for example) and
enable hugepages by setting   "hw:mem_page_size=2048" in the flavor
extra specs.  Do not specify dedicated CPUs on the flavor.

2) Ensure that the available compute nodes have fewer CPUs free than the
number of CPUs in the flavor above.

3) Ensure that the "cpu_allocation_ratio" is big enough that
"num_free_cpus * cpu_allocation_ratio" is more than the number of CPUs
in the flavor above.

4) Enable the NUMATopologyFilter for the nova filter scheduler.

5) Try to boot an instance with the specified flavor.

This should pass, because we're not using dedicated CPUs and so the
"cpu_allocation_ratio" should apply.  However, the NUMATopologyFilter
returns 0 hosts.

It seems like the NUMATopologyFilter is failing to properly account for
the cpu_allocation_ratio when checking whether an instance can fit onto
a given host.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: compute scheduler

** Description changed:

  There seems to be a bug in the NUMATopologyFilter where it doesn't
- properly account for cpu_allocation_ratio.
+ properly account for cpu_allocation_ratio.  (Detected on stable/kilo,
+ not sure if it applies to current master.)
  
  To reproduce:
  
  1) Create a flavor with a moderate number of CPUs (5, for example) and
  enable hugepages by setting   "hw:mem_page_size=2048" in the flavor
  extra specs.  Do not specify dedicated CPUs on the flavor.
  
  2) Ensure that the available compute nodes have fewer CPUs free than the
  number of CPUs in the flavor above.
  
  3) Ensure that the "cpu_allocation_ratio" is big enough that
  "num_free_cpus * cpu_allocation_ratio" is more than the number of CPUs
  in the flavor above.
  
  4) Enable the NUMATopologyFilter for the nova filter scheduler.
  
  5) Try to boot an instance with the specified flavor.
  
  This should pass, because we're not using dedicated CPUs and so the
  "cpu_allocation_ratio" should apply.  However, the NUMATopologyFilter
  returns 0 hosts.
  
  It seems like the NUMATopologyFilter is failing to properly account for
  the cpu_allocation_ratio when checking whether an instance can fit onto
  a given host.

-- 
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/1484742

Title:
  NUMATopologyFilter doesn't account for cpu_allocation_ratio

Status in OpenStack Compute (nova):
  New

Bug description:
  There seems to be a bug in the NUMATopologyFilter where it doesn't
  properly account for cpu_allocation_ratio.  (Detected on stable/kilo,
  not sure if it applies to current master.)

  To reproduce:

  1) Create a flavor with a moderate number of CPUs (5, for example) and
  enable hugepages by setting   "hw:mem_page_size=2048" in the flavor
  extra specs.  Do not specify dedicated CPUs on the flavor.

  2) Ensure that the available compute nodes have fewer CPUs free than
  the number of CPUs in the flavor above.

  3) Ensure that the "cpu_allocation_ratio" is big enough that
  "num_free_cpus * cpu_allocation_ratio" is more than the number of CPUs
  in the flavor above.

  4) Enable the NUMATopologyFilter for the nova filter scheduler.

  5) Try to boot an instance with the specified flavor.

  This should pass, because we're not using dedicated CPUs and so the
  "cpu_allocation_ratio" should apply.  However, the NUMATopologyFilter
  returns 0 hosts.

  It seems like the NUMATopologyFilter is failing to properly account
  for the cpu_allocation_ratio when checking whether an instance can fit
  onto a given host.

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