openstack/nova-specs
Code Issues Proposed changes

fix blueprint related to the spec overhead-pin-set

Browse Source 
It's important to note that, there are some differents between the
blueprint proposed and the spec accepted:

- It has been indicated in the approved spec that the option
  introduced will not be 'CONF.overhead_pin_set' but
  'CONF.cpu_shared_set'.

- Also instead of introducing a new policy HOST for
  hw:emulator_threads_policy it has been indicated in the approved
  spec that, the already defined policy SHARE in conjuncture with
  CONF.cpu_shared_set will make the guests emulator threads to float
  on the whole set of pCPUs defined by CONF.cpu_shared_set.

Related-to: bp overhead-pin-set
Change-Id: Ia6a7be7e3abb0cd27752fdef3721a748848b3747
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@redhat.com>
This commit is contained in:
Sahid Orentino Ferdjaoui
2018-04-17 13:43:21 +02:00
parent 9f2da51bcb
commit e5bf5a0f0d
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
specs/rocky/approved/libvirt-emulator-threads-policy.rst → specs/rocky/approved/overhead-pin-set.rst
View File

@@ -1,8 +1,8 @@
================================================
Libvirt driver emulator threads placement policy
================================================
=====================================================================
Overhead option to differ hypervisor process on a global set of pCPUs
=====================================================================
https://blueprints.launchpad.net/nova/+spec/libvirt-emulator-threads-policy
https://blueprints.launchpad.net/nova/+spec/overhead-pin-set
The Nova scheduler and the placement API determine CPU resource
utilization and instance CPU placement based on the number of vCPUs in