frontier-squid, the OSG distribution of the Frontier Squid software. on on squid HTTP caching proxy software that is optimized for use with applications on the Worldwide LHC Computing Grid (WLCG). It has many advantages over regular squid for common grid applications, especially Frontier and CVMFS. The OSG distribution of frontier-squid is a straight rebuild of the upstream frontier-squid package for the convenience of OSG users.
osg-configureconfiguration tool (version 1.0.45 and later) warns users who have not added the proxy location to their CE configuration. In the future, a proxy will be required and osg-configure will fail if the proxy location is not set. upstream documentation Hardware considerations section to determine how to size your equipment.
# EPEL 5 (For RHEL 5, CentOS 5, and SL 5) [root@client ~]$ curl -O https://dl.fedoraproject.org/pub/epel/epel-release-latest-5.noarch.rpm [root@client ~]$ rpm -Uvh epel-release-latest-5.noarch.rpm # EPEL 6 (For RHEL 6, CentOS 6, and SL 6) [root@client ~]$ rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm # EPEL 7 (For RHEL 7, CentOS 7, and SL 7) [root@client ~]$ rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpmWARNING: if you have your own mirror or configuration of the EPEL repository, you MUST verify that the OSG repository has a better yum priority than EPEL (details). Otherwise, you will have strange dependency resolution (depsolving) issues.
Choose the correct package name based on your operating systemís major version:
Install the Yum priorities package:
[root@client ~]$ yum install PACKAGE
PACKAGE with the package name from the previous step.
/etc/yum.conf has the following line in the
[main] section (particularly when using ROCKS), thereby enabling Yum plugins, including the priorities one:
plugins=1NOTE: If you do not have a required key you can force the installation using
yum install --nogpgcheck yum-priorities.
If you are upgrading from OSG 3.1 (or 3.2) to OSG 3.2 (or 3.3), remove the old OSG repository definition files and clean the Yum cache:
[root@client ~]$ yum clean all [root@client ~]$ rpm -e osg-release
This step ensures that local changes to
*.repo files will not block the installation of the new OSG repositories. After this step,
*.repo files that have been changed will exist in
/etc/yum.repos.d/ with the
*.rpmsave extension. After installing the new OSG repositories (the next step) you may want to apply any changes made in the
*.rpmsave files to the new
Install the OSG repositories using one of the following methods depending on your EL version:
For EL versions greater than EL5, install the files directly from
[root@client ~]$ rpm -Uvh URL
URL is one of the following:
For EL5, download the repo file and install it using the following:
[root@client ~]$ curl -O https://repo.grid.iu.edu/osg/3.2/osg-3.2-el5-release-latest.rpm [root@client ~]$ rpm -Uvh osg-3.2-el5-release-latest.rpm
[root@client ~]$ yum install frontier-squidThen enable it to start at boot time with this command:
[root@client ~]$ chkconfig frontier-squid on
Note: An important difference between the standard Squid software and the Frontier Squid variant is that Frontier Squid changes are in
/etc/squid/customize.sh instead of
enabledis set to
locationto the hostname and port of your Frontier Squid service (e.g.,
DEFAULTunless you have specific reasons to change them
osg-configure to propagate the changes on your CE
Note: You may want to finish other CE configuration tasks before running
osg-configure. Just be sure to run it once before starting CE services.
[root@client ~]$ service frontier-squid startStopping frontier-squid:
[root@client ~]$ service frontier-squid stop
[user@client ~]$ export http_proxy=http://yoursquid.your.domain:3128 [user@client ~]$ wget -qdO/dev/null http://frontier.cern.ch 2>&1|grep X-Cache X-Cache: MISS from yoursquid.your.domain [user@client ~]$ wget -qdO/dev/null http://frontier.cern.ch 2>&1|grep X-Cache X-Cache: HIT from yoursquid.your.domainIf the grep doesn't print anything, try removing it from the pipeline to see if errors are obvious. If the second try says MISS again, something is probably wrong with the squid cache writes. Look at the squid access.log file to try to see what's wrong. If your squid will be supporting the Frontier application, it is also good to do the test in the upstream documentation Testing the installation section. upstream documentation Log file contents section. Help Procedure.