On Mon, 10 May 2004, Ian Stokes-Rees wrote:
> I think this crosses the boundary between two meanings of the word
> "issues". In terms of issues=problems, I don't have any with software
> installation. In terms of issue=comment, it is tied in to the idea that
> I am wondering "Wouldn't it just be easier to have everyone use gsi-ssh?".
If you're suggesting that someone would have to install the software by
hand on each site, I don't at all see that as being easier than having a
standard installation/certification job which can be fired off to every
site in the system. If you really *want* to do it by hand you can, but
what support do you want for it from LCG?
> Again, this is a matter of the amount of extra work it takes to set-up
> these per-VO pieces,
As I say, none of those things needs to be VO specific, you can do
everything with the standard LCG UI/RB/BDII if you want.
> compared to just providing a web-page with a list
> of VO-aware (e.g. LHCb aware) sites and then just gsi-sshing to them to
> use whatever local batch system they provide. I know tracking jobs
> across sites is terrible, and one which the RB, UI, and "grid" paradigm
> are meant to resolve, however in practice the difficulty of tracking LCG
> jobs at the moment makes this option appear perhaps not so aweful.
What difficulty? You seem to be talking about re-engineering the structure
of the middleware in a big way, but that's a matter for the EGEE JRA1
development, you aren't going to get major changes in the LCG-2 service.
In any case, we currently have about 35 sites in the system and we'll
probably be up to 50 before long, so you need some kind of automated
system to deal with it.
> I would love to install the LCG UI software on my desktop machine. I
> didn't realise this was now possible. Do you know where I can get
> details regarding it? My earlier attempts to do this were time
> consuming and unsuccessful.
Have a look at the last link on this page:
http://grid-deployment.web.cern.ch/grid-deployment/cgi-bin/index.cgi?var=documentation
although I can't comment on how easily it works in practice.
> > You can submit jobs through globus-job-submit, but what would be the
> > advantage?
>
> Avoiding per-VO configuration and an entire layer of software, I suppose.
But the per-VO configuration is only for things the VOs ask for, if
you have self-contained jobs then submitting to the RB is no different
to submitting directly except that it can find a place to run the job
for you.
Stephen
|