Volume QoS Create Extra Specs description incorrect

[Simon Dodsley]

When creating a new extra-spec for a volume QoS the description states 3 acceptable values for keys.
This is incorrect as the values given (and the examples) are very specific for a Solidfire storage array using back-end QoS.

This is confusing when setting up QoS extra-specs as it implies the dashboard will only accept the listed back-end extra-specs.

Front-end QoS has, currently, 13 different acceptable keys, plus all the different supported back-end keys from vendors other than Solidfire.

The wording needs be changed to be more generic and if examples are given then they should cover the more generic front-end extra-specs than something that is specific to a single vendors implementation of volume QoS.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/618248

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/618248
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=e480773184e5b10d6fae2dc270999bb10a5affa5
Submitter: Zuul
Branch: master

commit e480773184e5b10d6fae2dc270999bb10a5affa5
Author: Simon Dodsley <email address hidden>
Date: Thu Nov 15 12:23:10 2018 -0500

    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

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/horizon 15.0.0.0b2 development milestone.