From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HqAmq-0001NE-Lq for garchives@archives.gentoo.org; Mon, 21 May 2007 16:31:09 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4LGUUMf025663; Mon, 21 May 2007 16:30:30 GMT Received: from smtp103.sbc.mail.mud.yahoo.com (smtp103.sbc.mail.mud.yahoo.com [68.142.198.202]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4LGSU7q023287 for ; Mon, 21 May 2007 16:28:33 GMT Received: (qmail 7494 invoked from network); 21 May 2007 16:28:28 -0000 Received: from unknown (HELO ?0.0.0.0?) (gibbonsr@att.net@69.13.46.6 with plain) by smtp103.sbc.mail.mud.yahoo.com with SMTP; 21 May 2007 16:28:27 -0000 X-YMail-OSG: vrciJcwVM1lJjz6XnB.0swa_XA_VcQ7zyyD9DXiSZt6joreM Message-ID: <4651C876.2@routedtechnologies.com> Date: Mon, 21 May 2007 11:27:34 -0500 From: Ryan Gibbons User-Agent: Thunderbird 3.0a1 (X11/20070404) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-server@gentoo.org Reply-to: gentoo-server@lists.gentoo.org MIME-Version: 1.0 To: gentoo-server@lists.gentoo.org Subject: Re: [gentoo-server] Best practices in managing large server groups References: <4650937E.80301@spamcop.net> <4650BCC7.60909@vanalteren.nl> <246510DE-93FF-46CD-AF10-70C53C8442A7@rogers.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------020401070805060804050500" X-Archives-Salt: 1016b3e9-b304-43d3-bd7e-8fb7077ecea4 X-Archives-Hash: 9732761efbf33341153ea0304d992548 This is a multi-part message in MIME format. --------------020401070805060804050500 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit I believe you will still need a tree either way. I would just have the master server share it's portage tree over nfs, and then when you update the nodes of the cluster, just mount the nfs share, run your emerge system or world or whatever, and then when you are finished umount the nfs share. I imagine this could be done easily via scripts, complete with error checking for bad mounts bad emerges etc. Ronan Mullally wrote: > Hi Karl, > > On Mon, 21 May 2007, Karl Holz wrote: > > >>> Is there a way to run gentoo without a portage tree on each box? >>> >> yes, if you setup a build system, using a stage3 tarball, and build your >> system into a directory. Portage will only be under your /usr/portage and not >> into the system image you're building. the good thing about using a Stage3 >> tarball is you can build you system on any linux system, build your system >> image, tarball the image, deploy and install grub on x86, yaboot on Mac PPC, >> silo on Sparc64. >> > > How are updates handled? "emerge -uD " isn't going to work > without a portage tree, so I presume I'd need to tell each server which > packages need to be updated with "emerge ... " to have > it download them from the binhost? > > > -Ronan > --------------020401070805060804050500 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit I believe you will still need a tree either way.

I would just have the master server share it's portage tree over nfs, and then when you update the nodes of the cluster, just mount the nfs share, run your emerge system or world or whatever, and then when you are finished umount the nfs share.

I imagine this could be done easily via scripts, complete with error checking for bad mounts bad emerges etc.

Ronan Mullally wrote: 
Hi Karl,

On Mon, 21 May 2007, Karl Holz wrote:

  
Is there a way to run gentoo without a portage tree on each box?
      
yes, if  you setup a build system, using a stage3 tarball, and build your
system into a directory. Portage will only be under your /usr/portage and not
into the system image you're building. the good thing about using a Stage3
tarball is you can build you system on any linux system, build your system
image, tarball the image, deploy and install grub on x86, yaboot on Mac PPC,
silo on Sparc64.
    

How are updates handled?  "emerge -uD <pkg|world>" isn't going to work
without a portage tree, so I presume I'd need to tell each server which
packages need to be updated with "emerge <pkg1> <pkg2> ... <pkgn>" to have
it download them from the binhost?


-Ronan
--------------020401070805060804050500-- -- gentoo-server@gentoo.org mailing list