Difference: InstallSquidForLaunchpad (1 vs. 9)

Revision 92017-03-22 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallLaunchpad"

Installing Squid for a Frontier launchpad

Line: 32 to 32
  commentout("acl NET_LOCAL src") commentout("http_access allow NET_LOCAL") insertline("^http_access deny all", "http_access allow to_localhost")
Deleted:
<
<
setoption("quick_abort_min", "-1 KB")
  setoption("read_ahead_gap", "100 MB") setoption("shutdown_lifetime", "0 seconds")

Revision 82016-11-11 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallLaunchpad"

Installing Squid for a Frontier launchpad

Line: 18 to 18
  For installation, use the regular InstallSquid Installation instructions. Increase the file descriptors to 16384 as shown in the section on running out of file descriptors.
Changed:
<
<
If you have yum auto updates enabled, it's generally not a good idea to auto update the application service on a production system. Instead add exclude=frontier-* in /etc/yum.repos.d/cern-frontier.repo. Then when you want to really update it you can add the yum install option --ignoreexcludes=cern-frontier.
>
>
If you have yum auto updates enabled, it's generally not a good idea to autoupdate the application service on a production system. If you have autoupdates enabled it is recommended to avoid updating frontier packages. Some ways to handle this are:
  • Keep the frontier-* rpms in a local mirror repository instead
  • Set enabled=0 in /etc/yum.repos.d/cern-frontier.repo. Then to really upgrade, add the yum install option --enablerepo=cern-frontier.
  • Add exclude=frontier-* in /etc/yum.repos.d/cern-frontier.repo. Then when you want to really upgrade, add the yum install option --disableexcludes=cern-frontier.
 

Configuration

Revision 72016-11-10 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallLaunchpad"

Installing Squid for a Frontier launchpad

Line: 18 to 18
  For installation, use the regular InstallSquid Installation instructions. Increase the file descriptors to 16384 as shown in the section on running out of file descriptors.
Added:
>
>
If you have yum auto updates enabled, it's generally not a good idea to auto update the application service on a production system. Instead add exclude=frontier-* in /etc/yum.repos.d/cern-frontier.repo. Then when you want to really update it you can add the yum install option --ignoreexcludes=cern-frontier.
 

Configuration

In addition to the regular InstallSquid Configuration instructions, add these /etc/squid/customize.sh entries for launchpads:


Changed:
<
<
setoption("http_port", "8000 accel defaultsite=127.0.0.1:8080") insertline("^http_port", "cache_peer 127.0.0.1 parent 8080 0 no-query originserver")
>
>
setoption("http_port", "8000 accel defaultsite=127.0.0.1:8080 no-vhost") setoption("cache_peer", "127.0.0.1 parent 8080 0 no-query originserver")
  commentout("acl NET_LOCAL src") commentout("http_access allow NET_LOCAL") insertline("^http_access deny all", "http_access allow to_localhost")
Deleted:
<
<
setoption("ignore_ims_on_miss", "on")
  setoption("quick_abort_min", "-1 KB") setoption("read_ahead_gap", "100 MB") setoption("shutdown_lifetime", "0 seconds")
Changed:
<
<
Also set the default maximum squid per-log size in /etc/sysconfig/frontier-squid, for example this 5GB per log maximum for 60GB of disk space (there are 11 access.log files).
    export LARGE_ACCESS_LOG=5000000000
>
>
Also set the default maximum squid per-log size in /etc/sysconfig/frontier-squid as described on the InstallSquid page.
 

Testing

Revision 62016-06-22 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallLaunchpad"

Installing Squid for a Frontier launchpad

Line: 16 to 16
 

Installation

Changed:
<
<
For installation, use the regular InstallSquid Installation instructions.
>
>
For installation, use the regular InstallSquid Installation instructions. Increase the file descriptors to 16384 as shown in the section on running out of file descriptors.
 

Configuration

Revision 52016-02-24 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallLaunchpad"

Installing Squid for a Frontier launchpad

Line: 31 to 31
  setoption("quick_abort_min", "-1 KB") setoption("read_ahead_gap", "100 MB") setoption("shutdown_lifetime", "0 seconds")
Deleted:
<
<
setoption("positive_dns_ttl", "5 minutes")
 

