Browse code
Remove hard-coded VOLUME_BACKING_FILE_SIZE from multinode docs
The default for VOLUME_BACKING_FILE_SIZE changes over time
and the docs referencing it are clearly not keeping pace so
rather than hard-code a default in the docs just remove it
since the doc already mentions the variable used to set that
size.
Change-Id: I4242584d13250872250689863d1b70c68594eefe
Matt Riedemann authored on 2019/01/31 10:50:47Showing 1 changed files
| ... | ... |
@@ -302,10 +302,10 @@ Volumes |
| 302 | 302 |
|
| 303 | 303 |
DevStack will automatically use an existing LVM volume group named |
| 304 | 304 |
``stack-volumes`` to store cloud-created volumes. If ``stack-volumes`` |
| 305 |
-doesn't exist, DevStack will set up a 10Gb loop-mounted file to contain |
|
| 306 |
-it. This obviously limits the number and size of volumes that can be |
|
| 307 |
-created inside OpenStack. The size can be overridden by setting |
|
| 308 |
-``VOLUME_BACKING_FILE_SIZE`` in ``local.conf``. |
|
| 305 |
+doesn't exist, DevStack will set up a loop-mounted file to contain |
|
| 306 |
+it. If the default size is insufficient for the number and size of volumes |
|
| 307 |
+required, it can be overridden by setting ``VOLUME_BACKING_FILE_SIZE`` in |
|
| 308 |
+``local.conf`` (sizes given in ``truncate`` compatible format, e.g. ``24G``). |
|
| 309 | 309 |
|
| 310 | 310 |
``stack-volumes`` can be pre-created on any physical volume supported by |
| 311 | 311 |
Linux's LVM. The name of the volume group can be changed by setting |