From 4a3cc1ce341eca821ddf004ca484bd827d060507 Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Wed, 30 Jan 2019 20:50:47 -0500 Subject: [PATCH] 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 --- doc/source/guides/multinode-lab.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/source/guides/multinode-lab.rst b/doc/source/guides/multinode-lab.rst index 33820daec0..7978cd86ea 100644 --- a/doc/source/guides/multinode-lab.rst +++ b/doc/source/guides/multinode-lab.rst @@ -302,10 +302,10 @@ Volumes DevStack will automatically use an existing LVM volume group named ``stack-volumes`` to store cloud-created volumes. If ``stack-volumes`` -doesn't exist, DevStack will set up a 10Gb loop-mounted file to contain -it. This obviously limits the number and size of volumes that can be -created inside OpenStack. The size can be overridden by setting -``VOLUME_BACKING_FILE_SIZE`` in ``local.conf``. +doesn't exist, DevStack will set up a loop-mounted file to contain +it. If the default size is insufficient for the number and size of volumes +required, it can be overridden by setting ``VOLUME_BACKING_FILE_SIZE`` in +``local.conf`` (sizes given in ``truncate`` compatible format, e.g. ``24G``). ``stack-volumes`` can be pre-created on any physical volume supported by Linux's LVM. The name of the volume group can be changed by setting