Re: Zope and Ultramonkey: balancing more ZEO clients on the same machine

Paolo Asioli <[email protected]> wrote:
> [-- text/plain, encoding quoted-printable, charset: ISO-8859-1, 201 lines --]
> 
> No, it doesn't seem to work   :(
> 
> I'll try to recap:
> 
> CLIENTS
>   |  LAN1 (192.168.1.x)
>   |---------------------|
> (VIP 192.168.1.10)       | 
> 192.168.1.11          192.168.1.12
> |----------------|    |----------------|
> |REDIRECTOR      |    |STBY REDIRECTOR |  
> |realserver 1    |    |realserver 2    |   
> |(Apache on port |    |(Apache on port |  
> |10080, 10081,   |    |10080, 10081,   |   
> |10082)          |    |10082)          |   
> |----------------|    |----------------|  
> 192.168.2.11          192.168.2.12
>   |---------------------|
>      LAN2 (192.168.2.x)
> 
> 
> Every port is bound to an Apache Virtual Host that interacts with a 
> separate instance of Zope.
> 
> The relevant part of my ldirectord.cf is
> 
> # Virtual Server for HTTP
> virtual=192.168.1.10:80
>        real=192.168.2.11:10080 masq
>        real=192.168.2.12:10080 masq
>        real=192.168.2.11:10081 masq
>        real=192.168.2.12:10081 masq
>        real=192.168.2.11:10082 masq
>        real=192.168.2.12:10082 masq
>        service=http
>        request="index.html"
>        receive="Intranet"
>        scheduler=rr
>        protocol=tcp
>        checktype=negotiate
> 
> 
> Now ipvsadm shows the right entries, but also local entries which I 
> haven't configured
> 
> TCP  192.168.1.10:80 rr
> 
>  -> 192.168.2.12:10082        Masq    1      0          0
> 
>  -> 192.168.2.11:10082        Local   0      0          0
> 
>  -> 192.168.2.12:10081        Masq    1      0          0
> 
>  -> 192.168.2.11:10081        Local   0      0          0
> 
>  -> 192.168.2.12:10080        Masq    1      0          0
> 
>  -> 192.168.2.11:10080        Local   0      0          0


Unfortunately you are trying to do something with LVS, and thus
Ultra Monkey can't do. Here is the deal:

1. If you add a real server to LVS (using ldirectord or any other
means),
   and the real-server's IP address is a local IP address, then
   the Local forwarding machanism is autmatically used.

2. You can only do port mapping (80 -> 10080 masq) with LVS Nat
   But you aren't using NAT on 192.168.2.11 because of 1)

I have farily untested patch whith gets around this problem by
using NAT were Local would have been used if portmapping is requested.

Please feel free to test and give feeback.

http://archive.linuxvirtualserver.org/html/lvs-users/2005-06/msg00113.html

-- 
Horms


-- 
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to [email protected], with a body:
unsubscribe ultramonkey-users [email protected]
where "[email protected]" is YOUR email address.