Public bug reported: 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. ** Affects: nova Importance: Undecided Status: New -- 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): New 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 -- 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