From owner-freebsd-arch@FreeBSD.ORG Fri Apr 22 08:52:41 2005 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CBBD16A4CE for ; Fri, 22 Apr 2005 08:52:41 +0000 (GMT) Received: from postfix4-1.free.fr (postfix4-1.free.fr [213.228.0.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F75F43D2F for ; Fri, 22 Apr 2005 08:52:40 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix4-1.free.fr (Postfix) with ESMTP id 8E3EB31787E; Fri, 22 Apr 2005 10:52:38 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id C11E8405B; Fri, 22 Apr 2005 10:51:56 +0200 (CEST) Date: Fri, 22 Apr 2005 10:51:56 +0200 From: Jeremie Le Hen To: dragonfly dragonfly Message-ID: <20050422085156.GQ91329@obiwan.tataz.chchile.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i cc: freebsd-arch@freebsd.org Subject: Re: How about porting LVS to FreeBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 08:52:41 -0000 Hi, > LVS(http://www.linuxvirtualserver.org/) is a widely used server cluster > schedule system,which is be included in Linux official kernel 2.4 and 2.6 > release. > Recently i ported LVS/ipvs to FreeBSD,and released 0.1.0 version > (http://dragon.linux-vs.org/~dragonfly/htm/lvs_freebsd.htm).It is only a > draft release,only to prove that LVS can play happily with FreeBSD:).It > support LVS/DR and Round Robin schedule algorithm.It is been in hot > developing.Welcome to test it and hope it be useful. This is very interesting, thank you. I know that LVS uses keepalived(8) to do VRRP and although I must admit it is very useful and powerful, this daemon is IMHO a great mess. (For the short story, the release process is awful, not to say inexistant. Indeed, I use keepalived 1.1.7 at work and this version has an annoying bug for us but we found an acceptable workaround. New versions has been released since, but when 1.1.8 was out, there have been numerous new bugs introduced that needed the version 1.1.9 to be quickly released to correct them. But this version has in turn introduced new bugs and finally version 1.1.10 fixed everything IIRC. Now the version is 1.1.11, but I'm still waiting to jump to this version as I'm afraid to come across new bugs for which I won't find an acceptable workaround.) What I want to know is if you are planning to simply port keepalived(8) to FreeBSD or use the BSD flavoured replacement for VRRP : CARP. I'm convinced this is not a trivial job as keepalived(8) is also used as a ISO level 7 health-checker. AFAIK, VRRP is completely implemented in userland on Linux as the RFC requires to use a special MAC address for the clustered IP but the Linux kernel doesn't support to have more than one MAC address for an interface. Instead, MAC address spoofing is achieved by keepalived(8), by sending gratuitous ARP requests. I think the health-checker part is interesting in keepalived(8) but it would be nice to have the HA mechanic handled by CARP (or maybe using UCARP [1] would be easier, since it's in userland too). I'll try to look at this today. Thanks again for your work. Regards, [1] http://www.ucarp.org/ -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >