diff options
| author | Pierre Riteau <pierre@stackhpc.com> | 2022-09-16 10:39:42 +0200 |
|---|---|---|
| committer | Stephen Finucane <sfinucan@redhat.com> | 2022-09-20 14:50:47 +0100 |
| commit | 37129b4b4423ef8ce932ae506f0e9a6ae771ec0c (patch) | |
| tree | b19e13d66d444f3ae6f36dbf122bada361387105 | |
| parent | 6d61fccb8455367aaa37ae7bddf3b8befd3c3d88 (diff) | |
| download | nova-37129b4b4423ef8ce932ae506f0e9a6ae771ec0c.tar.gz | |
Remove mentions of removed scheduler filters
Change-Id: I1348cca8cbd8b1142dab8507c8aa1b9baf01e73c
(cherry picked from commit 4fb4f6832c156907b786571f214984894703bf16)
(cherry picked from commit c3489ed5cc21a9fa968949e04f1c7762f09b5606)
| -rw-r--r-- | doc/source/contributor/development-environment.rst | 2 | ||||
| -rw-r--r-- | nova/conf/compute.py | 12 |
2 files changed, 4 insertions, 10 deletions
diff --git a/doc/source/contributor/development-environment.rst b/doc/source/contributor/development-environment.rst index 32b8f8334e..3e19ef1ca2 100644 --- a/doc/source/contributor/development-environment.rst +++ b/doc/source/contributor/development-environment.rst @@ -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: diff --git a/nova/conf/compute.py b/nova/conf/compute.py index 5abe7694f8..5a60b43895 100644 --- a/nova/conf/compute.py +++ b/nova/conf/compute.py @@ -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 |