From owner-freebsd-cluster Tue Jul 9 14:24: 9 2002 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 8339837B400 for ; Tue, 9 Jul 2002 14:24:05 -0700 (PDT) Received: from ws5-2.us4.outblaze.com (205-158-62-132.outblaze.com [205.158.62.132]) by mx1.FreeBSD.org (Postfix) with SMTP id 371FB43E09 for ; Tue, 9 Jul 2002 14:24:05 -0700 (PDT) (envelope-from click46@operamail.com) Received: (qmail 16404 invoked by uid 1001); 9 Jul 2002 21:24:04 -0000 Message-ID: <20020709212404.16403.qmail@operamail.com> Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [207.105.193.195] by ws5-2.us4.outblaze.com with http for click46@operamail.com; Wed, 10 Jul 2002 05:24:04 +0800 From: "aaron g" To: Cc: freebsd-cluster@freebsd.org Date: Wed, 10 Jul 2002 05:24:04 +0800 Subject: Re: SPREAD clusters X-Originating-Ip: 207.105.193.195 X-Originating-Server: ws5-2.us4.outblaze.com Sender: owner-freebsd-cluster@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From my limited knowledge of the project I beleive this is not out of the question. Infact it may have been Andy himself who made reference to the VMS like clustering technology. I'm not really in a place to give a definitive answer but I too am interested in a solution for the situation you describe. - aarong ----- Original Message ----- From: Clifton Royston Date: Tue, 9 Jul 2002 09:51:32 -1000 To: Andy Sporner Subject: Re: SPREAD clusters > > Is there a document explaining the scope of the project, what kinds > of problems it's intended to address, and the overall outline or > roadmap? I'm having a hard time getting that from the URL you posted. > (I'm also new to this list, obviously.) > > Is the current project aimed at application failover and load-balancing > for specific applications, i.e. providing the software equivalent of a > "layer 4" or load balancing Ethernet switch? > > Or does it generically instantiate all network applications into the > same failover and load-balancing environment? > > Or is it more like Mosix, in which servers join a kind of "hive mind" > where any processor can vfork() a process onto a different server with > more RAM/CPU available, but processes have to remain on the original > machine to do device I/O? > > Or is it like Digital (R.I.P.s) Vax VMS or "TrueUNIX" clustering, > where for most purposes the clustered servers behaved like a single > machine, with shared storage, unified access to file systems and > devices, etc.? > > My main practical interest is in the nitty-gritty of building > practical highly reliable and highly scalable mail server clusters, > both for mail delivery (SMTP,LMTP) and mail retrieval (POP, IMAP.) The > main challenge in doing this right now is dealing with the need for all > servers to have a coherent common view of the file systems where mail > is stored. This means the cluster solution needs to include shared > storage, either via NFS or via some better mechanism which provides > reliable sharing of file systems between multiple servers and allows > for server failure without interruption of data access. > > Is this kind of question outside the scope of the current project? > > -- Clifton > > -- > Clifton Royston -- LavaNet Systems Architect -- cliftonr@lava.net > "What do we need to make our world come alive? > What does it take to make us sing? > While we're waiting for the next one to arrive..." - Sisters of Mercy > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-cluster" in the body of the message > -- _______________________________________________ Download the free Opera browser at http://www.opera.com/ Free OperaMail at http://www.operamail.com/ Powered by Outblaze To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-cluster" in the body of the message