From owner-freebsd-questions@FreeBSD.ORG Mon Apr 7 13:55:43 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34F891065676 for ; Mon, 7 Apr 2008 13:55:43 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.freebsd.org (Postfix) with ESMTP id DB0EE8FC32 for ; Mon, 7 Apr 2008 13:55:42 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: (qmail 10762 invoked from network); 7 Apr 2008 08:55:42 -0500 Received: from 124-170-182-203.dyn.iinet.net.au (HELO localhost) (124.170.182.203) by sigma.octantis.com.au with (DHE-RSA-AES128-SHA encrypted) SMTP; 7 Apr 2008 08:55:41 -0500 Date: Mon, 7 Apr 2008 23:55:37 +1000 From: Norberto Meijome To: bseklecki@collaborativefusion.com Message-ID: <20080407235537.4764d53d@meijome.net> In-Reply-To: <1207505302.2821.99.camel@localhost.localdomain> References: <5c99941f0804041923t1e6e9cdbue40e782805fa34f6@mail.gmail.com> <1207505302.2821.99.camel@localhost.localdomain> X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Steel City Phantom , freebsd-questions@freebsd.org Subject: Re: building a distribution server X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2008 13:55:43 -0000 On Sun, 06 Apr 2008 14:08:21 -0400 "Brian A. Seklecki (Mobile)" wrote: > It also sounds like you need a load balancer to do zero-downtime > upgrades. Just take a server out of production, upgrade it, validate it > with the new OS, and put it back into rotation. and if u dont want to spend $$ on a LB and u understand your server / traffic load, just move the public IP of the server being upgraded to another server. Of course, this assumes u have at least one spare public IP to assign to the server being upgraded.... btw, building packages, sharing and installing with portupgrade -PP works GREAT in 99.999% of the cases. If you cant be bothered with NFS, just rsync the /usr/ports/packages/All dir :) B _________________________ {Beto|Norberto|Numard} Meijome Never attribute to malice what can adequately be explained by incompetence. I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.