Browse code
Workaround Cinder "wishlist" bug 1255593 for multi-backend volume_clear
Cinder currently only applies the volume_clear setting from the DEFAULT
section of cinder.conf if you're using a single backend.
The Cinder team has determined this is a 'wishlist' item to propagate
volume_clear to each backend, but it does impact usability and
performance.
To improve the performance of running Tempest with multi-backends in the
gate, workaround the bug in devstack.
Related-Bug: #1255593
Change-Id: Ia0ff5422f53eeda9a3ac4336eefec3b9bdea6da2
Matt Riedemann authored on 2013/12/08 06:53:33Showing 1 changed files
| ... | ... |
@@ -237,6 +237,11 @@ function configure_cinder() {
|
| 237 | 237 |
iniset $CINDER_CONF lvmdriver-2 volume_group $VOLUME_GROUP2 |
| 238 | 238 |
iniset $CINDER_CONF lvmdriver-2 volume_driver cinder.volume.drivers.lvm.LVMISCSIDriver |
| 239 | 239 |
iniset $CINDER_CONF lvmdriver-2 volume_backend_name LVM_iSCSI_2 |
| 240 |
+ # NOTE(mriedem): Work around Cinder "wishlist" bug 1255593 |
|
| 241 |
+ if [[ "$CINDER_SECURE_DELETE" == "False" ]]; then |
|
| 242 |
+ iniset $CINDER_CONF lvmdriver-1 volume_clear none |
|
| 243 |
+ iniset $CINDER_CONF lvmdriver-2 volume_clear none |
|
| 244 |
+ fi |
|
| 240 | 245 |
else |
| 241 | 246 |
iniset $CINDER_CONF DEFAULT volume_group $VOLUME_GROUP |
| 242 | 247 |
iniset $CINDER_CONF DEFAULT volume_name_template ${VOLUME_NAME_PREFIX}%s
|