Frontier Squid Cache server installation details

The BNL Frontier Squid Cache installation server is based on the notes of Sergey's and Lee's notes located here. This information is well explained and is a good guide to perform the installation of frontier Squid.

This installation was performed in the same machine where the BNL frontier resides and is sharing the machine with more applications. Also this installation requires a user dbfrontier for this test. I used my account but will be changed to a local account in the new machine i.e.

dbfrontiersquid@xxx.xxx 

FRONTIER_USER=cgamboa
FRONTIER_GROUP=usatlas

BNL Squid cache server was installed on:

[cgamboa@gridui01 frontier-cache]$ pwd
/data/frontier/frontier-cache 

this directory holds the working directory and the cache (var) directory.

/data/frontier/frontier-cache/squid/var/cache

The Fermilab script allows you to specify the not only the installation prefix previously shown but the network/netmask which would allowed to access the squid.

For this testing exercise is define for

FRONTIER_NET_LOCAL='130.199.0.0/255.255.0.0'

The amount of cache memory defined was 512MB and the amount of 65000MB

The server is controlled manually trough the following commands

The command to start the server is:

/data/frontier/frontier-cache/utils/bin/fn-local-squid.sh start

and the command to stop the server is:

/data/frontier/frontier-cache/utils/bin/fn-local-squid.sh start

A cron job can be used to rotate and prevent that the log files consume a lot of disk space Thus:

5 7 * * * /data/frontier/frontier-cache/utils/cron/daily.sh 2>&1 >/dev/null

Customizing the Squid cache server to BNL needs

The installation previously done is performed initially with the squid.conf file that came with the squid installation package previously designed at Fermilab. This configuration file would have to be change according the BNL requirements in terms of data load and network speed and access control list.