From e480773184e5b10d6fae2dc270999bb10a5affa5 Mon Sep 17 00:00:00 2001 From: Simon Dodsley Date: Thu, 15 Nov 2018 12:23:10 -0500 Subject: [PATCH] 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 --- .../volume_types/qos_specs/_create.html | 20 +++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/openstack_dashboard/dashboards/admin/volume_types/templates/volume_types/qos_specs/_create.html b/openstack_dashboard/dashboards/admin/volume_types/templates/volume_types/qos_specs/_create.html index c229b50524..8522d05395 100644 --- a/openstack_dashboard/dashboards/admin/volume_types/templates/volume_types/qos_specs/_create.html +++ b/openstack_dashboard/dashboards/admin/volume_types/templates/volume_types/qos_specs/_create.html @@ -5,16 +5,24 @@

{% trans "Description:" %}

{% 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 - "minIOPS", "maxIOPS" and "burstIOPS". + Valid key names are expected in the QoS specs. Refer to Cinder documentation + for the supported front-end and back-end keys. {% endblocktrans %}

- {% trans "Example:" %} + {% trans "Front-End Example:" %}

+

+

+ {% trans "Back-End Example:" %} +

{% endblock %}