From d048f688a76efe4e1f59201964f4ef8f79fd565d Mon Sep 17 00:00:00 2001 From: Sandy Walsh Date: Tue, 20 Jan 2015 04:34:14 -0800 Subject: [PATCH] Fix JSONFilter docs Sheds a little light on the historical variable naming used by this filter. Removes the snark. Change-Id: If3aeee62851b7995f67687fa80f8c3151a5adc86 --- doc/source/devref/filter_scheduler.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/source/devref/filter_scheduler.rst b/doc/source/devref/filter_scheduler.rst index ea16b03b74c9..9101c60058ac 100644 --- a/doc/source/devref/filter_scheduler.rst +++ b/doc/source/devref/filter_scheduler.rst @@ -246,7 +246,9 @@ and at the same time with free disk space greater or equal than 200 GB. Many filters use data from ``scheduler_hints``, that is defined in the moment of creation of the new server for the user. The only exception for this rule is -|JsonFilter|, that takes data in some strange difficult to understand way. +|JsonFilter|, that takes data from the schedulers ``HostState`` data structure +directly. Variable naming, such as the ``$free_ram_mb`` example above, should +be based on those attributes. The |RetryFilter| filters hosts that have already been attempted for scheduling. It only passes hosts that have not been previously attempted.