From e1943b01e1739360484bef45a7e444b9b72959d6 Mon Sep 17 00:00:00 2001 From: qiaomin Date: Thu, 8 Dec 2016 12:01:23 +0000 Subject: [PATCH] Use 'openstack' command-client commands to replace cinder commands Change-Id: I77a3fa68de50f78553c191ce8c5b3a64113398fb Implements: blueprint use-openstack-command --- .../source/blockstorage-multi-backend.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/doc/admin-guide/source/blockstorage-multi-backend.rst b/doc/admin-guide/source/blockstorage-multi-backend.rst index 8be0a11607..7740cd0819 100644 --- a/doc/admin-guide/source/blockstorage-multi-backend.rst +++ b/doc/admin-guide/source/blockstorage-multi-backend.rst @@ -124,15 +124,15 @@ This can be done by the following command: .. code-block:: console - $ cinder --os-username admin --os-tenant-name admin type-create lvm + $ openstack --os-username admin --os-tenant-name admin volume type create lvm Then, an extra-specification has to be created to link the volume type to a back end name. Run this command: .. code-block:: console - $ cinder --os-username admin --os-tenant-name admin type-key lvm set \ - volume_backend_name=LVM_iSCSI + $ openstack --os-username admin --os-tenant-name admin volume type set lvm \ + --property volume_backend_name=LVM_iSCSI This example creates a ``lvm`` volume type with ``volume_backend_name=LVM_iSCSI`` as extra-specifications. @@ -141,10 +141,10 @@ Create another volume type: .. code-block:: console - $ cinder --os-username admin --os-tenant-name admin type-create lvm_gold + $ openstack --os-username admin --os-tenant-name admin volume type create lvm_gold - $ cinder --os-username admin --os-tenant-name admin type-key lvm_gold set \ - volume_backend_name=LVM_iSCSI_b + $ openstack --os-username admin --os-tenant-name admin volume type set lvm_gold \ + --property volume_backend_name=LVM_iSCSI_b This second volume type is named ``lvm_gold`` and has ``LVM_iSCSI_b`` as back end name. @@ -173,13 +173,13 @@ back end has to be used. .. code-block:: console - $ cinder create --volume_type lvm --display_name test_multi_backend 1 + $ openstack volume create --size 1 --type lvm test_multi_backend Considering the ``cinder.conf`` described previously, the scheduler creates this volume on ``lvmdriver-1`` or ``lvmdriver-2``. .. code-block:: console - $ cinder create --volume_type lvm_gold --display_name test_multi_backend 1 + $ openstack volume create --size 1 --type lvm_gold test_multi_backend This second volume is created on ``lvmdriver-3``.