From a30fd0276babf566d25aeb4272342ae8e096a472 Mon Sep 17 00:00:00 2001 From: Minmin Ren Date: Fri, 10 May 2019 08:39:26 +0000 Subject: [PATCH] Update doc for missed quotation marks Update doc for missed quotation marks Change-Id: I4993878b0b86e3b25ee6a7d86b7a406023f20118 --- doc/source/contributor/replication.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/contributor/replication.rst b/doc/source/contributor/replication.rst index e1987233b1c..faedadefb82 100644 --- a/doc/source/contributor/replication.rst +++ b/doc/source/contributor/replication.rst @@ -101,7 +101,7 @@ is show below:: replication_device = backend_id:vendor-id-2,unique_key:val.... 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:: [{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 require it for replication volume types adding ``replication_enabled=' -True``` and also specifying it for all non replicated volume types +True'`` and also specifying it for all non replicated volume types ``replication_enabled=' False'``. It's up to the driver to parse the volume type info on create and set things up