From 5ae35e9cd7dd5bb98e3dfc1add4e4f5fe970d4de Mon Sep 17 00:00:00 2001 From: Stephen Gordon Date: Sun, 19 Jan 2014 17:38:51 -0500 Subject: [PATCH] Remove image requirement for boot from volume Section previously implied an image had to be specified when booting from volume. This was true previously but has since been corrected and thus it is not necessary to specify an image to successfully boot from a volume. Change-Id: I85d61726f00ece33e453ad739c4955b5f8082353 Closes-Bug: #1269767 --- doc/common/section_cli_nova_boot_from_volume.xml | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/doc/common/section_cli_nova_boot_from_volume.xml b/doc/common/section_cli_nova_boot_from_volume.xml index 6d70d167f2..515a4a87f8 100644 --- a/doc/common/section_cli_nova_boot_from_volume.xml +++ b/doc/common/section_cli_nova_boot_from_volume.xml @@ -145,12 +145,6 @@ - - You must specify an image when booting from a volume, - even though the specified image is not used. Otherwise, the - Attempt to boot from volume - no image - supplied error is returned. - You can also attach a swap disk on boot with the --swap flag, or you can attach an ephemeral disk on boot with the @@ -158,13 +152,13 @@ For example, you might enter the following command to boot from a volume. The volume is not deleted when the instance is terminated: - $ nova boot --flavor 2 --image e0b7734d-2331-42a3-b19e-067adc0da17d \ + $ nova boot --flavor 2 \ --block_device_mapping vda=3195a5a7-fd0d-4ac3-b919-7ba6cbe11d46:::0 myInstanceFromVolume +-------------------------------------+--------------------------------------+ | Property | Value | +-------------------------------------+--------------------------------------+ | OS-EXT-STS:task_state | scheduling | -| image | cirros-0.3.1-x86_64-uec | +| image | | | OS-EXT-STS:vm_state | building | | OS-EXT-SRV-ATTR:instance_name | instance-00000003 | | flavor | m1.small |