Browse code
Change CINDER_LVM_TYPE back to 'default' as the default
Change dddb2c7b5f85688de9c9b92f025df25d2f2d3016 recently
changed devstack to enable the Cinder image cache by default
and changed to use thinly provisioned LVM volumes by default.
Since then we've had a spike in thin LVM snapshot test failures
in the gate, which is by far our top gate bug at 219 hits in the
last 10 days.
So unless there is a fix on the Cinder side, this changes the
default lvm_type back to 'default' for thick provisioning.
Change-Id: I1c53bbe40177fe104ed0a222124bbc45c553b817
Related-Bug: #1642111
Matt Riedemann authored on 2016/11/22 11:10:49Showing 1 changed files
| ... | ... |
@@ -68,8 +68,12 @@ CINDER_SERVICE_PROTOCOL=${CINDER_SERVICE_PROTOCOL:-$SERVICE_PROTOCOL}
|
| 68 | 68 |
CINDER_SERVICE_LISTEN_ADDRESS=${CINDER_SERVICE_LISTEN_ADDRESS:-$SERVICE_LISTEN_ADDRESS}
|
| 69 | 69 |
|
| 70 | 70 |
# What type of LVM device should Cinder use for LVM backend |
| 71 |
-# Defaults to thin. For thick provisioning change to 'default' |
|
| 72 |
-CINDER_LVM_TYPE=${CINDER_LVM_TYPE:-thin}
|
|
| 71 |
+# Defaults to default, which is thick, the other valid choice |
|
| 72 |
+# is thin, which as the name implies utilizes lvm thin provisioning. |
|
| 73 |
+# Thinly provisioned LVM volumes may be more efficient when using the Cinder |
|
| 74 |
+# image cache, but there are also known race failures with volume snapshots |
|
| 75 |
+# and thinly provisioned LVM volumes, see bug 1642111 for details. |
|
| 76 |
+CINDER_LVM_TYPE=${CINDER_LVM_TYPE:-default}
|
|
| 73 | 77 |
|
| 74 | 78 |
# Default backends |
| 75 | 79 |
# The backend format is type:name where type is one of the supported backend |