[geclipse-dev] 'using' gLite based middleware as a user

[Markus Knauer <mknauer@xxxxxxxxxxxxxx>]

I don't know your experience with a a Grid based on the gLite middleware, but 
I am once again frustrated. Did you ever try to send a job to the Grid that 
is more than /bin/hostname? Be honest!

Anyway. I am trying this from time to time, especially if I need a showcase 
for a presentation, or a tutorial like the EclipseCon tutorial. So I updated 
my scripts (maybe we should add another editor for bash/shell scripts?) and 
my application and tried to run it.
I had to re-run this application 7 (seven!) times until I had a successful job 
termination. In all other cases there were I/O problems, whatever 
problems, 'No compatible resources', many 'hit job shallow retry count', etc.

What about a functionality like 'watch my job and reschedule if Job terminated 
not successful'? That would be user friendly instead of waiting another 20 
minutes to get feedback from the job.

I don't know how people can run jobs that are long running or a bit more 
complicated than a 'Hello World' application. Is there a paper somewhere 
about wasted computing resources by aborted jobs? Or is there a hidden 
gimmick (hey, grid experts!) that helps during job execution?

Okay, if you need another example of an application running on gLite 
resources, I've grid-enable my EPP package build. It is located in 
egee-ce1.gup.uni-linz.ac.at.2811/markus/epp. 
There is a stupid run.sh script that does the work on the node, 
epp.linux.gtk.x86.tar.gz that contains the EPP build application, a few other 
important files that will be staged in, and two examplary JSDL files 
eppbuild_cpp.jsdl and eppbuild_java.jsdl. If you want to run them, please 
copy them and change their stage out locations.

Markus