> > And the CVMFS area for each project is standalone with no possibility of
> interference. The drawback is that one needs separate DNs (or roles
> memberships) in order to access/maintain multiple repositories.
> For LSST in particular since we are already working on establishing the VO I'd
> rather not add this extra degree of freedom.
>
> For smaller subgroups it may make sense although it means that each needs
> to be added to the WNs.
But the 'public_for_everyone' feature of CVMFS could be used here by the small subgroups. It's true the VO_SW_DIR variable would make no sense, but /cvmfs/lsst.gridpp.ac.uk would be perfect accessible by a 'northgrid' VO member working for the 'lsst' project. And 'northgrid' is already supported by the (most) of UK grid sites.
Catalin
|