openstack
/
devstack
Code Issues Proposed changes

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
This commit is contained in:
Matt Riedemann 2019-01-30 20:50:47 -05:00 committed by Ian Wienand
parent ec8285271e
commit 4a3cc1ce34
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/guides/multinode-lab.rst
View File

@ -302,10 +302,10 @@ Volumes
DevStack will automatically use an existing LVM volume group named DevStack will automatically use an existing LVM volume group named
``stack-volumes`` to store cloud-created volumes. If ``stack-volumes`` ``stack-volumes`` to store cloud-created volumes. If ``stack-volumes``
doesn't exist, DevStack will set up a 10Gb loop-mounted file to contain doesn't exist, DevStack will set up a loop-mounted file to contain
it. This obviously limits the number and size of volumes that can be it. If the default size is insufficient for the number and size of volumes
created inside OpenStack. The size can be overridden by setting required, it can be overridden by setting ``VOLUME_BACKING_FILE_SIZE`` in
``VOLUME_BACKING_FILE_SIZE`` in ``local.conf``. ``local.conf`` (sizes given in ``truncate`` compatible format, e.g. ``24G``).
``stack-volumes`` can be pre-created on any physical volume supported by ``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 Linux's LVM. The name of the volume group can be changed by setting