| 1 |
Joe Rizzo wrote: |
| 2 |
> I am looking at deploying a large scale installation of systems running |
| 3 |
> Gentoo. (Large scale being 200-300 systems) Currently, I am mainly |
| 4 |
> concerned with how to handle portage and packages. |
| 5 |
> |
| 6 |
<snip> |
| 7 |
> |
| 8 |
> Please provide experience or ideas on: |
| 9 |
> 1) Creating and maintaining a minimal gentoo image? |
| 10 |
|
| 11 |
I'll leave this one to those with experience, but I'll at least offer |
| 12 |
the advise of "test test test!" ;) |
| 13 |
|
| 14 |
> 2) Managing portage and packages for a large scale gentoo environment? |
| 15 |
|
| 16 |
Although it pains me to say it, I'd suggest not using emerge's remote |
| 17 |
binary package feature. Instead, you'd be much safer to rsync the binary |
| 18 |
packages as well and use portage with the local package repository. To |
| 19 |
be quite honest, that particular feature in it's current implementation |
| 20 |
is basically unmaintained and has several obscure bugs that hit often. |
| 21 |
This will be rectified in the next major portage release, but until then |
| 22 |
the ideas and methods you outlined would be your best bet. |
| 23 |
|
| 24 |
As for the actual rolling out of upgrades and configuration changes, |
| 25 |
I've heard many people rave about cfengine. I believe it is used |
| 26 |
extensively throughout gentoo's own infrastructure as well. I haven't |
| 27 |
spent the time to learn it myself yet though so can't offer any advice |
| 28 |
beyond that either. |
| 29 |
|
| 30 |
Regards, |
| 31 |
Jason Stubbs |
| 32 |
-- |
| 33 |
gentoo-server@g.o mailing list |
Archives