Hi Zou,
I’m not quite sure
if I got your question right. I think you are asking how we are able to remotely
compile or debug applications running on the Grid, taking the border condition
of non-interactivity of batch systems into account, right?! Well, in fact we
are not sending jobs to a queue for compiling or debugging purposes but
directly work with the worker nodes themselves, i.e. we use gLogin to access
the worker nodes and/or computing
elements and to communicate with
them in order to be able to exchange
executables and/or debug
information.
But to be honest I am not
the expert on that. Nevertheless I am sure Thomas and
Christof (also on this mailing list) can
give you more details.
Best regards,
Mathias
Von:
geclipse-dev-bounces@xxxxxxxxxxx [mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im Auftrag von ???
Gesendet: Donnerstag, 27. März
2008 05:05
An: Developer
mailing list
Betreff: [geclipse-dev] Some
problem when implement interface on anothermiddleware
As I know, almost all jobs in Grid are managed
by batch systems such as PBS or LSF. These batch systems run the jobs in a
queue, always not instantiously and certainly without any
interactive I/O. While users use the Grid environment to debug their projects,
such as MPI projects, these properties are intolerable. So I am wondering how
gLite and g-Eclipse handle this problem. I have noticed that there is
such usage in the help document.
Best wishes,
Yuanbin Zou
FIT 1-111, Grid Computation Department, DSCT, Tsinghua University
Beijing, 100086
