From d4a55dd08b48cd44107904121a6426767f487221 Mon Sep 17 00:00:00 2001 From: chen-xing Date: Thu, 25 Feb 2016 18:02:53 +0800 Subject: [PATCH] [user-guide]Fix the wrong nova volume-attach command Change-Id: If4c31c3fa5e331db675f47577f6bbd7f2374b461 Closes-Bug: #1549448 --- doc/user-guide/source/cli_cheat_sheet.rst | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/doc/user-guide/source/cli_cheat_sheet.rst b/doc/user-guide/source/cli_cheat_sheet.rst index 75902585b6..6ade8ba56b 100644 --- a/doc/user-guide/source/cli_cheat_sheet.rst +++ b/doc/user-guide/source/cli_cheat_sheet.rst @@ -308,7 +308,18 @@ available .. code-block:: console $ nova volume-attach INSTANCE_ID VOLUME_ID auto - $ nova volume-attach MyVolumeInstance /dev/vdb auto + $ nova volume-attach MyVolumeInstance 573e024d-5235-49ce-8332-be1576d323f8 auto + +.. note:: + + On the Xen Hypervisor it is possible to provide a specific device name instead of + automatic allocation. For example: + + .. code-block:: console + + $ nova volume-attach MyVolumeInstance 573e024d-5235-49ce-8332-be1576d323f8 /dev/vdb + + This is not currently possible when using non-Xen hypervisors with OpenStack. Manage volumes after login into the instance