openstack
/
devstack
Code Issues Proposed changes

Merge "Remove hard-coded VOLUME_BACKING_FILE_SIZE from multinode docs"

This commit is contained in:
Zuul 2019-02-06 00:42:47 +00:00 committed by Gerrit Code Review
parent 12aaa23440 4a3cc1ce34
commit f1275599ad
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