Merge "increase disk_erasure_coconcurrency"
This commit is contained in:
commit
b767a92dd8
@ -108,7 +108,7 @@ opts = [
|
||||
'state. If True, shred will be invoked and cleaning '
|
||||
'will continue.')),
|
||||
cfg.IntOpt('disk_erasure_concurrency',
|
||||
default=1,
|
||||
default=4,
|
||||
min=1,
|
||||
mutable=True,
|
||||
help=_('Defines the target pool size used by Ironic Python '
|
||||
|
@ -0,0 +1,10 @@
|
||||
---
|
||||
other:
|
||||
- |
|
||||
The maximum disk erasure concurrency setting,
|
||||
``[deploy]disk_erasure_concurrency`` has been incremed to 4.
|
||||
Previously, this was kept at 1 in order to maintain continuity of
|
||||
experience, but operators have not reported any issues with an increased
|
||||
concurrency, and as such we feel comfortable upstream enabling concurrent
|
||||
disk erasure/cleaning. This setting applies to the ``erase_devices`` clean
|
||||
step.
|
Loading…
x
Reference in New Issue
Block a user