openstack/nova-specs
Code Issues Proposed changes

Add thread policy note to virt-driver-cpu-pinning

Browse Source 
CPU thread policy manipulation was ultimately not implemented as part of
the virt-driver-cpu-pinning work done in Kilo and now exists (or at
least did for Liberty, pending re-proposal for Mitaka) as a separate
proposal.

This patch updates the original specification to note this and add a
link to the newer blueprint in the hope of removing confusion.

Change-Id: If014840ac5a79dfaeffc56dd56d9627bc0208324
This commit is contained in:
Stephen Gordon
2015-09-24 13:18:54 -04:00
parent 75a2c02c79
commit cd327a0a5f
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
specs/kilo/implemented/virt-driver-cpu-pinning.rst
View File

@@ -83,6 +83,12 @@ This will only be honoured if the flavor does not already have a threads
policy set. This ensures the cloud administrator can have absolute control
over threads policy if desired.
.. NOTE::
Configurable CPU thread policies as outlined above were not implemented in
OpenStack "Kilo". This feature has since been separated out into a
separate proposal attached to
https://blueprints.launchpad.net/nova/+spec/virt-driver-cpu-thread-pinning.
The scheduler will have to be enhanced so that it considers the usage of CPUs
by existing guests. Use of a dedicated CPU policy will have to be accompanied
by the setup of aggregates to split the hosts into two groups, one allowing
@@ -286,3 +292,7 @@ work
Previously approved for Juno but implementation not completed
* https://review.openstack.org/93652
Virt driver pinning guest vCPUs threads to host pCPUs threads blueprint
* https://blueprints.launchpad.net/nova/+spec/virt-driver-cpu-thread-pinning