Date: Mon, 7 Apr 2008 23:55:37 +1000 From: Norberto Meijome <freebsd@meijome.net> To: bseklecki@collaborativefusion.com Cc: Steel City Phantom <scphantm@gmail.com>, freebsd-questions@freebsd.org Subject: Re: building a distribution server 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 06 Apr 2008 14:08:21 -0400
"Brian A. Seklecki (Mobile)" <bseklecki@collaborativefusion.com> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080407235537.4764d53d>