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

Bug 584035

Summary:	Low Latency Grid needs a home in Grid console (and a cmdline tool for monitoring)
Product:	Red Hat Enterprise MRG	Reporter:	William Henry <whenry>
Component:	condor-qmf	Assignee:	Matthew Farrellee <matt>
Status:	CLOSED WONTFIX	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	high	Docs Contact:
Priority:	medium
Version:	1.2	CC:	matt
Target Milestone:	2.2
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-04 20:51:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description William Henry 2010-04-20 15:09:45 UTC

Description of problem:


Currently the only way to get any sort 0f information about what is going on in a lo latency pool or sub-pool in Grid is to look a the message queues that have been defined.

It would be great of there was a tab in the console that provided some information.  The obvious is to provide an abstraction on the queue or queues that are been used and provide some statistics similar to the Messaging section. Some hook in with the reply queues might also be needed.

It would be good if each carod reported how many job submissions that they are handling - i.e. hoe many messages they have accepted.

A cmdline tool like the following would be useful and provide a condor-like interface:

condor_llq <executenodename> 

This would provide statistics on the low-lat execute including how many jobs accepted, any rejected. How many reply messages were sent. How many outpur files (?)


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: