yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Per comments 45 and 46, I've marked this bug as fix released for
evacuate/cold migrate and as noted, live migration with NUMA is being
handled in the Rocky release via the linked spec.

** Changed in: nova
       Status: In Progress => Fix Released

** Changed in: nova
     Assignee: sahid (sahid-ferdjaoui) => 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/1417667

Title:
  migration/evacuation/resize/unshelve of instance with NUMA topology
  needs to recalculate NUMA topology

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  I'm running nova trunk, commit 752954a.

  I configured a flavor with two vcpus and extra specs
  "hw:cpu_policy=dedicated" in order to enable vcpu pinning.

  I booted up a number of instances such that there was one instance
  affined to host cpus 12 and 13 on compute-0, and another instance
  affined to cpus 12 and 13 on compute-2.  (As reported by "virsh
  vcpupin" and "virsh dumpxml".)

  I then triggered a live migration of one instance from compute-0 to
  compute-2.  This resulted in both instances being affined to host cpus
  12 and 13 on compute-2.

  The "hw:cpu_policy=dedicated" extra spec is intended to provide
  dedicated host cpus for the instance.  In order to provide this, on a
  live migration (or cold migration, or evacuation, or resize, etc.)
  nova needs to ensure that the instance is affined to host cpus that
  are not currently being used by other instances.

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