Jason Stubbs wrote:
> Joe Rizzo wrote:
> 
>> I am looking at deploying a large scale installation of systems running
>> Gentoo.  (Large scale being 200-300 systems)  Currently, I am mainly
>> concerned with how to handle portage and packages.

I've been wanting to deal with that myself, but haven't had a chance to
figure out the best method to do so. I'd be interested in what you come
up with in the end that works!


> Although it pains me to say it, I'd suggest not using emerge's remote
> binary package feature. Instead, you'd be much safer to rsync the binary
> packages as well and use portage with the local package repository. To
> be quite honest, that particular feature in it's current implementation
> is basically unmaintained and has several obscure bugs that hit often.
> This will be rectified in the next major portage release, but until then
> the ideas and methods you outlined would be your best bet.

Also, if you include updates from the main tree that include movement of
packages between categories, sometimes the binary packages will get
broken because of that. I'm sure Jason can point out the problem with
that, but I've been bit by that a few times myself.

> As for the actual rolling out of upgrades and configuration changes,
> I've heard many people rave about cfengine. I believe it is used
> extensively throughout gentoo's own infrastructure as well. I haven't
> spent the time to learn it myself yet though so can't offer any advice
> beyond that either.

Yes, if you want to do simple config pushes, cfengine would be the
perfect fit. We do use it throughout all of Gentoo's infrastructure and
makes our life much easier (though, sometimes its a pain). Just make
sure you read up on their documentation (which is great), and maybe add
yourself to their help mailing list.

-- 
Lance Albertson <[EMAIL PROTECTED]>
Gentoo Infrastructure | Operations Manager

---
GPG Public Key:  <http://www.ramereth.net/lance.asc>
Key fingerprint: 0423 92F3 544A 1282 5AB1  4D07 416F A15D 27F4 B742

ramereth/irc.freenode.net

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to