yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxx>]

This wishlist bug has been open a year without any activity. I'm going
to move it to "Opinion / Wishlist", which is an easily-obtainable queue
of older requests that have come on. If you decide to work on this
consider using a blueprint [1] (maybe with a spec [2]). I'll recommend to 
read [3] if not yet done. 

References:
[1] https://blueprints.launchpad.net/nova/
[2] https://github.com/openstack/nova-specs
[3] https://wiki.openstack.org/wiki/Blueprints

** Changed in: nova
       Status: Confirmed => Opinion

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

Title:
  Specify exact CPU topology

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  The work done in https://blueprints.launchpad.net/nova/+spec/virt-
  driver-vcpu-topology to allow setting CPU topology on guests
  implements what might be called a "best attempt" algorithm -- it
  *tries* to give you the topology requested, but does not do so
  reliably. Absolute upper bounds can be set, but it's not possible to
  specify an *exact* topology.

  This seems to violate the principle of least surprise. As such, there
  should be a spec key that forces the topology specs to be *exact*, and
  produces an error if the requested topology cannot be satisfied.

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