yahoo-eng-team team mailing list archive

[Alan Pevec <1386236@xxxxxxxxxxxxxxxxxx>]

** Also affects: nova/juno
   Importance: Undecided
       Status: New

** Changed in: nova/juno
   Importance: Undecided => High

** Changed in: nova/juno
       Status: New => In Progress

** Changed in: nova/juno
     Assignee: (unassigned) => Nikola Đipanov (ndipanov)

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

Title:
  NUMA scheduling will not attempt to pack an instance onto a host

Status in OpenStack Compute (Nova):
  Fix Committed
Status in OpenStack Compute (nova) juno series:
  In Progress

Bug description:
  When creating a flavor which includes "hw:numa_nodes": "1", all
  instances booted with this flavor are always pinned to NUMA node0.
  Multiple instances end up on node0 and no instances are on node1.  Our
  expectation was that instances would be balanced across NUMA nodes.

  To recreate:

  1) Ensure you have a compute node with at least 2 sockets
  2) Create a flavor with vcpus and memory which fits within one socket
  3) Add the flavor key: nova flavor-key <flavor> set hw:numa_nodes=1
  4) Boot more than 1 instances
  5) Verify where the vcpus are pinned

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