Browse Source

Merge "Remove hard-coded VOLUME_BACKING_FILE_SIZE from multinode docs"

Zuul 2 months ago
parent
commit
f1275599ad
1 changed files with 4 additions and 4 deletions
  1. 4
    4
      doc/source/guides/multinode-lab.rst

+ 4
- 4
doc/source/guides/multinode-lab.rst View File

@@ -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

Loading…
Cancel
Save