High Availability High Performance Web Cache - Revision history

Sertonix: use relative symlink

2023-11-17T10:31:11Z

use relative symlink

← Older revision		Revision as of 10:31, 17 November 2023
Line 71:		Line 71:
	* The AlpineLinux ucarp init script expects it is run on a multi-homed machine; with the ability to run ucarp processes on each interface. Copy the scripts for the interface:		* The AlpineLinux ucarp init script expects it is run on a multi-homed machine; with the ability to run ucarp processes on each interface. Copy the scripts for the interface:
	apk add ucarp		apk add ucarp
	ln -s ~~/etc/init.d/~~ucarp /etc/init.d/ucarp.eth0		ln -s ucarp /etc/init.d/ucarp.eth0
	cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth0		cp /etc/conf.d/ucarp /etc/conf.d/ucarp.eth0
	* edit the /etc/conf/ucarp.eth0 file:		* edit the /etc/conf/ucarp.eth0 file:

Sertonix: replace /etc/init.d with rc-service

2023-11-17T10:30:59Z

replace /etc/init.d with rc-service

← Older revision		Revision as of 10:30, 17 November 2023
Line 60:		Line 60:
	* ensure squid starts on boot		* ensure squid starts on boot
	rc_update add squid		rc_update add squid
	~~/etc/init.d/~~squid start		rc-service squid start


Line 96:		Line 96:
	* Start ucarp and save the changes		* Start ucarp and save the changes
	rc-update add ucarp.eth0		rc-update add ucarp.eth0
	~~/etc/init.d/~~ucarp.eth0 start		rc-service ucarp.eth0 start
	lbu commit		lbu commit
	* Follow the above steps for each of the Cache servers.		* Follow the above steps for each of the Cache servers.
Line 149:		Line 149:
	* ''On the cache that currently owns the 192.168.1.10 ucarp address''		* ''On the cache that currently owns the 192.168.1.10 ucarp address''

	~~/etc/init.d/~~haproxy start		rc-service haproxy start

	* Change your browser to use 192.168.1.10:8080 as the proxy address.		* Change your browser to use 192.168.1.10:8080 as the proxy address.
Line 173:		Line 173:
	ip addr add $2/24 dev $1		ip addr add $2/24 dev $1

	~~/etc/init.d/~~haproxy start		rc-service haproxy start

	for a in 330 440 550; do beep -f $a -l 100; done		for a in 330 440 550; do beep -f $a -l 100; done
Line 179:		Line 179:
	#!/bin/sh		#!/bin/sh

	~~/etc/init.d/~~haproxy stop		rc-service haproxy stop

	# Remove the VIP address		# Remove the VIP address

Dubiousjim: Category:Server

2012-03-24T16:09:33Z

Category:Server

← Older revision		Revision as of 16:09, 24 March 2012
Line 219:		Line 219:
	The "-sf" flag allows rolling maintenance of the web caches with no observable effect on the clients.		The "-sf" flag allows rolling maintenance of the web caches with no observable effect on the clients.

	[[Category:~~Networking~~]]		[[Category:Server]]

Dubiousjim: Category:Networking

2012-03-12T09:29:46Z

Category:Networking

← Older revision		Revision as of 09:29, 12 March 2012
Line 218:		Line 218:

	The "-sf" flag allows rolling maintenance of the web caches with no observable effect on the clients.		The "-sf" flag allows rolling maintenance of the web caches with no observable effect on the clients.

			[[Category:Networking]]

Jbilyk: added note that it's been tested on 2.2.3

2011-09-07T21:22:09Z

added note that it's been tested on 2.2.3

