Reviewed: https://review.openstack.org/60694 Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=7103a84e3900502648e81bd4313b777f2da63f92 Submitter: Jenkins Branch: master
commit 7103a84e3900502648e81bd4313b777f2da63f92 Author: Matt Riedemann <email address hidden> Date: Sat Dec 7 13:53:33 2013 -0800
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
Reviewed: https:/ /review. openstack. org/60694 /git.openstack. org/cgit/ openstack- dev/devstack/ commit/ ?id=7103a84e390 0502648e81bd431 3b777f2da63f92
Committed: https:/
Submitter: Jenkins
Branch: master
commit 7103a84e3900502 648e81bd4313b77 7f2da63f92
Author: Matt Riedemann <email address hidden>
Date: Sat Dec 7 13:53:33 2013 -0800
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: Ia0ff5422f53eed a9a3ac4336eefec 3b9bdea6da2