|
At 14:36 13/03/2001 -0500, you wrote:
I'm trying to build a production LVS server.
What is the best combination of kernel (2.2 or 2.4), lvs code? I would
like to be fairly bleeding edge but this is production. I will have two
lvs servers with keepalived running. I'm also planning on using
ldirectord for the service monitoring, is that still the best choice?
Hi Matt,
What kind of service are you planing to loadbalance ? smtp, http, ssl, ...?
Your LVS design depend on your need (ie: bandwidth, ...) if you plan to use
LVS NAT your design is correct. Just think in HA using a hearthbeat or
other stuff (i am working on VRRP/HSRP right now to add a strong routing
level tolerence) => With that kind of stuff you add to your main LVS server
a Backup server and you can even loadbalance flows between the two LVS
server (master & slave).
LVS 2.2 code is really stable, but if you plan using LVS with source NAT
for example you will need 2.4.
As an example, I run in production 3 LVS (using keepalived) loadbalancing 4
servers each over HTTP & SSL protocols. It really works fine
Hope it will help you,
Best regards,
Alexandre
|
