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 <david.mogar@gmail.com>
Closes-Bug: #1808358
(cherry picked from commit 984e45544e
)
This commit is contained in:
parent
734df042a1
commit
56778f82d6
@ -127,7 +127,7 @@ fields (in addition to the ones that were already there):
|
|||||||
* `snapshot`
|
* `snapshot`
|
||||||
* `blank`
|
* `blank`
|
||||||
|
|
||||||
* dest_type - this can have one of the following values:
|
* destination_type - this can have one of the following values:
|
||||||
|
|
||||||
* `local`
|
* `local`
|
||||||
* `volume`
|
* `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
|
usage is to set it to 0 for the boot device and leave it as None for any
|
||||||
other devices.
|
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
|
kind of block device the entry is referring to. The following
|
||||||
combinations are supported:
|
combinations are supported:
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user