Nova fully fills each node before considering placing a guest on the
next node. This isn't a bug - its expected behaviour intended to
maximise number of guests that can be packed onto each compute host. If
you want to suggest alternative strategies please submit a blueprint +
spec with the proposed design & rational
** Changed in: nova
Status: In Progress => Invalid
--
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/1601994
Title:
instances always packed to NUMA node 0
Status in OpenStack Compute (nova):
Invalid
Bug description:
Description
===========
Instances are packed into node0, always. NUMA placement criteria is undefined
when not using CPU pinning and hw:numa_nodes=1.
Steps to reproduce
==================
Create a flavor w/ hw:numa_nodes=1 (hw:cpu_policy unset)
Spawn multiple instances
Check nodeset in the instance XML
Expected result
===============
Use all NUMA nodes by applying some NUMA placement criteria: Spread,
pack or random
Actual result
=============
Only node 0 is used. All others are unused.
Environment
===========
Ubuntu Xenial 16.10, OpenStack Mitaka release, Libvirt 1.3.1
Note: This issue has been found / tested on Ubuntu KVM on Power
(ppc64le arch), however, it affects all architectures.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1601994/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
