Fix wording for Cinder Volume QoS Create Extra Specs

Update wording to make more generic and give additonal examples
for front-end keys and change current examples to be referenced
as back-end keys.

Change-Id: I248c4f7b55f84a6e4cb054124d988292db455cab
Closes-Bug: 1800494
This commit is contained in:
Simon Dodsley 2018-11-15 12:23:10 -05:00
parent 11fbb9dbd1
commit e480773184
1 changed files with 14 additions and 6 deletions

View File

@ -5,16 +5,24 @@
<h3>{% trans "Description:" %}</h3>
<p>{% blocktrans trimmed %}
Create a new "spec" key-value pair for QoS Spec "{{ qos_spec_name }}".
Valid key names are expected in the QoS specs. The acceptable values for key are
<tt>"minIOPS", "maxIOPS" and "burstIOPS"</tt>.
Valid key names are expected in the QoS specs. Refer to Cinder documentation
for the supported front-end and back-end keys.
{% endblocktrans %}
</p>
<p>
{% trans "Example:" %}
{% trans "Front-End Example:" %}
<ul>
<li>{% trans "Key: minIOPS and Value:20 (number value less than maxIOPS)" %}</li>
<li>{% trans "Key: maxIOPS and Value:5000 (number value bigger than minIOPS)" %}</li>
<li>{% trans "Key: burstIOPS and Value:5000 (number value bigger than minIOPS)" %}</li>
<li>{% trans "Key: total_iops_sec and Value: 5000" %}</li>
<li>{% trans "Key: total_bytes_sec_max and Value: 512000" %}</li>
<li>{% trans "Key: size_iops_sec and Value: 16" %}</li>
</ul>
</p>
<p>
{% trans "Back-End Example:" %}
<ul>
<li>{% trans "Key: minIOPS and Value: 20 (number value less than maxIOPS)" %}</li>
<li>{% trans "Key: maxIOPS and Value: 5000 (number value bigger than minIOPS)" %}</li>
<li>{% trans "Key: burstIOPS and Value: 5000 (number value bigger than minIOPS)" %}</li>
</ul>
</p>
{% endblock %}