Bug 1436403 - [RFE] - Extend search bar to allow searching on storage domain type
Summary: [RFE] - Extend search bar to allow searching on storage domain type
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.Core
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-27 20:53 UTC by Scott Dickerson
Modified: 2018-05-27 13:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-27 13:59:40 UTC
oVirt Team: Storage
Embargoed:
ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Scott Dickerson 2017-03-27 20:53:26 UTC
Currently, when on the main storage tab of the admin portal, there are a number of additional filters/search terms that may be applied.  No filter is available for "Domain Type".  For example, there is no way to setup the search bar such that only master storage domains are shown.

If a domain type filter is added, the dashboard can use it to filter the specific storage domain types displayed when a user clicks through from the Data Storage Domain inventory card.  Without the filter, users have gotten confused because the Data Storage Domain inventory card only shows data domains.  When they click through (by clicking on the card's title) they may see more storage domains then what is counted on the card.  Dashboard only counts Master and Data storage domains types in its queries.

See BZ1420448, especially 1420448#c6 for how this relates to ovirt-engine-dashboard.

Comment 1 Doron Fediuck 2018-05-27 13:59:40 UTC
Closing old RFEs. Most likely storage domain types will be unified in
the upcoming version(s).
If relevant, please re-open and explain why.
As always- patches are welcomed!


Note You need to log in before you can comment on or make changes to this bug.