Clarify the help text for [scheduler]periodic_task_interval

There was some confusing/incorrect information in
the help text about the scheduler driver disabling a service
via heartbeat, which is not accurate. What this is really trying
to say is that the ComputeFilter might think a cached compute
service has outlasted it's report interval and consider it
down when using the CachingScheduler, which is the only in-tree
driver that uses this periodic task config option. So this change
updates the wording a bit.

Change-Id: I5a31f2c6c9b1bbe892a423ea4e1820eec19c2117
Related-Bug: #1749235
This commit is contained in:
Matt Riedemann 2018-02-13 12:19:35 -05:00
parent 8be8d02aa7
commit 4746a0d638
2 changed files with 7 additions and 6 deletions

View File

@ -73,13 +73,13 @@ Periodic task interval.
This value controls how often (in seconds) to run periodic tasks in the
scheduler. The specific tasks that are run for each period are determined by
the particular scheduler being used.
the particular scheduler being used. Currently the only in-tree scheduler
driver that uses this option is the ``caching_scheduler``.
If this is larger than the nova-service 'service_down_time' setting, Nova may
report the scheduler service as down. This is because the scheduler driver is
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.
If this is larger than the nova-service 'service_down_time' setting, the
ComputeFilter (if enabled) may think the compute service is down. As each
scheduler can work a little differently than the others, be sure to test this
with your selected scheduler.
Possible values:

View File

@ -49,6 +49,7 @@ for more than service_down_time, then the compute node is considered down.
Related Options:
* report_interval (service_down_time should not be less than report_interval)
* scheduler.periodic_task_interval
"""),
cfg.BoolOpt('periodic_enable',
default=True,