Are definitely wrong, since you can't use openstack client CLI to boot a server from an image and have nova create a volume. OSC only supports booting from an image or an existing volume, not creating a new root volume from a source image or volume snapshot.
Note that steps 4 and 5 are more accurate - it creates a bootable volume from an image (step 4) and then uses that to create the server (step 5).
The --block-device parameter description in step 3 should probably just reference the OSC CLI docs since those are the source of truth for that command:
Alternatively, just change step 3 to be the nova boot command because that's what the --block-device parameters described there are coming from, not OSC:
The description of the --block-device parameters in #3 here:
https:/ /docs.openstack .org/nova/ latest/ user/launch- instance- from-volume. html#create- volume- from-image- and-boot- instance
Are definitely wrong, since you can't use openstack client CLI to boot a server from an image and have nova create a volume. OSC only supports booting from an image or an existing volume, not creating a new root volume from a source image or volume snapshot.
Note that steps 4 and 5 are more accurate - it creates a bootable volume from an image (step 4) and then uses that to create the server (step 5).
The --block-device parameter description in step 3 should probably just reference the OSC CLI docs since those are the source of truth for that command:
https:/ /docs.openstack .org/python- openstackclient /latest/ cli/command- objects/ server. html#server- create
Alternatively, just change step 3 to be the nova boot command because that's what the --block-device parameters described there are coming from, not OSC:
https:/ /docs.openstack .org/python- novaclient/ latest/ cli/nova. html#nova- boot
That was probably a regression when someone went through that document and updated the nova CLIs to OSC CLIs.