1 |
>> Keeping all of the laptops 100% identical as far as hardware is |
2 |
>> central to this plan. I know I'm setting myself up for big problems |
3 |
>> otherwise. |
4 |
>> |
5 |
>> I'm hoping I can emerge every package on my laptop that every other |
6 |
>> laptop needs. That way I can fix any build problems and update any |
7 |
>> config files right on my own system. Then I would push config file |
8 |
>> differences to all of the other laptops. Then each laptop could |
9 |
>> emerge its own stuff unattended. |
10 |
> |
11 |
> I see what you desire now - essentially you want to clone your laptop |
12 |
> (or big chunks of it) over to your other workstations. |
13 |
|
14 |
That sounds about right. |
15 |
|
16 |
> To get a feel for how it works, visit puppet's web site and download |
17 |
> some of the test appliances they have there and run them in vm software. |
18 |
> Set up a server and a few clients, and start experimenting in that |
19 |
> sandbox. You'll quickly get a feel for how it all hangs together (it's |
20 |
> hard to describe in text how puppet gets the job done, so much easier to |
21 |
> do it for real and watch the results) |
22 |
|
23 |
Puppet seems like overkill for what I need. I think all I really need |
24 |
is something to manage config file differences and user accounts. At |
25 |
this point I'm thinking I shouldn't push packages themselves, but |
26 |
portage config files and then let each laptop emerge unattended based |
27 |
on those portage configs. I'm going to bring this to the 'salt' |
28 |
mailing list to see if it might be a good fit. It seems like a much |
29 |
lighter weight application. |
30 |
|
31 |
I'm soaking up a lot of your time (again). I'll return with any real |
32 |
Gentoo questions I run into and to run down the final plan before I |
33 |
execute it. Thanks so much for your help. Not sure what I'd do |
34 |
without you. :) |
35 |
|
36 |
- Grant |