Hello all, The question is not necessarily CentOS-specific - but there are lots of bright people on here, and - quite possibly - the final implementation will be on CentOS hence I figured I'd ask it here. Here is the situation. I need to configure a Linux-based network load balancer (NLB) solution. The idea is this. Let us say I have a public facing load balancer machine with an public IP of, say, 50.50.50.50. It is to receive the traffic (let's say, HTTP traffic) and then route it to two private HTTP servers, let's say, 192.168.10.10 and 192.168.10.11. It has to have persistence - i.e., be state- and session-aware. If for whatever reason one of the servers goes down the remaining pool shares all the traffic in some fashion (be it eound robin, saturation based, whatever). We have tried Vyatta ( http://vyatta.org/ ) and ZeroShell ( http://www.zeroshell.org/ ) and both are very good but their NLB seems to be externally facing (i.e., you have several internet connections and are trying to divide your traffic between them). What we need is an "internally facing" one, if I may say so. Any advice on what may help us would be greatly appreciated. Thanks. Boris.
Am 19.01.2013 um 21:35 schrieb Boris Epstein <borepstein at gmail.com>:> Hello all, > > The question is not necessarily CentOS-specific - but there are lots of > bright people on here, and - quite possibly - the final implementation will > be on CentOS hence I figured I'd ask it here. Here is the situation. > > I need to configure a Linux-based network load balancer (NLB) solution. The > idea is this. Let us say I have a public facing load balancer machine with > an public IP of, say, 50.50.50.50. It is to receive the traffic (let's say, > HTTP traffic) and then route it to two private HTTP servers, let's say, > 192.168.10.10 and 192.168.10.11. It has to have persistence - i.e., be > state- and session-aware. If for whatever reason one of the servers goes > down the remaining pool shares all the traffic in some fashion (be it eound > robin, saturation based, whatever). > > We have tried Vyatta ( http://vyatta.org/ ) and ZeroShell ( > http://www.zeroshell.org/ ) and both are very good but their NLB seems to > be externally facing (i.e., you have several internet connections and are > trying to divide your traffic between them). What we need is an "internally > facing" one, if I may say so. > > Any advice on what may help us would be greatly appreciated.Did you check haproxy -> http://haproxy.1wt.eu. Application session should be shared via distributed key-value store (e.g. redis). Speak another instance to manage. -- LF
On Sat, Jan 19, 2013 at 3:35 PM, Boris Epstein <borepstein at gmail.com> wrote:> Hello all, > > The question is not necessarily CentOS-specific - but there are lots of > bright people on here, and - quite possibly - the final implementation will > be on CentOS hence I figured I'd ask it here. Here is the situation. > > I need to configure a Linux-based network load balancer (NLB) solution. The > idea is this. Let us say I have a public facing load balancer machine with > an public IP of, say, 50.50.50.50. It is to receive the traffic (let's say, > HTTP traffic) and then route it to two private HTTP servers, let's say, > 192.168.10.10 and 192.168.10.11. It has to have persistence - i.e., be > state- and session-aware. If for whatever reason one of the servers goes > down the remaining pool shares all the traffic in some fashion (be it eound > robin, saturation based, whatever). > > We have tried Vyatta ( http://vyatta.org/ ) and ZeroShell ( > http://www.zeroshell.org/ ) and both are very good but their NLB seems to > be externally facing (i.e., you have several internet connections and are > trying to divide your traffic between them). What we need is an "internally > facing" one, if I may say so. > > Any advice on what may help us would be greatly appreciated. > > Thanks. > > Boris.Add another vote for HAproxy. It's excellent at what it does, as long as it meets your requirements. It's main purpose is to load balance HTTP traffic, and it can maintain session using a cookie. It will monitor each server and remove it from rotation if it goes down. It also has methods to place servers into maintenance mode. It doesn't really handle SSL (though they have been working on it for newer versions), but that can be handled by using Apache or nginx as the front-end termination point for SSL, and reverse proxy into haproxy. It also does generic TCP load balancing, but I don't use it so can't comment on that. ? Brian Mathis
On 19/1/2013 10:35 ??, Boris Epstein wrote:> Any advice on what may help us would be greatly appreciated.Have you checked HAProxy (http://haproxy.1wt.eu)? Nick
On 19.01.2013 20:35, Boris Epstein wrote:> Any advice on what may help us would be greatly appreciated.Haproxy. Session-aware, SSL-aware, extremely light and powerful. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
On 19/1/2013 10:35 ??, Boris Epstein wrote:> Any advice on what may help us would be greatly appreciated.Some reading that might help in making up your mind: http://www.chinanetcloud.com/blog/load-balancing-haproxy-vs-nginx http://www.techopsguys.com/tag/netscaler/ http://blog.exceliance.fr/2012/09/10/how-to-get-ssl-with-haproxy-getting-rid-of-stunnel-stud-nginx-or-pound/ http://blog.exceliance.fr/2012/08/25/haproxy-varnish-and-the-single-hostname-website/ You'll undoubtedly find more material on the iNet, but I hope the above may serve as a starting point. Good luck, Nick
Hello all, Many thanks to everyone who responded with extremely helpful tips. Reporting back that I implemented HAProxy on CentOS 6.3 and this works like a charm - after I worked out a couple of HAProxy kinks. Boris. On Sat, Jan 19, 2013 at 3:35 PM, Boris Epstein <borepstein at gmail.com> wrote:> Hello all, > > The question is not necessarily CentOS-specific - but there are lots of > bright people on here, and - quite possibly - the final implementation will > be on CentOS hence I figured I'd ask it here. Here is the situation. > > I need to configure a Linux-based network load balancer (NLB) solution. > The idea is this. Let us say I have a public facing load balancer machine > with an public IP of, say, 50.50.50.50. It is to receive the traffic (let's > say, HTTP traffic) and then route it to two private HTTP servers, let's > say, 192.168.10.10 and 192.168.10.11. It has to have persistence - i.e., be > state- and session-aware. If for whatever reason one of the servers goes > down the remaining pool shares all the traffic in some fashion (be it eound > robin, saturation based, whatever). > > We have tried Vyatta ( http://vyatta.org/ ) and ZeroShell ( > http://www.zeroshell.org/ ) and both are very good but their NLB seems to > be externally facing (i.e., you have several internet connections and are > trying to divide your traffic between them). What we need is an "internally > facing" one, if I may say so. > > Any advice on what may help us would be greatly appreciated. > > Thanks. > > Boris. >
Pound Load Balancer is pretty good in my experience. On 19 January 2013 20:35, Boris Epstein <borepstein at gmail.com> wrote:> Hello all, > > The question is not necessarily CentOS-specific - but there are lots of > bright people on here, and - quite possibly - the final implementation will > be on CentOS hence I figured I'd ask it here. Here is the situation. > > I need to configure a Linux-based network load balancer (NLB) solution. The > idea is this. Let us say I have a public facing load balancer machine with > an public IP of, say, 50.50.50.50. It is to receive the traffic (let's say, > HTTP traffic) and then route it to two private HTTP servers, let's say, > 192.168.10.10 and 192.168.10.11. It has to have persistence - i.e., be > state- and session-aware. If for whatever reason one of the servers goes > down the remaining pool shares all the traffic in some fashion (be it eound > robin, saturation based, whatever). > > We have tried Vyatta ( http://vyatta.org/ ) and ZeroShell ( > http://www.zeroshell.org/ ) and both are very good but their NLB seems to > be externally facing (i.e., you have several internet connections and are > trying to divide your traffic between them). What we need is an "internally > facing" one, if I may say so. > > Any advice on what may help us would be greatly appreciated. > > Thanks. > > Boris. > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >-- Kind Regards, Christopher J. Buckley
Apparently Analagous Threads
- load balancer recommendation
- getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device
- 8-15 TB storage: any recommendations?
- getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device
- djbdns under CentOS7: startup and socket issues