Browse code
Change CINDER_LVM_TYPE to 'auto' as the default
This was previously set to thin as the default, but at the time
there were failures seen with what appeared to be race conditions
when creating snapshots.
These failures are not seen locally, and we have a lot of installs
using the default auto by this point with no reports from the field
of seeing this failure. This is to be able to more extensively test
this in the gate, and hopefully get this switched over to be able
to thinly provision by default when possible.
Change-Id: I3e99adadd1c37ba8b24b6cb71a8969ffc93f75a1
Related-bug: #1642111
Sean McGinnis authored on 2017/09/06 09:56:06Showing 1 changed files
| ... | ... |
@@ -70,12 +70,11 @@ CINDER_SERVICE_PROTOCOL=${CINDER_SERVICE_PROTOCOL:-$SERVICE_PROTOCOL}
|
| 70 | 70 |
CINDER_SERVICE_LISTEN_ADDRESS=${CINDER_SERVICE_LISTEN_ADDRESS:-$SERVICE_LISTEN_ADDRESS}
|
| 71 | 71 |
|
| 72 | 72 |
# What type of LVM device should Cinder use for LVM backend |
| 73 |
-# Defaults to default, which is thick, the other valid choice |
|
| 74 |
-# is thin, which as the name implies utilizes lvm thin provisioning. |
|
| 75 |
-# Thinly provisioned LVM volumes may be more efficient when using the Cinder |
|
| 76 |
-# image cache, but there are also known race failures with volume snapshots |
|
| 77 |
-# and thinly provisioned LVM volumes, see bug 1642111 for details. |
|
| 78 |
-CINDER_LVM_TYPE=${CINDER_LVM_TYPE:-default}
|
|
| 73 |
+# Defaults to auto, which will do thin provisioning if it's a fresh |
|
| 74 |
+# volume group, otherwise it will do thick. The other valid choices are |
|
| 75 |
+# default, which is thick, or thin, which as the name implies utilizes lvm |
|
| 76 |
+# thin provisioning. |
|
| 77 |
+CINDER_LVM_TYPE=${CINDER_LVM_TYPE:-auto}
|
|
| 79 | 78 |
|
| 80 | 79 |
# Default backends |
| 81 | 80 |
# The backend format is type:name where type is one of the supported backend |