Merge "Remove mentions of removed scheduler filters" into stable/wallaby

This commit is contained in:
Zuul 2023-06-21 16:32:20 +00:00 committed by Gerrit Code Review
commit d46a71f47e
2 changed files with 4 additions and 10 deletions

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:

View File

@ -425,9 +425,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::
@ -458,9 +456,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::
@ -486,9 +482,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