openstack
/
ironic
Code Issues Proposed changes

Merge "increase disk_erasure_coconcurrency"

This commit is contained in:
Zuul 2022-09-20 20:56:35 +00:00 committed by Gerrit Code Review
parent 0d71a2562e 556d5de9d3
commit b767a92dd8
2 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ironic/conf/deploy.py
View File

@ -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 '

10
releasenotes/notes/maximum-disk-erasure-concurrency-6d132bd84e3df4cf.yaml Normal file
View File

@ -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.