[ptp-dev] PTP enhancements to support LoadLeveler

[Dave Wootton <dwootton@xxxxxxxxxx>]

We have some success now with seeing job and node status from LoadLeveler 
in the PTP views. There are some enhancements we think would be useful to 
LoadLeveler and other resource managers as well as some questions

Suggestions

1) LoadLeveler has a number of statuses for a job and node beyond the 
simple running and exited that I am using for PE. We originally talked 
about adding additional icons or different colored icons to represent 
those statuses, but we think there are too many for this to be a good 
idea. We're thinking that if the job and machine view could be enhanced to 
allow flyover/tooltip help for each icon in the view. That text could be 
used to display additional status. We are also thinking this status would 
be sent from the proxy as an additional, optional, attribute to node and 
job change events. Each time job or node status changed we would send 
across a new event. The tooltip text would present whatever thye last 
additional status for that node or job was. It might make sense to extend 
this to machine and task objects as well, but we don't have a need for 
these to support LoadLeveler.
2) LoadLeveler can provide additional, detailed information on a submitted 
job, such as resources allocated to a job, reason why a job is not 
running, etc that we think would be useful to the user. Our thinking here 
is that the user could right click on an entry in the job view and get a 
popup menu witt 'detailed status' as one choice. Selecting that results in 
a command to the proxy requesting status. The proxy sends back an event 
with the detailed status. The GUI proceses that event and opens a popup, 
scrollable, window displaying that status (or maybe put this info in a new 
PTP view)
3) It looks like the job view uses task indices starting at 0. LoadLeveler 
identifies the application tasks in a parallel application using their 
task rank 0..n-1 and uses -1 for the master (poe) process of the 
application as well as -1 for the sole task of a serial application. Is it 
possible to modify the definition of task index to allow -1 (and maybe an 
arbitary lower linit)

Questions
1) Is the PID attribute to a process mandatory? This information is not 
provided to us by LoadLeveler, so we would like to omit it, or use '-1' as 
the pid if none is provided. We could also live with a requirement that we 
send pid 0, but that woulod be a bit inconsistent with task index where we 
have -1 as a task index.

I also have a couple bugs which I will log in bugzilla when I get a chance

Dave