From 2993d8d4fae6bfe8d8cb7292536a7d08d5103e6b Mon Sep 17 00:00:00 2001 From: EdLeafe Date: Mon, 8 May 2017 16:08:21 +0000 Subject: [PATCH] Correct the wording about filter options The current docs on the Filter Scheduler imply that filters can be specified per request. This is not the case, so this change corrects that page to remove this incorrect language, and make clear that only the filters specified in the config file will be used. Closes-Bug: #1689339 Change-Id: I3459a894481cab7d3961ef875015e2b8011e9a58 --- doc/source/filter_scheduler.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/filter_scheduler.rst b/doc/source/filter_scheduler.rst index 48a505cf5fec..230895a5ec4b 100644 --- a/doc/source/filter_scheduler.rst +++ b/doc/source/filter_scheduler.rst @@ -361,9 +361,9 @@ settings: filters shipped with nova. With these settings, nova will use the ``FilterScheduler`` for the scheduler -driver. The standard nova filters and MyFilter are available to the -FilterScheduler. The RamFilter, ComputeFilter, and MyFilter are used by -default when no filters are specified in the request. +driver. All of the standard nova filters and MyFilter are available to the +FilterScheduler, but just the RamFilter, ComputeFilter, and MyFilter will be +used on each request. Each filter selects hosts in a different way and has different costs. The order of ``filter_scheduler.enabled_filters`` affects scheduling performance. The