Bug 536623 (RHQ-954)

Summary: RFE: GUI views better depicting agent and server connection topology
Product: [Other] RHQ Project Reporter: John Mazzitelli <mazz>
Component: Core UI, High AvailabilityAssignee: Nobody <nobody>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: jshaughn, mazz
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: All   
URL: http://jira.rhq-project.org/browse/RHQ-954
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
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: 536626    
Bug Blocks: 678340    

Description John Mazzitelli 2008-10-07 15:00:00 UTC
In trying to debug why some agents are connected to the servers I think they should be connected to, it would be nice to have an admin page that shows me those agents that are connected to other servers that are NOT their primaries.

In effect, I want to see how the cloud is different than the way we optimally want it to be.  This will show us which agents are connected to failover servers.

Comment 1 Red Hat Bugzilla 2009-11-10 21:20:21 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-954


Comment 2 Jay Shaughnessy 2014-05-15 21:43:57 UTC
More topology work is still relevant.

Comment 3 Jay Shaughnessy 2014-05-15 21:46:56 UTC
Copied from another, similar BZ that is being closed:

In HAAC List Servers view, you can click on a server and see which agents are connected to it.

It would be very helpful if there was some kind of marker next to an agents name if the server you are looking at is NOT the agent's primary server.  So, I can scan the list and see which agents are connected to this server as a backup.

This allows me to see what agents are connected to a server after a failover happened.

Comment 4 Jay Shaughnessy 2014-05-15 21:47:23 UTC
*** Bug 536626 has been marked as a duplicate of this bug. ***