Skip to content

Commit f127559

Browse files
Zuulopenstack-gerrit
authored andcommitted
Merge "Remove hard-coded VOLUME_BACKING_FILE_SIZE from multinode docs"
2 parents 12aaa23 + 4a3cc1c commit f127559

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

doc/source/guides/multinode-lab.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -302,10 +302,10 @@ Volumes
302302

303303
DevStack will automatically use an existing LVM volume group named
304304
``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``).
309309

310310
``stack-volumes`` can be pre-created on any physical volume supported by
311311
Linux's LVM. The name of the volume group can be changed by setting

0 commit comments

Comments
 (0)