Skip to content

Commit

Permalink
add documentation on limiting squid access to certain stratum 1s
Browse files Browse the repository at this point in the history
  • Loading branch information
jblomer committed Nov 30, 2023
1 parent 78db71e commit fed1619
Showing 1 changed file with 11 additions and 3 deletions.
14 changes: 11 additions & 3 deletions cpt-squid.rst
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
Setting up a Local Squid Proxy
==============================

For clusters of nodes with CernVM-FS clients, we strongly recommend
For clusters of nodes with CernVM-FS clients, we strongly recommend
setting up two or more `Squid forward proxy <http://www.squid-
cache.org>`_ servers as well. The forward proxies will reduce the
latency for the local worker nodes, which is critical for cold cache
Expand Down Expand Up @@ -60,11 +60,19 @@ something like this:

acl localnet src A.B.C.D/NN

If you instead want to limit the destinations to major cvmfs Stratum 1s,
it is better to use the list built in to
If you instead want to limit the destinations to major WLCG cvmfs Stratum 1s,
it is best to use the list built in to
`Frontier Squid <https://twiki.cern.ch/twiki/bin/view/Frontier/InstallSquid#Restricting_the_destination>`_
because the list is sometimes updated with new releases.

For manually limiting the destinations, use a configuration like

::

acl cvmfs dst <a stratum 1 host name>
acl cvmfs dst <another stratum 1 host name>
http_access allow cvmfs

The Squid configuration can be verified by ``squid -k parse``. Before
the first service start, the cache space on the hard disk needs to be
prepared by ``squid -z``. In order to make enough file descriptors
Expand Down

0 comments on commit fed1619

Please sign in to comment.