summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPierre Riteau <pierre@stackhpc.com>2022-09-16 10:39:42 +0200
committerPierre Riteau <pierre@stackhpc.com>2022-09-16 10:39:42 +0200
commit4fb4f6832c156907b786571f214984894703bf16 (patch)
treecba63fd7d500fff2e8f589348a623df86d3638e4 /doc
parent797779688f0515cfa5eb58f935a376cbc08d33e4 (diff)
downloadnova-4fb4f6832c156907b786571f214984894703bf16.tar.gz
Remove mentions of removed scheduler filters
Change-Id: I1348cca8cbd8b1142dab8507c8aa1b9baf01e73c
Diffstat (limited to 'doc')
-rw-r--r--doc/source/contributor/development-environment.rst2
1 files changed, 1 insertions, 1 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: