Gonzalo Merino wrote:
> What I do not understand is why for castorsrm.pic.es the lcg-cr was not
> working, if we were publishing the same SARoot=dteam:dteam and
> CESEBindAccessPoint=/castor/pic.es/grid.
>
> Anyhow, following Maarten advice, after changing the SARoot into
> dteam:/castor/pic.es/grid, now it works, but I was trying to understand
> what is different between a classic SE and an SRM in the format in which
> these attributes must be published... anybody knows?
An SRM SE is self-sufficient: it publishes everything needed to access files.
A Classic SE, i.e. a dumb gridftp server, may be NFS-mounted on a close CE
for the "file" protocol, in which case the local mount point, i.e. access path,
is decided by the CE, so at least that has to be published by the CE.
Then the SARoot just names the subdirectory for the VO.
In principle this could have been done better, with a small schema change,
allowing the SE to be self-sufficient at least for the "gsiftp" protocol.
Note: LCG-2 no longer supports the "file" protocol, but the information system
usage was not adapted. Now we have better ways in GLUE 1.2, but the Classic SE
should go away soon... ;-)
|