On 27/02/2015 14:15, Catalin Condurache wrote:
>>> 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.
northgrid is not supported by most UK sites it is supported by the
Northgrid sites (Lancaster, Liverpool, Manchester, Sheffield). We have
added/are adding the CVMFS configuration temporarily to Edinburgh nodes
as a stop gap so we an use the LSST VO there while we get proper CVMFS
for LSST enabled. That still took me collecting the configuration files
from Manchester, Andy adapting them and testing them on a WN and finally
their cluster manager rolling it out.
The reason I think it may be a good idea is that there is no risk of
interference and the VO manager doesn't have to install all the small
subgroups software.
cheers
alessandra
> Catalin
--
Respect is a rational process.
|