From ec71da3ac2c4001d72e47b64ce1ebe1673d5eb1e Mon Sep 17 00:00:00 2001 From: njirap Date: Thu, 10 Dec 2015 14:20:10 +0300 Subject: [PATCH] [config-ref] Minor changes to HPE 3PAR drivers RST Change-Id: I89dc3d2ec74f4e5297c8ac8d183ae59ada0d5879 Implements: blueprint config-ref-rst --- .../block-storage/drivers/hpe-3par-driver.rst | 50 ++++++++----------- 1 file changed, 22 insertions(+), 28 deletions(-) diff --git a/doc/config-ref-rst/source/block-storage/drivers/hpe-3par-driver.rst b/doc/config-ref-rst/source/block-storage/drivers/hpe-3par-driver.rst index 14898b2a55..177bd5d35c 100644 --- a/doc/config-ref-rst/source/block-storage/drivers/hpe-3par-driver.rst +++ b/doc/config-ref-rst/source/block-storage/drivers/hpe-3par-driver.rst @@ -82,14 +82,6 @@ following capabilities in the OpenStack Block Storage API ``cinder.api.contrib.types_extra_specs`` volume type extra specs extension module: -* ``hpe3par:cpg`` - - .. warning:: - - This setting is ignored as of Kilo. Instead, use the ``hpe3par_cpg`` - setting in ``cinder.conf`` to list the valid CPGs for a backend. CPGs - should now be controlled by configuring separate backends with pools. - * ``hpe3par:snap_cpg`` * ``hpe3par:provisioning`` @@ -170,40 +162,42 @@ pairs and associate them with a volume type, run the following commands: $ cinder help qos-create -.. code-block:: console - $ cinder help qos-key -.. code-block:: console - $ cinder help qos-associate The following keys require that the HPE 3PAR StoreServ storage array has a Priority Optimization license installed. -* ``hpe3par:vvs`` - The virtual volume set name that has been predefined by - the Administrator with Quality of Service (QoS) rules associated to it. If - you specify extra_specs ``hpe3par:vvs``, the qos_specs ``minIOPS``, - ``maxIOPS``, ``minBWS``, and ``maxBWS`` settings are ignored. +``hpe3par:vvs`` + The virtual volume set name that has been predefined by the Administrator + with Quality of Service (QoS) rules associated to it. If you specify + extra_specs ``hpe3par:vvs``, the qos_specs ``minIOPS``, ``maxIOPS``, + ``minBWS``, and ``maxBWS`` settings are ignored. -* ``minBWS`` - The QoS I/O issue bandwidth minimum goal in MBs. If not set, - the I/O issue bandwidth rate has no minimum goal. +``minBWS`` + The QoS I/O issue bandwidth minimum goal in MBs. If not set, the I/O issue + bandwidth rate has no minimum goal. -* ``maxBWS`` - The QoS I/O issue bandwidth rate limit in MBs. If not set, the - I/O issue bandwidth rate has no limit. +``maxBWS`` + The QoS I/O issue bandwidth rate limit in MBs. If not set, the I/O issue + bandwidth rate has no limit. -* ``minIOPS`` - The QoS I/O issue count minimum goal. If not set, the I/O - issue count has no minimum goal. +``minIOPS`` + The QoS I/O issue count minimum goal. If not set, the I/O issue count has no + minimum goal. -* ``maxIOPS`` - The QoS I/O issue count rate limit. If not set, the I/O issue - count rate has no limit. +``maxIOPS`` + The QoS I/O issue count rate limit. If not set, the I/O issue count rate has + no limit. -* ``latency`` - The latency goal in milliseconds. +``latency`` + The latency goal in milliseconds. -* ``priority`` - The priority of the QoS rule over other rules. If not - set, the priority is ``normal``, valid values are ``low``, ``normal`` and - ``high``. +``priority`` + The priority of the QoS rule over other rules. If not set, the priority is + ``normal``, valid values are ``low``, ``normal`` and ``high``. .. note::