We have three level configuration with reservation of components on each
level.
This is common scheme for our configuration (LVS-NAT):
Clients -> 2-LB for WebSrv -> 2-WebSrv -> 2-LB for AppSrv -> 2-AppSrv ->
2-DBSrv -> SAN
--------------- ---------------
VIP-1 & DG-1 VIP-2 & DG-2
But we cut two seconds LBs and assign its function on firsts LBs.
Now two LBs serve VIP not only for external clients but for
internal servers also. One LB (from this two) is MASTER for VIP-1 and DG-1
and BACKUP for VIP-2 and DG-2. Another LB vise versa is MASTER for VIP-2 and
DG-2
and BACKUP for VIP-1 and DG-1. I try to draw it on this scheme:
Clients -> 2-LB for -> 2-WebSrv
WebSrv & AppSrv <-
-> 2-AppSrv -> 2-DBSrv -> SAN
---------------
VIP-1 & VIP-2
DG-1 & DG-2
Load Balancers
--------------------------
static IPs
----------
LB-1 - 192.168.34.3
LB-2 - 192.168.34.4
dynamic (virtual) IPs (Keepalived)
----------------------------------
VIP-1 - 192.168.34.103 (WebSrv Virtual IP)
VIP-2 - 192.168.34.104 (AppSrv Virtual IP)
DG-1 - 192.168.35.101 (Default Gateway for WebSrv)
DG-2 - 192.168.33.101 (Default Gateway for AppSrv)
Web Servers
---------------------------
WebSrv-1 - 192.168.35.3
WebSrv-2 - 192.168.35.4
Application Servers
---------------------------
AppSrv-1 - 192.168.33.3
AppSrv-2 - 192.168.33.4
Config attached.
All work fine!
Many thanks to all developers.
Regards,
Alex
VB> Gents,
VB> Using keepalived for management of the LVS environment. So far... I
VB> love it.
VB> Right now, my need is to configure persistency, so that way I ensure
VB> that each click is to the same real server (shopping cart sake).
VB> Since you guys are pros, can you please warn me about things I am
VB> not aware of?
VB> Within keepalived.conf, I have these settings:
VB> lb_algo rr/wrr/lc/wlc/sh/dh/lblc First of all, I cant
VB> really find much documentation on the way keepalived loadbalances
VB> things... Can someone URL me so I can read read read :)
VB> Second, there are 2 more settings, persistence_timeout and
VB> persistence_granuality... again, same problem, cant really find much to
VB> read. I will google on.
VB> If you guys would like to share a working config for your
VB> keepalived.conf section, that would rock.
VB> Basicly, what this scenario is for is for about 50K-100K concurrent
VB> users to a shopping cart, running on separate real servers, so making
VB> sure people hit the same real server is essential.
VB> THANKS GUYS! :)
|