openstack/openstack-manuals
Code Issues Proposed changes

[user-guide]Fix the wrong nova volume-attach command

Browse Source 
Change-Id: If4c31c3fa5e331db675f47577f6bbd7f2374b461
Closes-Bug: #1549448
This commit is contained in:
chen-xing 2016-02-25 18:02:53 +08:00 committed by chen.xing
parent 6abb031851
commit d4a55dd08b
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/user-guide/source/cli_cheat_sheet.rst
View File

@ -308,7 +308,18 @@ available
.. code-block:: console .. code-block:: console
$ nova volume-attach INSTANCE_ID VOLUME_ID auto $ 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 Manage volumes after login into the instance