LHC Computer Grid - Rollout
> [mailto:[log in to unmask]] On Behalf Of Jeff Templon
said:
> the job needs to see the exact same list of grid clients
> everywhere. or
> at least (in the rosy future) the APIs with which the progr has been
> linked must work everywhere.
>
> Also there needs to be some basic set of things available. Python &
> Perl + the standard suite of unix v7 / SysV / whatever tools
> should be there.
>
> However there is an awful long way between this and "identical
> environments". And if we expect identical environments it
> will all fail too.
Obviously the actual environments may vary a lot, the point I was trying
to make is that the whole purpose of the grid middleware is that it
should sit on top of all that variation and present a uniform interface
to the applications (much as an OS means you don't have to worry about
which CPU or disk controller you have). What worried me about the way
this thread was going was that it seemed that some admins want to be
able to pick and choose what middleware to install, or indeed
potentially not install any of it.
From this, and other discussions in the UK deployment mailing list, I
somewhat wonder how many admins understand what EGEE is supposed to be
trying to achieve. In some cases I suspect that people are just being
told "you have to install all this stuff" without any guidance as to
what (as this thread started off) any of it is *for*, or what the
broader goals of the project are supposed to be. Part of the reason I
responded the way I did to the initial mail was that to me it is pretty
obvious what, say, edg-mkgridmap or voms-client_gcc3_2_2 or
edg-replica-metadata-catalog-client are, but maybe that kind of
knowledge needs to be transmitted more effectively to people new to the
project?
Similarly, in the UK we still haven't persuaded any site to support
biomed or any non-HEP VO, and even e.g. dzero is only supported at the
two RAL sites. Most sites still seem to think in terms of running jobs
for "their" experiments, and indeed sometimes "their" users, which is
not how grids are supposed to work.
Stephen
PS If you want to see which sites support which VOs, here's a fun thing
I came up with (this is all one line) - change the *.ac.uk* bits to look
at different groups of sites ...
for VO in `ldapsearch -x -h lcgbdii02.gridpp.rl.ac.uk -p 2170 -b o=grid
"(&(objectclass=GlueCE)(GlueCEUniqueID=*.ac.uk*))" | grep
GlueCEAccessControlBaseRule | cut -d: -f3 | sort | uniq`; do echo; echo
$VO:; echo; ldapsearch -x -h lcgbdii02.gridpp.rl.ac.uk -p 2170 -b o=grid
"(&(objectclass=GlueCE)(GlueCEUniqueID=*.ac.uk*)(GlueCEAccessControlBase
Rule=VO:$VO))" GlueCEInfoHostName | grep GlueCEInfoHostName: | sort |
uniq | cut -d: -f2; done
|