openstack/cinder
Code Issues Proposed changes

doc: fixes typo in multi backend configration doc

Browse Source 
changed backend_default to backend_defaults

Change-Id: Id2d66ec7fbe254a5d58ada2aa39cdf86de6f1f43
Closes-Bug: 1856859
This commit is contained in:
Shatadru Bandyopadhyay 2019-12-18 21:16:32 +05:30
parent 632f178e8e
commit 3ee18e5f6a
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/admin/blockstorage-multi-backend.rst
View File

@ -100,7 +100,7 @@ Configure shared volume driver backends
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When configuring multiple volume backends, common configuration When configuring multiple volume backends, common configuration
parameters can be shared using the `[backend_default]` section. As parameters can be shared using the `[backend_defaults]` section. As
an example: an example:
.. code-block:: ini .. code-block:: ini
@ -108,7 +108,7 @@ an example:
[DEFAULT] [DEFAULT]
enabled_backends=backend1,backend2,backend3 enabled_backends=backend1,backend2,backend3
[backend_default] [backend_defaults]
image_volume_cache_enabled = True image_volume_cache_enabled = True
volume_clear = none volume_clear = none
target_helper = tgtadm target_helper = tgtadm
@ -125,15 +125,15 @@ an example:
volume_group = cinder-volume-3 volume_group = cinder-volume-3
In this configuration, ``backend2`` and ``backend3`` have the same In this configuration, ``backend2`` and ``backend3`` have the same
``image_volume_cache_enabled`` as it is defined in the ``backend_default`` ``image_volume_cache_enabled`` as it is defined in the ``backend_defaults``
section. In other words, ``backend2`` and ``backend3`` have enabled section. In other words, ``backend2`` and ``backend3`` have enabled
the image cache features. ``image_volume_cache_enabled`` in ``backend1`` the image cache features. ``image_volume_cache_enabled`` in ``backend1``
is False, that means any overwritten configuration in a volume backend is False, that means any overwritten configuration in a volume backend
will ignore the original value in ``backend_default``. will ignore the original value in ``backend_defaults``.
.. note:: .. note::
The ``backend_default`` section should be configured according to The ``backend_defaults`` section should be configured according to
your cloud environment or your backend driver information. your cloud environment or your backend driver information.
Configure Block Storage scheduler multi back end Configure Block Storage scheduler multi back end