openstack/nova
Code Issues Proposed changes

Clarify CONF.scheduler.max_attempts

Browse Source 
The help text for the scheduler's max_attempts config option is
corrected/clarified.

Change-Id: Ia0f38ac1e1b0385981c4171d553330d0419a4dc8
This commit is contained in:
Matthew Edmonds 2018-02-05 16:51:07 -05:00
parent 58328627f5
commit 7b072d4bb0
1 changed files with 5 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
nova/conf/scheduler.py
View File

@ -97,18 +97,15 @@ Related options:
deprecated_name="scheduler_max_attempts", deprecated_name="scheduler_max_attempts",
deprecated_group="DEFAULT", deprecated_group="DEFAULT",
help=""" help="""
Maximum number of schedule attempts for a chosen host. This is the maximum number of attempts that will be made for a given instance
build/move operation. It limits the number of alternate hosts returned by the
This is the maximum number of attempts that will be made to schedule an scheduler. When that list of hosts is exhausted, a MaxRetriesExceeded
instance before it is assumed that the failures aren't due to normal occasional exception is raised and the instance is set to an error state.
race conflicts, but rather some other problem. When this is reached a
MaxRetriesExceeded exception is raised, and the instance is set to an error
state.
Possible values: Possible values:
* A positive integer, where the integer corresponds to the max number of * A positive integer, where the integer corresponds to the max number of
attempts that can be made when scheduling an instance. attempts that can be made when building or moving an instance.
"""), """),
cfg.IntOpt("discover_hosts_in_cells_interval", cfg.IntOpt("discover_hosts_in_cells_interval",
default=-1, default=-1,