LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: ip_vs_user_sync_simple-1.0.2 and kernel 2.4.28

To: jimm@xxxxxxxxxxxxxxx, <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: ip_vs_user_sync_simple-1.0.2 and kernel 2.4.28
From: Horms <horms@xxxxxxxxxxxx>
Date: Tue, 12 Apr 2005 14:54:33 +0900
On Fri, Apr 08, 2005 at 01:00:26PM -0500, Jim Miller wrote:
> > -----Original Message-----
> > From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx
> > [mailto:lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Jim Miller
> > Sent: Friday, April 08, 2005 11:52 AM
> > To: LinuxVirtualServer.org users mailing list.
> > Subject: ip_vs_user_sync_simple-1.0.2 and kernel 2.4.28
> >
> >
> > Hi everyone,
> >
> > Sorry to be mister pesty but I have a few questions.  I'm trying to use
> > Horms' ip_vs_user_sync_simple-1.0.2 and linux-2.4.26-user_sync.3.patch.  I
> > read that ipvs 1.0.12 is in the 2.4.28 kernel.  Do I still need the
> > ip_vs_user_sync patch with ipvs 1.0.12 in 2.4.28?  Or should I just stick
> > with 2.4.26 and ipvs 1.0.10?
> >
> >
> > Thanks,
> > Jim
> >
> >
> > _______________________________________________
> 
> 
> I think I answered my own question and hopefully I'm understanding it
> correctly ;)
> 
> I was just re-reading Chapter 28 of the LVS-HOWTO.. specifically 28.5 where
> Horms says, "In 2.6 the code has been enhanced by Julian to allow a
> peer-to-peer setup. The current 2.6 code allows you to run a master or a
> backup sync daemon. If you want p2p then you just run both - previously you
> could only run one or the other. This is configured through ipvsadm."
> 
> So I'm going to compile 2.6.11-7 w/hidden-2.6.9 arp patch (and all the IPVS
> support of course) and once I get saru to compile ;) I'll just run the
> following on both directors:
> ipvsadm --start-daemon=master -mcast-interface=ethx
> ipvsadm --start-daemon=backup -mcast-interface=ethx

Yes. The patch that I wrote takes a slightly different approach to the
problem. In some ways I think its a bit better. In some ways a bit
worse. Julian's fixes are included in the kernel, so I would recommend
using that.

-- 
Horms

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