I am trying to set up LVS with NAT'ing and am having a problem that I have not been able to resolve. I have two Piranha Load Balancers that have front facing internet IP's. ... [by Crowdness]
I'm planning to add a hardware load balancer, but I'm not sure if adding one will cause me to lose the ability to restrict traffic by IP ( on folder level by using allow and deny in apache configuration)?
Do you use hardware load balancers to shift traffic with client IP or load balancer IP ?
Our infrastructure consists of load balancers running HAProxy and Apache, which forward traffic to our app servers running just Apache. The past few days, we've been seeing connection floods which the load balancers happily pass along, but the connections quickly overwhelm our application servers.
We're building a load balanced setup with two load balancers (that also terminate SSL) and several upstream servers. Both the load balancers and the upstream servers run nginx. The network on which requests are forwarded to the upstream servers cannot be trusted, hence we have to re-encrypt it after SSL termination on the load balancer.
I am tasked with setting up redundancy on two load balancers (using Haproxy & Keepalived). The idea is that we will have a load balancer managing our site but we need that load balancer to have a backup.
I am having trouble pinging a load balancer server through a VPN. I'm using keepalived for a failover to keep the load balancers redundant.
How does sticky sessions relate to HTTP and HTTPS;
If I place a load balancer in front of some web app servers that run a front end that supports HTTPS, will the sessions remain "sticky" on a typical load balancer that lists "stick sessions" as one of it's supported features?
I understand that question is partly open ended; To clarify, would I require a load balancer that supports sticky HTTPS s