[Bioperl-pipeline] web, restart

[Elia Stupka]

> By monitoring, I mean we do not need to look at the process calls like 
> you mentioned below cuz we rely on the job scheduler LSF in this case. 
> Thus we only need to provide the information in the pipeline job table 
> like juguang said.

However, we want to overcome the limitations of a standalone system by 
implementing a thin client that can run on each node if we do want to 
look at what is happening on that particular node, or read the file,etc.

> We may want to be smart about the monitoring, and put in some 
> heuristics to have the pipeline stop if all jobs that sent  to the 
> node come back failed very quickly which may signal that something is 
> not setup properly that has escaped the initial setup checks.

Absolutely. I'd like (if we get into this again) to make sure we go 
further than simple monitoring, and start putting smars into the 
software.

> sitting behind a firewall so we need some daemon... More fanciful 
> would be an applet...

We most definitely need a  server/client structure, which will enable 
us to do tons of things in the future, so let's decided it upfront.

> This work was started by Kiran and Yujin but it never took off.

Yujin is coming to work with us from mid-July for a couple of months, 
he could help

Elia

---
Bioinformatics Program Manager
Temasek Life Sciences Laboratory
1, Research Link
Singapore 117604
Tel. +65 6874 4945
Fax. +65 6872 7007