Re: [squid-users] Managing clusters of siblings (squid2.7)

On 28.09.09 15:04, Chris Hostetter wrote:
> My company currently runs several "clusters" of application servers
> behind load balancers, which are each in turn sitting behind a "cluster"
> of squid machines configured as accelerators. each squid cluster is then
> sitting behind a load balancer that is hit by our clients.
...
> Our operations team is pretty adamant about software/configs deployed to
> boxes in a clustering needing to be the same for every box in the
> cluster. The goal is understandable: they don't want to need custom
> install steps for every individual machine. So while my dev setup of a 5
> machine squid cluster each with 4 distinct "cache_peer ... sibling" lines
> works great so far, i can't deploy a unique squid.conf for each machine
> in a cluster.
...
> is there any easy way to reuse the same cache_peer config options on
> multiple instances, but keep squid smart enough that it doesn't bother
> trying to peer with itself?

We have similar problem for forward proxies. We use /etc/hosts table that
contains local and remote IPs different on each host (not only for squid) so
for squid I could just set up:

http_port proxy.example.com:3128
cache_peer sibling1.example.com
cache_peer sibling2.example.com
visible_hostname proxy.example.com

The only problem was unique_hostname which is (de facto) taken from
visible_hostname, so I've filled bugreport
http://www.squid-cache.org/bugs/show_bug.cgi?id=2654

for now we include small file containing only unique_hostname setting.

-- 
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
WinError #99999: Out of error messages.