yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #75512
[Bug 1800494] [NEW] Volume QoS Create Extra Specs description incorrect
Public bug reported:
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.
** Affects: horizon
Importance: Undecided
Status: New
--
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):
New
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
Follow ups