From owner-freebsd-cluster@FreeBSD.ORG Tue Feb 10 04:20:09 2004 Return-Path: Delivered-To: freebsd-cluster@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04B4916A4CE for ; Tue, 10 Feb 2004 04:20:09 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4FC143D1F for ; Tue, 10 Feb 2004 04:20:08 -0800 (PST) (envelope-from sporner@nentec.de) Received: from [212.227.126.179] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1AqWs3-0003p4-00 for freebsd-cluster@freebsd.org; Tue, 10 Feb 2004 13:20:07 +0100 Received: from [194.25.215.66] (helo=gate.nentec.de) (TLSv1:EDH-RSA-DES-CBC3-SHA:168) (Exim 3.35 #1) id 1AqWs3-0004cT-00 for freebsd-cluster@FreeBSD.ORG; Tue, 10 Feb 2004 13:20:07 +0100 Received: from nenny.nentec.de (nenny.nentec.de [153.92.64.1]) by gate.nentec.de (8.11.3/) with ESMTP id i1ACK5d16279 for ; Tue, 10 Feb 2004 13:20:05 +0100 Received: from nentec.de (andromeda.nentec.de [153.92.64.34]) by nenny.nentec.de (8.11.3/8.11.3) with ESMTP id i1ACJon05459 for ; Tue, 10 Feb 2004 13:19:51 +0100 Message-ID: <4028CC66.80300@nentec.de> Date: Tue, 10 Feb 2004 13:19:50 +0100 From: Andy Sporner User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2a) Gecko/20020910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-cluster References: <187a6c3bb6bd5002259b39e485140752@202.157.183.139> <4028A614.8030103@nentec.de> <20040210015115.C17961@knight.ixsystems.net> <1076410247.1150.28.camel@ip16.ops.uk.psi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:56ea142331898a06f3703ddc80e12bc5 Subject: Clustering with FreeBSD X-BeenThere: freebsd-cluster@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Clustering FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2004 12:20:09 -0000 Hi, It is a different subject and I sort of hate threads that are misleading. So far it hasn't happened yet, but before it can. :-) The clustering that I am offering is *NOT* Beowulf-like. It is more geared towards Internet Application HA. In other words--server X dies, what should server Y and Z do to make sure that the stuff on server X does not have to wait for server X to recover. Somewhere else on my site I have a utility called FREP. In my test area in my lab I have the two things integrated. There is in Linux-Land a thing called sometime like "Remote raw disk" (can't remember specifically what it is called) but it gives a local device node for a remote device on another machine. What FREP does (at the moment only in the lab) is to syncronize access to directories and replicate the changes done by the nodes. The idea is to be able to have a 2-3 nodes running mail servers with the spool directories replicated (locking is on the file basis). A load balancer goes on the front and with this you have a scalabale Mail server that is fault resiliant. A lot of people in the academic community are worried about Beowulf and for correct reason, but there is an often neglected area which is where Micro$oft is winning in the moment and that is in the business end of the house. Cheers.