summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZuul <zuul@review.opendev.org>2022-09-20 20:56:35 +0000
committerGerrit Code Review <review@openstack.org>2022-09-20 20:56:35 +0000
commitb767a92dd8212e254980d04b89b19ed01950f01d (patch)
tree5ea1afc7ce135539bcd2446d6b778c1d6fc51cb0
parent0d71a2562e6779aa965702cca83b26977f8977bb (diff)
parent556d5de9d391eaee13e5d5ed12481f802909e1ea (diff)
downloadironic-b767a92dd8212e254980d04b89b19ed01950f01d.tar.gz
Merge "increase disk_erasure_coconcurrency"
-rw-r--r--ironic/conf/deploy.py2
-rw-r--r--releasenotes/notes/maximum-disk-erasure-concurrency-6d132bd84e3df4cf.yaml10
2 files changed, 11 insertions, 1 deletions
diff --git a/ironic/conf/deploy.py b/ironic/conf/deploy.py
index 198e0ac95..ff2020105 100644
--- a/ironic/conf/deploy.py
+++ b/ironic/conf/deploy.py
@@ -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 '
diff --git a/releasenotes/notes/maximum-disk-erasure-concurrency-6d132bd84e3df4cf.yaml b/releasenotes/notes/maximum-disk-erasure-concurrency-6d132bd84e3df4cf.yaml
new file mode 100644
index 000000000..f09421593
--- /dev/null
+++ b/releasenotes/notes/maximum-disk-erasure-concurrency-6d132bd84e3df4cf.yaml
@@ -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.