| 1 |
I was thinking of that, too, but what about the cascade effect of packages |
| 2 |
being built for a specific arch? Like say, GCC on the build box was built |
| 3 |
against different CFLAGS than what Apache is being built against? |
| 4 |
|
| 5 |
Am I just splitting hairs here? |
| 6 |
|
| 7 |
I'm getting ready to implement two production Gentoo servers and have a |
| 8 |
box with a different arch. Maybe the secondary production server with the |
| 9 |
exact same arch as the primary would be a better test bed? |
| 10 |
|
| 11 |
|
| 12 |
On Wed, October 19, 2005 11:50, Michael Crute wrote: |
| 13 |
> On 10/19/05, Robert Larson <robert@×××××××××.com> wrote: |
| 14 |
>> |
| 15 |
>> Hello, |
| 16 |
>> |
| 17 |
>> I was wondering if anyone has information on a good method to centrally |
| 18 |
>> build |
| 19 |
>> and push packages out to machines with Gentoo. I have multiple machines |
| 20 |
>> setup under multiple processor types, and up until now I have been |
| 21 |
>> executing |
| 22 |
>> upgrades on the machines themselves. Since these are production |
| 23 |
>> machines, |
| 24 |
>> I |
| 25 |
>> would like to set up another machine that acts as a compile/install |
| 26 |
>> machine. |
| 27 |
>> |
| 28 |
>> This might be compareable to a "gold server", as described at |
| 29 |
>> infrastructures.org <http://infrastructures.org>. I don't suppose I |
| 30 |
>> could |
| 31 |
>> get around this using distcc? |
| 32 |
>> |
| 33 |
>> Configuration management is another issue. As it is, I have cfengine |
| 34 |
>> setup, |
| 35 |
>> though it is not setup to work with portage and I can't really see these |
| 36 |
>> two |
| 37 |
>> coming together nicely. Maybe I could create a patch for |
| 38 |
>> dispatch-conf... |
| 39 |
>> |
| 40 |
>> Mind you, I have no idea on where to even start on something like this, |
| 41 |
>> so |
| 42 |
>> any |
| 43 |
>> thoughts, ideas, or information would be helpful. |
| 44 |
>> |
| 45 |
>> |
| 46 |
> You could use one server to build binary packages and then emerge them on |
| 47 |
> the systems that need the upgrades, saves a lot of resources over running |
| 48 |
> the compile on each machine. Not sure how to handle the multiple archs |
| 49 |
> however, perhaps you could write some scripts to "change out" your build |
| 50 |
> environment on the build machine and re-build the packages for each arch. |
| 51 |
> That approach should be as simple as changing out your /etc/make.conf file |
| 52 |
> if all the servers use the same build profile otherwise it's going to |
| 53 |
> involve a bit more work. |
| 54 |
> |
| 55 |
> -Mike |
| 56 |
> |
| 57 |
> -- |
| 58 |
> ________________________________ |
| 59 |
> Michael E. Crute |
| 60 |
> Software Developer |
| 61 |
> SoftGroup Development Corporation |
| 62 |
> |
| 63 |
> Linux, because reboots are for installing hardware. |
| 64 |
> "In a world without walls and fences, who needs windows and gates?" |
| 65 |
> |
| 66 |
|
| 67 |
|
| 68 |
-- |
| 69 |
Steven McCoy |
| 70 |
Site Development/Manager |
| 71 |
IndigoRobot Services |
| 72 |
http://www.indigorobot.com |
| 73 |
mailto:stevenmccoy@×××××××××××.com |
| 74 |
|
| 75 |
-- |
| 76 |
gentoo-server@g.o mailing list |
Archives