Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 978804

Summary: [Docs] [Dev] Events main tab / sub-tabs Must Support the UI Plug-in Model
Product: Red Hat Enterprise Virtualization Manager Reporter: Andrew Burden <aburden>
Component: DocumentationAssignee: Zac Dover <zdover>
Status: CLOSED NOTABUG QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: acathrow, bazulay, ecohen, gklein, sgordon, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.3.0   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 975673 Environment:
Last Closed: 2014-07-22 19:54:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 953989, 975673    
Bug Blocks: 894399    

Description Andrew Burden 2013-06-27 07:33:27 UTC
+++ This bug was initially created as a clone of Bug #975673 +++

+++ This bug was initially created as a clone of Bug #953989 +++

1. Proposed title of this feature request
Event Viewer Must Support UI Plug-in Model

2. Who is the customer behind the request?
Red Hat 

3. What is the nature and description of the request?
All of the other TABs in the Webadmin console support the new UI plug-in model; however, the event viewer does not.  We need the event viewer to be plug-able so that we can diagnose the faults therein.

4. Why does the customer need this? (List the business requirements here)
Diagnostic services.

5. How would the customer like to achieve this? (List the functional requirements here)
Ensure that the admin console's event viewer is compliant with the existing plug-in model.

6. List any affected packages or components.
The Red Hat Support Plug-in for RHEV is adversely affected by the fact that the event viewer is not plug-able.

7. Would the customer be able to assist in testing this functionality if implemented?
Yes.

--- Additional comment from  on 2013-05-09 12:21:41 EDT ---

I assume this is about adding custom context-sensitive buttons/menu-items to existing Event-related tab(s).

Currently, we have addMainTabActionButton API function for main tabs. Currently, this API function doesn't support "Events" main tab, this RFE is intended to add support for this main tab:

api.addMainTabActionButton('Event', 'Button/menu-item label', {
    ...
    onClick: function() { ... },
    isEnabled: function() { ... },
    ...
});

Keith, do we also need to support adding custom context-sensitive buttons/menu-items to existing Event-related *sub* tabs? If the answer is yes, we'll have to introduce new API function for this purpose:

// Add action button to Cluster Event sub-tab
api.addSubTabActionButton('Cluster', 'Event', 'Button/menu-item label', { ... });

--- Additional comment from Spenser Shumaker on 2013-05-13 13:40:06 EDT ---

We would like to be able to add Action buttons in both main-tabs and sub-tabs.  Anywhere the user can access events, there will be value added by being able to "Diagnose" the event using our services.

--- Additional comment from  on 2013-05-15 11:53:55 EDT ---

Thanks Spenser, so we will need to improve existing addMainTabActionButton API + add new addSubTabActionButton API. Both API functions should support all table-based main/sub tabs.

--- Additional comment from  on 2013-06-17 13:07:15 EDT ---

A plugin that verifies addSubTab, addMainTabActionButton and addSubTabActionButton API functions.

Comment 1 Zac Dover 2014-07-22 19:54:39 UTC
This is an engineering bug cloned as a docs bug, clearly raised out of the better-to-have-it-and-not-need-it-than-need-it-and-not-have-it school of documentation bug cultivation. Fortunately, we don't need it. Consequently, it's been sitting untended for a long time. I will close it NOTABUG.