openstack/openstack-manuals
Code Issues Proposed changes

Merge "[config-ref] Minor changes to HPE 3PAR drivers RST"

Browse Source
This commit is contained in:
Jenkins 2015-12-10 11:59:15 +00:00 committed by Gerrit Code Review
commit ca5121dedd
1 changed files with 22 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

50
doc/config-ref-rst/source/block-storage/drivers/hpe-3par-driver.rst
View File

@ -82,14 +82,6 @@ following capabilities in the OpenStack Block Storage API
``cinder.api.contrib.types_extra_specs`` volume type extra specs extension ``cinder.api.contrib.types_extra_specs`` volume type extra specs extension
module: 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:snap_cpg``
* ``hpe3par:provisioning`` * ``hpe3par:provisioning``
@ -170,40 +162,42 @@ pairs and associate them with a volume type, run the following commands:
$ cinder help qos-create $ cinder help qos-create
.. code-block:: console
$ cinder help qos-key $ cinder help qos-key
.. code-block:: console
$ cinder help qos-associate $ cinder help qos-associate
The following keys require that the HPE 3PAR StoreServ storage array has a The following keys require that the HPE 3PAR StoreServ storage array has a
Priority Optimization license installed. Priority Optimization license installed.
* ``hpe3par:vvs`` - The virtual volume set name that has been predefined by ``hpe3par:vvs``
the Administrator with Quality of Service (QoS) rules associated to it. If The virtual volume set name that has been predefined by the Administrator
you specify extra_specs ``hpe3par:vvs``, the qos_specs ``minIOPS``, with Quality of Service (QoS) rules associated to it. If you specify
``maxIOPS``, ``minBWS``, and ``maxBWS`` settings are ignored. 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, ``minBWS``
the I/O issue bandwidth rate has no minimum goal. 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 ``maxBWS``
I/O issue bandwidth rate has no limit. 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 ``minIOPS``
issue count has no minimum goal. 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 ``maxIOPS``
count rate has no limit. 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 ``priority``
set, the priority is ``normal``, valid values are ``low``, ``normal`` and The priority of the QoS rule over other rules. If not set, the priority is
``high``. ``normal``, valid values are ``low``, ``normal`` and ``high``.
.. note:: .. note::