openstack/nova
Code Issues Proposed changes

Remove mentions of removed scheduler filters

Browse Source 
Change-Id: I1348cca8cbd8b1142dab8507c8aa1b9baf01e73c
(cherry picked from commit 4fb4f6832c)
(cherry picked from commit c3489ed5cc)
(cherry picked from commit 37129b4b44)
This commit is contained in:
Pierre Riteau 2022-09-16 10:39:42 +02:00 committed by Stephen Finucane
parent e812b6f580
commit 5f1e83cfbc
2 changed files with 4 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/contributor/development-environment.rst
View File

@ -197,7 +197,7 @@ Using fake computes for tests
The number of instances supported by fake computes is not limited by physical
constraints. It allows you to perform stress tests on a deployment with few
resources (typically a laptop). Take care to avoid using scheduler filters
that will limit the number of instances per compute, such as ``AggregateCoreFilter``.
that will limit the number of instances per compute, such as ``NumInstancesFilter``.
Fake computes can also be used in multi hypervisor-type deployments in order to
take advantage of fake and "real" computes during tests:

12
nova/conf/compute.py
View File

@ -426,9 +426,7 @@ allocation_ratio_opts = [
Virtual CPU to physical CPU allocation ratio.
This option is used to influence the hosts selected by the Placement API by
configuring the allocation ratio for ``VCPU`` inventory. In addition, the
``AggregateCoreFilter`` (deprecated) will fall back to this configuration value
if no per-aggregate setting is found.
configuring the allocation ratio for ``VCPU`` inventory.
.. note::
@ -459,9 +457,7 @@ Related options:
Virtual RAM to physical RAM allocation ratio.
This option is used to influence the hosts selected by the Placement API by
configuring the allocation ratio for ``MEMORY_MB`` inventory. In addition, the
``AggregateRamFilter`` (deprecated) will fall back to this configuration value
if no per-aggregate setting is found.
configuring the allocation ratio for ``MEMORY_MB`` inventory.
.. note::
@ -487,9 +483,7 @@ Related options:
Virtual disk to physical disk allocation ratio.
This option is used to influence the hosts selected by the Placement API by
configuring the allocation ratio for ``DISK_GB`` inventory. In addition, the
``AggregateDiskFilter`` (deprecated) will fall back to this configuration value
if no per-aggregate setting is found.
configuring the allocation ratio for ``DISK_GB`` inventory.
When configured, a ratio greater than 1.0 will result in over-subscription of
the available physical disk, which can be useful for more efficiently packing