openstack/cinder
Code Issues Proposed changes

Update doc for missed quotation marks

Browse Source 
Update doc for missed quotation marks

Change-Id: I4993878b0b86e3b25ee6a7d86b7a406023f20118
This commit is contained in:
Minmin Ren 2019-05-10 08:39:26 +00:00
parent 1bee9f4fc0
commit a30fd0276b
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/contributor/replication.rst
View File

@ -101,7 +101,7 @@ is show below::
replication_device = backend_id:vendor-id-2,unique_key:val.... replication_device = backend_id:vendor-id-2,unique_key:val....
In this example the result of calling In this example the result of calling
``self.configuration.safe_get('replication_device)`` within the driver is the ``self.configuration.safe_get('replication_device')`` within the driver is the
following list:: following list::
[{backend_id: vendor-id-1, unique_key: val1}, [{backend_id: vendor-id-1, unique_key: val1},
@ -153,7 +153,7 @@ replicated volumes won't end up in a replicated backend.
Since the driver is reporting the ``replication_enabled`` key, we just need to Since the driver is reporting the ``replication_enabled`` key, we just need to
require it for replication volume types adding ``replication_enabled='<is> require it for replication volume types adding ``replication_enabled='<is>
True``` and also specifying it for all non replicated volume types True'`` and also specifying it for all non replicated volume types
``replication_enabled='<is> False'``. ``replication_enabled='<is> False'``.
It's up to the driver to parse the volume type info on create and set things up It's up to the driver to parse the volume type info on create and set things up