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 protected]> 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 ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1800494 Title: Volume QoS Create Extra Specs description incorrect Status in OpenStack Dashboard (Horizon): Fix Released Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1800494/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
