From 56778f82d655860c2f86a91158799707e21e898a Mon Sep 17 00:00:00 2001 From: Jose Castro Leon Date: Thu, 13 Dec 2018 16:15:23 +0100 Subject: [PATCH] Fix destination_type attribute in the bdm_v2 documentation All the clients using block device mapping are using the attribute destination_type and the documentation points to dest_type instead. Change-Id: Iba6e698e826d1a1898fde5cc999592f5821e3ebc Co-Authored-By: David Moreno Garcia Closes-Bug: #1808358 (cherry picked from commit 984e45544eabc5fa6b2a1c65e77c5605664b3cdf) --- doc/source/user/block-device-mapping.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/source/user/block-device-mapping.rst b/doc/source/user/block-device-mapping.rst index 4517a5bf9a1e..deebd9fa8ca8 100644 --- a/doc/source/user/block-device-mapping.rst +++ b/doc/source/user/block-device-mapping.rst @@ -127,7 +127,7 @@ fields (in addition to the ones that were already there): * `snapshot` * `blank` -* dest_type - this can have one of the following values: +* destination_type - this can have one of the following values: * `local` * `volume` @@ -161,10 +161,10 @@ fields (in addition to the ones that were already there): usage is to set it to 0 for the boot device and leave it as None for any other devices. -Valid source / dest combinations -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +Valid source / destination combinations +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Combination of the ``source_type`` and ``dest_type`` will define the +Combination of the ``source_type`` and ``destination_type`` will define the kind of block device the entry is referring to. The following combinations are supported: