openstack/openstack-manuals
Code Issues Proposed changes

[user-guide] Fix the Legacy openstack command

Browse Source 
This patch use 'openstack' command to replace the 'cinder' commands

Change-Id: I27fea5ed02554d33992945a4ba224d9ff32a1668
Implements: blueprint use-openstack-command
This commit is contained in:
luqitao 2017-03-18 03:43:40 -04:00
parent 6750467082
commit 039e1046bd
1 changed files with 33 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

54
doc/common/cli-manage-volumes.rst
View File

@ -24,20 +24,20 @@ Possible use cases for data migration include:
* Free up space in a thinly-provisioned back end. * Free up space in a thinly-provisioned back end.
Migrate a volume with the :command:`cinder migrate` command, as shown in the Migrate a volume with the :command:`openstack volume migrate` command, as shown
following example: in the following example:
.. code-block:: console .. code-block:: console
$ cinder migrate --force-host-copy <True|False> $ openstack volume migrate [-h] --host <host> [--force-host-copy]
--lock-volume <True|False> [--lock-volume | --unlock-volume]
<volume> <host> <volume>
In this example, ``--force-host-copy True`` forces the generic In this example, ``--force-host-copy`` forces the generic
host-based migration mechanism and bypasses any driver optimizations. host-based migration mechanism and bypasses any driver optimizations.
``--lock-volume <True|False>`` applies to the available volume. ``--lock-volume | --unlock-volume`` applies to the available volume.
To determine whether the termination of volume migration caused by other To determine whether the termination of volume migration caused by other
commands. ``True`` locks the volume state and does not allow the commands. ``--lock-volume`` locks the volume state and does not allow the
migration to be aborted. migration to be aborted.
.. note:: .. note::
@ -608,16 +608,17 @@ you can manage and unmanage snapshots.
Manage a snapshot Manage a snapshot
----------------- -----------------
Manage a snapshot with the :command:`openstack snapshot set` command: Manage a snapshot with the :command:`openstack volume snapshot set` command:
.. code-block:: console .. code-block:: console
$ openstack snapshot set \ $ openstack volume snapshot set [-h]
[--name <name>] \ [--name <name>]
[--description <description>] \ [--description <description>]
[--property <key=value> [...] ] \ [--no-property]
[--state <state>] \ [--property <key=value>]
<snapshot> [--state <state>]
<snapshot>
The arguments to be passed are: The arguments to be passed are:
@ -627,6 +628,11 @@ The arguments to be passed are:
``--description <description>`` ``--description <description>``
New snapshot description New snapshot description
``--no-property``
Remove all properties from <snapshot> (specify both
--no-property and --property to remove the current
properties before setting new properties.)
``--property <key=value>`` ``--property <key=value>``
Property to add or modify for this snapshot (repeat option to set Property to add or modify for this snapshot (repeat option to set
multiple properties) multiple properties)
@ -642,24 +648,30 @@ The arguments to be passed are:
.. code-block:: console .. code-block:: console
$ openstack snapshot set my-snapshot-id $ openstack volume snapshot set my-snapshot-id
Unmanage a snapshot Unmanage a snapshot
------------------- -------------------
Unmanage a snapshot with the :command:`cinder snapshot-unmanage` command: Unmanage a snapshot with the :command:`openstack volume snapshot unset`
command:
.. code-block:: console .. code-block:: console
$ cinder snapshot-unmanage SNAPSHOT $ openstack volume snapshot unset [-h]
[--property <key>]
<snapshot>
The arguments to be passed are: The arguments to be passed are:
SNAPSHOT ``--property <key>``
Name or ID of the snapshot to unmanage. Property to remove from snapshot (repeat option to remove multiple properties)
``<snapshot>``
Snapshot to modify (name or ID).
The following example unmanages the ``my-snapshot-id`` image: The following example unmanages the ``my-snapshot-id`` image:
.. code-block:: console .. code-block:: console
$ cinder snapshot-unmanage my-snapshot-id $ openstack volume snapshot unset my-snapshot-id