commit cf73bff104b6557e74c7eb0c4d210c0b6ab4b199
Author: Matt Riedemann <email address hidden>
Date: Wed Oct 3 10:27:22 2018 -0400
doc: fix and clarify --block-device usage in user docs
The docs on create a volume-backed server from the command
line were wrong in a few ways:
* The openstack server create command does not currently allow
booting from a volume where a source image is provided and
nova creates the volume from the image and uses that volume
as the root disk. The nova boot command supports that, so the
docs are updated to call out the nova boot command since that
is the appropriate command in this case (even the syntax with
the openstack server create --block-device was wrong).
* When creating a server from a bootable volume with the OSC CLI,
either the --volume or --block-device options should be used
for a single volume, but not both. The docs were using both, so
the latter is dropped and a note is added which links to the CLI
documentation for more details on --block-device option usage.
Reviewed: https:/ /review. opendev. org/694450 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=cf73bff104b 6557e74c7eb0c4d 210c0b6ab4b199
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit cf73bff104b6557 e74c7eb0c4d210c 0b6ab4b199
Author: Matt Riedemann <email address hidden>
Date: Wed Oct 3 10:27:22 2018 -0400
doc: fix and clarify --block-device usage in user docs
The docs on create a volume-backed server from the command
line were wrong in a few ways:
* The openstack server create command does not currently allow
booting from a volume where a source image is provided and
nova creates the volume from the image and uses that volume
as the root disk. The nova boot command supports that, so the
docs are updated to call out the nova boot command since that
is the appropriate command in this case (even the syntax with
the openstack server create --block-device was wrong).
* When creating a server from a bootable volume with the OSC CLI,
either the --volume or --block-device options should be used
for a single volume, but not both. The docs were using both, so
the latter is dropped and a note is added which links to the CLI
documentation for more details on --block-device option usage.
Conflicts:
doc/ source/ user/launch- instance- from-volume. rst
NOTE(amodi): The conflict is due to not having 5f51f13d1a5832b d7dbf9f690fcad7 in Pike
Ifa2e2bbb4c
Change-Id: I985b870759d6c2 1ef9357b04f3909 9c02354f135 d9f2e766431f18a adeff54a40) dd9b56aa9a93768 d05e4dde0e) 75d7be296fef7f7 2585689729)
Closes-Bug: #1794827
(cherry picked from commit 16027094ebabc5c
(cherry picked from commit 6a6d0e943443a9c
(cherry picked from commit c55eff39f22bec8