Also set the default maximum squid per-log size in /etc/sysconfig/frontier-squid, for example this 5GB per log maximum for 60GB of disk space (there are 11 access.log files).

Revision 42014-11-18 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallLaunchpad"

Installing Squid for a Frontier launchpad

Line: 29 to 29
  insertline("^http_access deny all", "http_access allow to_localhost") setoption("ignore_ims_on_miss", "on") setoption("quick_abort_min", "-1 KB")
Changed:
<
<
setoption("read_ahead_gap", "1 GB")
>
>
setoption("read_ahead_gap", "100 MB")
  setoption("shutdown_lifetime", "0 seconds") setoption("positive_dns_ttl", "5 minutes")

Revision 32013-09-11 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallLaunchpad"

Installing Squid for a Frontier launchpad

Line: 6 to 6
 

Hardware

Changed:
<
<
The hardware requirements for squid on a launchpad tend to be much less than on a site proxy squid, because the bandwidth requested and the number of queries requested is usually much lower. That is because launchpads usually have far fewer clients: only other squids rather than worker node jobs.
>
>
The hardware requirements for squid on a launchpad tend to be much less than on a site proxy squid, because the bandwidth requested and the number of queries requested is usually much lower. That is because launchpads usually have far fewer clients: only other squids rather than worker node jobs. The recommended disk space for launchpads are at least 100GB for squid cache and 60GB for squid logs.
 

Software

Line: 34 to 34
  setoption("positive_dns_ttl", "5 minutes")
Added:
>
>
Also set the default maximum squid per-log size in /etc/sysconfig/frontier-squid, for example this 5GB per log maximum for 60GB of disk space (there are 11 access.log files).
    export LARGE_ACCESS_LOG=5000000000
 

Testing

Use the regular InstallSquid Testing instructions, except don't set http_proxy, replace cmsfrontier.cern.ch with the name of your server, and replace FrontierProd with the name of your servlet.

Revision 22012-11-14 - DaveDykstra

Line: 1 to 1
 
META TOPICPARENT name="InstallLaunchpad"
Deleted:
<
<
THIS PAGE IS UNDER CONSTRUCTION
 

Installing Squid for a Frontier launchpad

Changed:
<
<
Talk about reduced hardware requirements
>
>
Every Frontier launchpad machine runs frontier-squid in addition to a frontier-tomcat. This squid is configured in what as known as a "reverse proxy" which automatically forwards all connections to the backend server process.

Hardware

The hardware requirements for squid on a launchpad tend to be much less than on a site proxy squid, because the bandwidth requested and the number of queries requested is usually much lower. That is because launchpads usually have far fewer clients: only other squids rather than worker node jobs.

Software

Preparation

It is best if you set the user and group id for squid to be the same as that used for tomcat as described in the InstallSquid Preparation section.

Installation

For installation, use the regular InstallSquid Installation instructions.

Configuration

In addition to the regular InstallSquid Configuration instructions, add these /etc/squid/customize.sh entries for launchpads:

    setoption("http_port", "8000 accel defaultsite=127.0.0.1:8080")
    insertline("^http_port", "cache_peer 127.0.0.1 parent 8080 0 no-query originserver")
    commentout("acl NET_LOCAL src")
    commentout("http_access allow NET_LOCAL")
    insertline("^http_access deny all", "http_access allow to_localhost")
    setoption("ignore_ims_on_miss", "on")
    setoption("quick_abort_min", "-1 KB")
    setoption("read_ahead_gap", "1 GB")
    setoption("shutdown_lifetime", "0 seconds")
    setoption("positive_dns_ttl", "5 minutes")

Testing

 
Changed:
<
<
Recommend setting the user & group id the same as what was used for frontier-tomcat
>
>
Use the regular InstallSquid Testing instructions, except don't set http_proxy, replace cmsfrontier.cern.ch with the name of your server, and replace FrontierProd with the name of your servlet.
 
Deleted:
<
<
Recommended customize.sh entries for launchpads
 \ No newline at end of file
Added:
>
>
Responsible: DaveDykstra

Revision 12012-11-02 - DaveDykstra

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="InstallLaunchpad"
THIS PAGE IS UNDER CONSTRUCTION

Installing Squid for a Frontier launchpad

Talk about reduced hardware requirements

Recommend setting the user & group id the same as what was used for frontier-tomcat

Recommended customize.sh entries for launchpads

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback