Duncan Rand [mailto:[log in to unmask]] said:
> I thought each VO had their own SE:
>
> VO_ATLAS_DEFAULT_SE=gfe02.grid.hep.ph.ic.ac.uk
>
> is this not in the BDII?
As the politicians say, I'm glad you asked me that ... the main purpose of that is to set an environment variable on the WN. In the BDII there's a single default SE per CE, but there is also the same variable in the VOView object which allows it to be different for each VO - however I'm not sure if the YAIM variable is used to set that, probably you can tell more easily than me.
In any case, looking at the source code of lcg-info I think it only reads from the global CE attribute so you'd need a direct ldap query to get the VO-specific one.
Looking specifically at RAL, which I suspect is the only UK site with VO-specific SEs, the CREAM CEs do publish correct-looking values in the VOView - but I guess that may be configued with quattor. And in the ARC CEs the VOView default SE just says "0" ...
ldapsearch -x -h lcg-bdii.cern.ch -p 2170 -b o=grid '(&(objectclass=GlueVOView)(GlueCEAccessControlBaseRule=VO:atlas)(GlueChunkKey=GlueCEUniqueID=*gridpp.rl.ac.uk*))' | grep DefaultSE:
GlueCEInfoDefaultSE: srm-atlas.gridpp.rl.ac.uk
GlueCEInfoDefaultSE: srm-atlas.gridpp.rl.ac.uk
GlueCEInfoDefaultSE: srm-atlas.gridpp.rl.ac.uk
GlueCEInfoDefaultSE: srm-atlas.gridpp.rl.ac.uk
GlueCEInfoDefaultSE: 0
GlueCEInfoDefaultSE: 0
GlueCEInfoDefaultSE: 0
Stephen
--
Scanned by iCritical.
|