Fix opt description for scheduler.py

Removed the 'Services that use...' as per [0].
Also, there are no deprecated options in this file, so the
'check_deprecation_status' flag has been removed, too.

[0] https://wiki.openstack.org/wiki/ConfigOptionsConsistency

Blueprint centralize-config-options-newton

Change-Id: Ic9edf054a3431a02717ade93a92d4b0e7fd8ac81
This commit is contained in:
EdLeafe 2016-07-07 14:53:40 +00:00
parent 8e51a653c2
commit c2aabe7044
1 changed files with 0 additions and 134 deletions

View File

@ -1,5 +1,3 @@
# needs:fix_opt_description
# needs:check_deprecation_status
# needs:check_opt_group_and_type
# needs:fix_opt_description_indentation
# needs:fix_opt_registration_consistency
@ -45,10 +43,6 @@ given request.
This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.
* Services that use this:
``nova-scheduler``
* Related options:
None
@ -74,10 +68,6 @@ restrictive filters first to make the filtering process more efficient.
This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.
* Services that use this:
``nova-scheduler``
* Related options:
If the 'scheduler_use_baremetal_filters' option is False, this option has
@ -94,10 +84,6 @@ scheduling baremetal nodes, leave this at the default setting of False.
This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.
* Services that use this:
``nova-scheduler``
* Related options:
If this option is set to True, then the filters specified in the
@ -120,10 +106,6 @@ path to a filter.
This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.
* Services that use this:
``nova-scheduler``
* Related options:
scheduler_default_filters
@ -151,10 +133,6 @@ first to make the filtering process more efficient.
This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.
* Services that use this:
``nova-scheduler``
* Related options:
All of the filters in this option *must* be present in the
@ -180,10 +158,6 @@ the path to a weigher.
This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.
* Services that use this:
``nova-scheduler``
* Related options:
None
@ -205,10 +179,6 @@ usage data to query the database on each request instead.
This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.
* Services that use this:
``nova-scheduler``
* Related options:
None
@ -222,10 +192,6 @@ when the scheduler service is started up to configure the queue, and whenever
an RPC call to the scheduler is made. There is almost never any reason to ever
change this value.
* Services that use this:
``nova-scheduler``
* Related options:
None
@ -241,10 +207,6 @@ is converted from JSON to a Python data structure, and passed into the
filtering and weighing functions of the scheduler, which can use it for dynamic
configuration.
* Services that use this:
``nova-scheduler``
* Related options:
None
@ -263,10 +225,6 @@ namespace 'nova.scheduler.host_manager' of file 'setup.cfg'. For example,
option as of the Mitaka release is 'ironic_host_manager', which should be used
if you're using Ironic to provision bare-metal instances.
* Services that use this:
``nova-scheduler``
* Related options:
None
@ -294,10 +252,6 @@ Other options are:
* 'fake_scheduler' which is used for testing.
* Services that use this:
``nova-scheduler``
* Related options:
None
@ -316,10 +270,6 @@ responsible for sending a heartbeat and it will only do that as often as this
option allows. As each scheduler can work a little differently than the others,
be sure to test this with your selected scheduler.
* Services that use this:
``nova-scheduler``
* Related options:
``nova-service service_down_time``
@ -335,10 +285,6 @@ This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'IsolatedHostsFilter' filter is enabled.
* Services that use this:
``nova-scheduler``
* Related options:
scheduler/isolated_hosts
@ -355,10 +301,6 @@ This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'IsolatedHostsFilter' filter is enabled.
* Services that use this:
``nova-scheduler``
* Related options:
scheduler/isolated_images
@ -381,10 +323,6 @@ only affects scheduling if the 'IsolatedHostsFilter' filter is enabled. Even
then, this option doesn't affect the behavior of requests for isolated images,
which will *always* be restricted to isolated hosts.
* Services that use this:
``nova-scheduler``
* Related options:
scheduler/isolated_images
@ -409,10 +347,6 @@ This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'TrustedFilter' filter is enabled.
* Services that use this:
``nova-scheduler``
* Related options:
attestation_server_ca_file
@ -435,10 +369,6 @@ This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'TrustedFilter' filter is enabled.
* Services that use this:
``nova-scheduler``
* Related options:
attestation_server
@ -460,10 +390,6 @@ This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'TrustedFilter' filter is enabled.
* Services that use this:
``nova-scheduler``
* Related options:
attestation_server
@ -486,10 +412,6 @@ This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'TrustedFilter' filter is enabled.
* Services that use this:
``nova-scheduler``
* Related options:
attestation_server
@ -511,10 +433,6 @@ This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'TrustedFilter' filter is enabled.
* Services that use this:
``nova-scheduler``
* Related options:
attestation_server
@ -539,10 +457,6 @@ This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'TrustedFilter' filter is enabled.
* Services that use this:
``nova-scheduler``
* Related options:
attestation_server
@ -565,10 +479,6 @@ This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'TrustedFilter' filter is enabled.
* Services that use this:
``nova-scheduler``
* Related options:
attestation_server
@ -593,10 +503,6 @@ This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'io_ops_filter' filter is enabled.
* Services that use this:
``nova-scheduler``
* Related options:
None
@ -619,10 +525,6 @@ a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'aggregate_image_properties_isolation' filter is
enabled.
* Services that use this:
``nova-scheduler``
* Related options:
aggregate_image_properties_isolation_separator
@ -645,10 +547,6 @@ a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'aggregate_image_properties_isolation' filter is
enabled.
* Services that use this:
``nova-scheduler``
* Related options:
aggregate_image_properties_isolation_namespace
@ -669,10 +567,6 @@ This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'num_instances_filter' filter is enabled.
* Services that use this:
``nova-scheduler``
* Related options:
None
@ -696,10 +590,6 @@ only affects scheduling if the 'ram' weigher is enabled.
Valid values are numeric, either integer or float.
* Services that use this:
``nova-scheduler``
* Related options:
None
@ -728,10 +618,6 @@ only affects scheduling if the 'io_ops' weigher is enabled.
Valid values are numeric, either integer or float.
* Services that use this:
``nova-scheduler``
* Related options:
None
@ -767,10 +653,6 @@ Valid values are numeric, either integer or float.
This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.
* Services that use this:
``nova-scheduler``
* Related options:
weight_of_unavailable
@ -798,10 +680,6 @@ The final weight will be:
This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.
* Services that use this:
``nova-scheduler``
* Related options:
weight_of_unavailable
@ -820,10 +698,6 @@ host weight to 'weight_of_unavailable'.
This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.
* Services that use this:
``nova-scheduler``
* Related options:
weight_of_unavailable
@ -844,10 +718,6 @@ of any actual metric value:
This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.
* Services that use this:
``nova-scheduler``
* Related options:
weight_setting
@ -867,10 +737,6 @@ state.
Valid values are positive integers (1 or greater).
* Services that use this:
``nova-scheduler``
* Related options:
None