← Older revision		Revision as of 21:22, 7 September 2011
Line 1:		Line 1:
	== Introduction ==		== Introduction ==

	This document explains how to use [http://haproxy.1wt.eu/ HAProxy] and [http://www.ucarp.org/project/ucarp ucarp] to provide high performance and high-availability services.		This document explains how to use [http://haproxy.1wt.eu/ HAProxy] and [http://www.ucarp.org/project/ucarp ucarp] to provide high performance and high-availability services. This document has been tested using Alpine Linux 2.2.3.

	In this document we will use the [http://www.squid-cache.org/ Squid web cache] as the example service. Squid typically uses only a single processor, even on a multi-processor machine. To get increased web-caching performance, it is better to scale the web cache out across multiple (cheap) physical boxes. Although web caching is used as the example service, this document applies to other services, such as mail, web acceleration, etc.		In this document we will use the [http://www.squid-cache.org/ Squid web cache] as the example service. Squid typically uses only a single processor, even on a multi-processor machine. To get increased web-caching performance, it is better to scale the web cache out across multiple (cheap) physical boxes. Although web caching is used as the example service, this document applies to other services, such as mail, web acceleration, etc.

Jbilyk: update squid/haproxy ports to keep everything happy

2011-04-02T16:50:12Z

update squid/haproxy ports to keep everything happy

← Older revision		Revision as of 16:50, 2 April 2011
Line 41:		Line 41:
	icp_access allow all		icp_access allow all

	cache_peer 192.168.1.11 sibling ~~8080~~ 3130		cache_peer 192.168.1.11 sibling 3128 3130
	cache_peer 192.168.1.12 sibling ~~8080~~ 3130		cache_peer 192.168.1.12 sibling 3128 3130
	cache_peer 192.168.1.13 sibling ~~8080~~ 3130		cache_peer 192.168.1.13 sibling 3128 3130
	cache_peer 192.168.1.14 sibling ~~8080~~ 3130		cache_peer 192.168.1.14 sibling 3128 3130

	http_access allow localnet		http_access allow localnet
Line 50:		Line 50:
	http_access deny all		http_access deny all

	http_port ~~8080~~		http_port 3128

	forwarded_for off		forwarded_for off
Line 133:		Line 133:
	mode tcp		mode tcp
	balance roundrobin		balance roundrobin
	server cache1 192.168.1.11:~~8080~~ check		server cache1 192.168.1.11:3128 check
	server cache2 192.168.1.12:~~8080~~ check		server cache2 192.168.1.12:3128 check
	server cache3 192.168.1.13:~~8080~~ check		server cache3 192.168.1.13:3128 check
	server cache4 192.168.1.14:~~8080~~ check		server cache4 192.168.1.14:3128 check

	If your squid caches have public, routeable IP addresses, you may wish to change the balance algorithm to <code>source</code>. Some web applications get confused when a client's IP address changes between requests. Using <code>balance source</code> load balances clients across all web proxies, but once a client is assigned to a specific proxy, it continues to use that proxy.		If your squid caches have public, routeable IP addresses, you may wish to change the balance algorithm to <code>source</code>. Some web applications get confused when a client's IP address changes between requests. Using <code>balance source</code> load balances clients across all web proxies, but once a client is assigned to a specific proxy, it continues to use that proxy.
Line 205:		Line 205:
	* edit /etc/haproxy.conf and comment out the 192.168.1.11 line:		* edit /etc/haproxy.conf and comment out the 192.168.1.11 line:

	# server cache1 192.168.1.11:~~8080~~ check # 192.168		# server cache1 192.168.1.11:3128 check # 192.168

	* request a soft-restart of haproxy		* request a soft-restart of haproxy

Nangel: how to add/remove web caches without the clients noticing.

2011-03-01T17:32:30Z

how to add/remove web caches without the clients noticing.

@@ Line 1: / Line 1: @@
 == Introduction ==
@@ Line 191: / Line 188: @@
 * Save the changes
    lbu commit

Nangel: /* HA Proxy Load Balancer */ additional infor on balance roundrobin and balance source

2011-03-01T16:28:36Z

HA Proxy Load Balancer: additional infor on balance roundrobin and balance source

← Older revision		Revision as of 16:28, 1 March 2011
Line 141:		Line 141:
	server cache4 192.168.1.14:8080 check		server cache4 192.168.1.14:8080 check

			If your squid caches have public, routeable IP addresses, you may wish to change the balance algorithm to <code>source</code>. Some web applications get confused when a client's IP address changes between requests. Using <code>balance source</code> load balances clients across all web proxies, but once a client is assigned to a specific proxy, it continues to use that proxy.

	* make sure you have the haproxy user and group		* make sure you have the haproxy user and group
	adduser -s /bin/false -D -h /dev/null -H haproxy		adduser -s /bin/false -D -h /dev/null -H haproxy

Nangel: /* Initial Services */

2011-03-01T15:34:24Z

Initial Services

← Older revision		Revision as of 15:34, 1 March 2011
Line 59:		Line 59:
	{{warning\|This is a minimal configuration for demonstration purposes only. Likely you will need to configure more restrictive ACLs}}		{{warning\|This is a minimal configuration for demonstration purposes only. Likely you will need to configure more restrictive ACLs}}

	The `icp` and `cache_peer` entries allow all four squid server to share cached information. Once one server has retrieved an item, the others can get the information from the local server instead of reterieving it themselves.		The <code>icp</code> and <code>cache_peer</code> entries allow all four squid server to share cached information. Once one server has retrieved an item, the others can get the information from the local server instead of reterieving it themselves.

	* ensure squid starts on boot		* ensure squid starts on boot

Nangel: /* Initial Services */

2011-03-01T15:32:26Z

Initial Services

← Older revision		Revision as of 15:32, 1 March 2011
Line 48:		Line 48:
	cache_peer 192.168.1.13 sibling 8080 3130		cache_peer 192.168.1.13 sibling 8080 3130
	cache_peer 192.168.1.14 sibling 8080 3130		cache_peer 192.168.1.14 sibling 8080 3130

	http_access allow localnet		http_access allow localnet
	http_access allow localhost		http_access allow localhost
Line 58:		Line 58:

	{{warning\|This is a minimal configuration for demonstration purposes only. Likely you will need to configure more restrictive ACLs}}		{{warning\|This is a minimal configuration for demonstration purposes only. Likely you will need to configure more restrictive ACLs}}

			The `icp` and `cache_peer` entries allow all four squid server to share cached information. Once one server has retrieved an item, the others can get the information from the local server instead of reterieving it themselves.

	* ensure squid starts on boot		* ensure squid starts on boot
Line 65:		Line 67:

	At this point, you should be able to set your browser to use any of 192.168.1.1[1-4]:3129 as a proxy address, and get to the Internet. Because this config file does not use any optimizations, browsing will be ''slower'' than normal. This is to be expected. Any optimizations to the squid configuration you make to one server can be applied to all in the array. The purpose of this example is to show that the ''service'' is uniform across the array.		At this point, you should be able to set your browser to use any of 192.168.1.1[1-4]:3129 as a proxy address, and get to the Internet. Because this config file does not use any optimizations, browsing will be ''slower'' than normal. This is to be expected. Any optimizations to the squid configuration you make to one server can be applied to all in the array. The purpose of this example is to show that the ''service'' is uniform across the array.


	The `icp` and `cache_peer` entries allow all four squid server to share cached information. Once one server has retrieved an item, the others can get the information from the local server instead of reterieving it themselves.

	== Ucarp Virtual IP Manager ==		== Ucarp Virtual IP Manager ==