Fix configuration doc block formatting
Many of the code blocks in the configuration documentation had extra leading spaces. This resulted in the blocks being both code block formatted as well as blockquoted in the output. This patch removes leading spaces and some minor cleanup to get the formatted output correct. Change-Id: Ic4dfb49c547d51e16b673bc88d7b2b1a907e3258 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This commit is contained in:
Sean McGinnis
parent
fc9b41d733
commit
f7302e1af1
@ -224,22 +224,19 @@ check out. These may be overridden in ``local.conf`` to pull source
|
||||
from a different repo for testing, such as a Gerrit branch
|
||||
proposal. ``GIT_BASE`` points to the primary repository server.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
NOVA_REPO=$GIT_BASE/openstack/nova.git
|
||||
NOVA_BRANCH=master
|
||||
|
||||
To pull a branch directly from Gerrit, get the repo and branch from
|
||||
the Gerrit review page:
|
||||
the Gerrit review page::
|
||||
|
||||
::
|
||||
git fetch https://review.openstack.org/p/openstack/nova \
|
||||
refs/changes/50/5050/1 && git checkout FETCH_HEAD
|
||||
|
||||
git fetch https://review.openstack.org/p/openstack/nova refs/changes/50/5050/1 && git checkout FETCH_HEAD
|
||||
|
||||
The repo is the stanza following ``fetch`` and the branch is the
|
||||
stanza following that:
|
||||
|
||||
::
|
||||
The repo is the stanza following ``fetch`` and the branch is the
|
||||
stanza following that::
|
||||
|
||||
NOVA_REPO=https://review.openstack.org/p/openstack/nova
|
||||
NOVA_BRANCH=refs/changes/50/5050/1
|
||||
@ -255,7 +252,7 @@ By setting it early in the ``localrc`` section you can reference it in
|
||||
later variables. It can be useful to set it even though it is not
|
||||
changed from the default value.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
DEST=/opt/stack
|
||||
|
||||
@ -271,14 +268,14 @@ runs. It can be sent to a file in addition to the console by setting
|
||||
timestamp will be appended to the given filename for each run of
|
||||
``stack.sh``.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
LOGFILE=$DEST/logs/stack.sh.log
|
||||
|
||||
Old log files are cleaned automatically if ``LOGDAYS`` is set to the
|
||||
number of days of old log files to keep.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
LOGDAYS=1
|
||||
|
||||
@ -317,7 +314,7 @@ Example Logging Configuration
|
||||
For example, non-interactive installs probably wish to save output to
|
||||
a file, keep service logs and disable color in the stored files.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
[[local|localrc]]
|
||||
DEST=/opt/stack/
|
||||
@ -330,9 +327,7 @@ Database Backend
|
||||
Multiple database backends are available. The available databases are defined
|
||||
in the lib/databases directory.
|
||||
``mysql`` is the default database, choose a different one by putting the
|
||||
following in the ``localrc`` section:
|
||||
|
||||
::
|
||||
following in the ``localrc`` section::
|
||||
|
||||
disable_service mysql
|
||||
enable_service postgresql
|
||||
@ -347,9 +342,7 @@ backends may be available via external plugins. Enabling or disabling
|
||||
RabbitMQ is handled via the usual service functions and
|
||||
``ENABLED_SERVICES``.
|
||||
|
||||
Example disabling RabbitMQ in ``local.conf``:
|
||||
|
||||
::
|
||||
Example disabling RabbitMQ in ``local.conf``::
|
||||
|
||||
disable_service rabbit
|
||||
|
||||
@ -370,34 +363,23 @@ override toggle available that can be set in your ``local.conf``.
|
||||
|
||||
Keystone is run under Apache with ``mod_wsgi`` by default.
|
||||
|
||||
Example (Keystone)
|
||||
|
||||
::
|
||||
Example (Keystone)::
|
||||
|
||||
KEYSTONE_USE_MOD_WSGI="True"
|
||||
|
||||
Example (Nova):
|
||||
|
||||
::
|
||||
Example (Nova)::
|
||||
|
||||
NOVA_USE_MOD_WSGI="True"
|
||||
|
||||
Example (Swift):
|
||||
|
||||
::
|
||||
Example (Swift)::
|
||||
|
||||
SWIFT_USE_MOD_WSGI="True"
|
||||
|
||||
Example (Heat):
|
||||
|
||||
::
|
||||
Example (Heat)::
|
||||
|
||||
HEAT_USE_MOD_WSGI="True"
|
||||
|
||||
|
||||
Example (Cinder):
|
||||
|
||||
::
|
||||
Example (Cinder)::
|
||||
|
||||
CINDER_USE_MOD_WSGI="True"
|
||||
|
||||
@ -413,7 +395,7 @@ system you can have devstack install it from upstream, or from local
|
||||
git trees by specifying it in ``LIBS_FROM_GIT``. Multiple libraries
|
||||
can be specified as a comma separated list.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
LIBS_FROM_GIT=python-keystoneclient,oslo.config
|
||||
|
||||
@ -431,7 +413,7 @@ Each entry in the ``PROJECT_VENV`` array contains the directory name
|
||||
of a venv to be used for the project. The array index is the project
|
||||
name. Multiple projects can use the same venv if desired.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
PROJECT_VENV["glance"]=${GLANCE_DIR}.venv
|
||||
|
||||
@ -442,7 +424,7 @@ are 'optional' requirements, i.e. only needed for certain
|
||||
configurations. By default, the enabled databases will have their
|
||||
Python bindings added when they are enabled.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
ADDITIONAL_VENV_PACKAGES="python-foo, python-bar"
|
||||
|
||||
@ -453,7 +435,7 @@ By default ``stack.sh`` uses python2 (the exact version set by the
|
||||
``PYTHON2_VERSION``). This can be overriden so devstack will run
|
||||
python3 (the exact version set by ``PYTHON3_VERSION``).
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
USE_PYTHON3=True
|
||||
|
||||
@ -465,7 +447,7 @@ exist in ``$DEST``. ``stack.sh`` will freshen each repo on each run if
|
||||
``RECLONE`` is set to ``yes``. This avoids having to manually remove
|
||||
repos in order to get the current branch from ``$GIT_BASE``.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
RECLONE=yes
|
||||
|
||||
@ -478,7 +460,7 @@ requirement. If ``PIP_UPGRADE`` is set to ``True`` then existing
|
||||
required Python packages will be upgraded to the most recent version
|
||||
that matches requirements.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
PIP_UPGRADE=True
|
||||
|
||||
@ -494,7 +476,7 @@ their testing-requirements in ``stack.sh``. Setting
|
||||
these default images; in that case, you will want to populate
|
||||
``IMAGE_URLS`` with sufficient images to satisfy testing-requirements.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
DOWNLOAD_DEFAULT_IMAGES=False
|
||||
IMAGE_URLS="http://foo.bar.com/image.qcow,"
|
||||
@ -517,7 +499,7 @@ KVM on Power with QEMU 2.4 requires 512 MB to load the firmware -
|
||||
running instances on ppc64/ppc64le can choose one of the default
|
||||
created flavors as follows:
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
DEFAULT_INSTANCE_TYPE=m1.tiny
|
||||
|
||||
@ -530,14 +512,14 @@ IPv4, IPv6, or dual-stack self-service project data-network by with
|
||||
either ``IP_VERSION=4``, ``IP_VERSION=6``, or ``IP_VERSION=4+6``
|
||||
respectively.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
IP_VERSION=4+6
|
||||
|
||||
The following optional variables can be used to alter the default IPv6
|
||||
behavior:
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
IPV6_RA_MODE=slaac
|
||||
IPV6_ADDRESS_MODE=slaac
|
||||
@ -565,9 +547,7 @@ address.
|
||||
|
||||
The default value for this setting is ``4``. Dual-mode support, for
|
||||
example ``4+6`` is not currently supported. ``HOST_IPV6`` can
|
||||
optionally be used to alter the default IPv6 address
|
||||
|
||||
::
|
||||
optionally be used to alter the default IPv6 address::
|
||||
|
||||
HOST_IPV6=${some_local_ipv6_address}
|
||||
|
||||
@ -671,7 +651,7 @@ set by ``VOLUME_GROUP_NAME``, the logical volume name prefix is set with
|
||||
``VOLUME_NAME_PREFIX`` and the size of the volume backing file is set
|
||||
with ``VOLUME_BACKING_FILE_SIZE``.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
VOLUME_GROUP_NAME="stack-volumes"
|
||||
VOLUME_NAME_PREFIX="volume-"
|
||||
|
||||
Loading…
Reference in New Issue
Block a user