LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: LVS and dynamic routing

To: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: LVS and dynamic routing
From: Horms <horms@xxxxxxxxxxxx>
Date: Fri, 21 May 2004 10:39:56 +0900
On Tue, May 18, 2004 at 04:49:00PM -0400, Patrick LeBoutillier wrote:
> On Mon, 2004-05-17 at 14:06, Patrick LeBoutillier wrote:
> 
> >>>My question is: if heartbeat starts and brings up the alias on eth0 and
> >>>then
> >>>the network eth0 is connected to fails, will the director still be able 
> >>>to
> >>>deal with the packets even if they start coming in from eth1?
> >>>     
> >>>
> 
> Here's something I'm going to try:
> 
> - Switched from LVS-DR to LVS-TUN to allow virtual IP to be in a 
> different network than
>  realserver IP

You can do this with LVS-DR, and LVS-NAT for that matter.

> - Setup virtual IP interface on the tunl0 interface (192.168.82.1) on 
> each machine
> - Setup real IP interface on the lo interface (192.168.80.1 and 
> 192.168.81.1 respectively)
>  on each machine
> - Created "noop" heartbeat plugin so that heartbeat leaves the virtual 
> IP alias alone
>  (on tunl0) on fallback:

This part is not neccessary. Just leave the IP out of heartbeat's hands
all together.

> 
>    haresources: cluster.domain.tl noop::192.168.82.1 ldirectord ...

    haresources: cluster.domain.tl ldirectord ...

>  Heartbeat therefore no longer manages the virtual IP alias

Yes, but I am not sure how that solves your problem.
How do you effect IP address takeover? Or do you handle
geting packets to go to the newly active linux director
another way?

> 
> 
> Then:
> - Create 2 configurations for gated:
>       1) announce 192.168.8[01].0/24 (config "real_only")
>       2) announce 192.168.8[01].0/24 and192.168.82.0/24 (config "real_dir")
> 
> - Setup heartbeat so that it starts gated with "real_dir" config when 
> the ressources
>  are acquired and starts gated with "real_only" config when it looses 
> the resources.
> 
> That way gated always announces the realserver networks (so that the 
> director can reach
> the realservers) via both interfaces, but only the active director 
> announces the virtual
> IP network (again via both interfaces).
> 
> Seems like it should work, I will try it out tomorrow.
> Any comments?
> 
> 
> Patrick
> 
> -- 
> =====================
> Patrick LeBoutillier
> Laval, Quebec, Canada
> 
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users

-- 
Horms
<Prev in Thread] Current Thread [Next in Thread>