Right now, squid for CVMFS only seems to support (a set of) specific domains. I get that this is more deterministic, but it is also a pity, as it would be nice if it could support EESSI and the Compute Canada stack at the same time. Typically, what I have seen in the CVMFS tutorials is:
Of course this is very liberal, basically saying support all CVMFS repos...but is that so terrible?
Another problem with the current approach is that you are relying on the public Stratum 1's, but if CVMFS is configured to use a private Stratum1 it will not be cached by the squid. Even in the case of being more conservative, it would be good to allow the restriction based on cvmfs repo, not only on S1's.
One thing I would like to be able to do is to take the Desktop environment capabilities from the Alliance as we don't have support for this in EESSI right now.
Right now, squid for CVMFS only seems to support (a set of) specific domains. I get that this is more deterministic, but it is also a pity, as it would be nice if it could support EESSI and the Compute Canada stack at the same time. Typically, what I have seen in the CVMFS tutorials is:
Of course this is very liberal, basically saying support all CVMFS repos...but is that so terrible?
Another problem with the current approach is that you are relying on the public Stratum 1's, but if CVMFS is configured to use a private Stratum1 it will not be cached by the squid. Even in the case of being more conservative, it would be good to allow the restriction based on cvmfs repo, not only on S1's.