Bug 1418053 - [RFE] Add dynamic grouping functionality to Insights Web UI
Summary: [RFE] Add dynamic grouping functionality to Insights Web UI
Alias: None
Product: Cloud Software Services (cloud.redhat.com)
Classification: Red Hat
Component: General
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Kathryn Dixon
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-31 17:41 UTC by Matt Ruzicka
Modified: 2021-04-11 05:44 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Matt Ruzicka 2017-01-31 17:41:57 UTC
1. Who is the customer behind the request? 

   Not a specific customer request, but considered as part of a current eval. Details added to private comment in case this becomes public.  No case currently.
2. What is the nature and description of the request?  

   Add dynamic/automatic grouping functionality so Insights Web UI could auto-populated a set of pre-created/default system groups based on system inventory.  Dynamic groupings might be by domain, sub-domain, partial hostname match, etc. Allow customer to create their own dynamic rules for auto-inclusion of new systems.  (more below)

3. Why does the customer need this?

   Would make it easier to interact with large number of systems and reduce the up front effort needed by the customer in some cases.  Would also allow auto-population of new systems into existing groups to further reduce administrative overhead.
4. How would the customer like to achieve this? (List the functional requirements here)  


   Some easy groups could be domain (custdom1.tld vs custdom2.tld) and subdomain (*.rdu.custdom1.tld vs *.atl.custdom1.tld). Potentially a group for each third level domain regardless of primary domain as well (*.rdu.* vs *.atl.*). Would expect this to be an easy regex match on something like /^*\.([^\.]+\.[^\.]+)$/ or /^*\.(([^\.]+)\.[^\.]+\.[^\.]+)$/.

   More complicated, but potentially more valuable, groupings could be based on algorithmic comparison of all hostnames, so all mail*.domain.tld, *rhev*.domain.tld, *rhev*, ^xyz*, etc would have groups. I would think it would be possible to do a comparison of all 3+ strings that occur in a similar locations in more than 2 or 3 hostnames.

   Bonus if customers could create their own dynamic rules using reqex.  This way if they set up something like /^zy\w{1,2}-10\d\d\d\.domain\.tld/ named "zy*10* servers" group they could get whatever whacky stuff they might want.


   Would be best if this was a feature that could be enabled or disabled as preferred (on by default), and better yet if the group list dialog provided the ability to enable/disable individual groups - as well as maybe clone and modify existing groups. 

This might require the group administration view where they would see a checkbox list of groups showing if they are enabled or disabled (grayed out?), broken down by or labeled as dynamic vs custom. Here they could mass enable/disable/delete, and ideally be able to click a button to clone and modify. If they clicked the actual group (or the clone and modify) it would take them to a dialog to modify the existing group (name, systems, enable/disable, etc) and verify which systems are part of it. This would allow them to more easily see all groups in the admin view as currently it's a little noisy with everything seeming to be auto-expanded.

Then ideally the normal inventory view would only show the 'active" groups as it does now so they can view or take cation as needed.

Super bonus would be multi-tenency/configurable privs on each of these groups so Team A could see their servers, but not see Team B's servers.
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  
   Install against the Employee account to see what comes up initially.   Test creating dynamic rules and adding new systems.

6. Is there already an existing RFE upstream or in Red Hat Bugzilla?  

   Did not see one.

7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  

8. Is the sales team involved in this request and do they have any additional input?  
   Not at this time.

9. List any affected packages or components.  
10. Would the customer be able to assist in testing this functionality if implemented? 

   Likely yes.

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