| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
Added new configuration options to allow more specific control over |
| 5 |
some periodic processes. See the 'Upgrade' section for details. |
| 6 |
upgrade: |
| 7 |
- | |
| 8 |
The ``periodic_interval`` configuration option was being used in too |
| 9 |
many places, and as a result, it had become difficult to tune specific |
| 10 |
periodic tasks without affecting other functionality. The following |
| 11 |
configuration options should now be used in place of ``periodic_interval``: |
| 12 |
|
| 13 |
* ``backup_driver_init_check_interval`` |
| 14 |
* ``backup_driver_status_check_interval`` |
| 15 |
* ``scheduler_driver_init_wait_time`` |
| 16 |
* ``backend_stats_polling_interval`` |
| 17 |
|
| 18 |
See the help text for these options for more information. The default |
| 19 |
value of each option is 60, which has been the default value of |
| 20 |
``periodic_interval``. |
| 21 |
|
| 22 |
* If you *have not* modified ``periodic_interval``, you should see no |
| 23 |
differences from current behavior. |
| 24 |
* If you *have* modified ``periodic_interval``, please review the new |
| 25 |
options to determine which one(s) should be adjusted. Also, you should |
| 26 |
consider setting ``periodic_interval`` back to its default value of 60. |
| 27 |
|
| 28 |
A warning has been added to the ``cinder-status upgrade check`` CLI |
| 29 |
to detect whether the ``periodic_interval`` option has been modified |
| 30 |
from its default value to remind you which of the above situations |
| 31 |
currently applies to you. |
| 32 |
|
| 33 |
The ``periodic_interval`` configuration option still exists but its |
| 34 |
use is now restricted to providing a default periodicity for objects |
| 35 |
created from the ``cinder.service.Service`` class. |