1 |
>> I'm trying to reduce the number of systems I spend time managing. My |
2 |
>> previous plan was to set up multiseat on a small number of systems. |
3 |
>> Now I'm wondering if it would be better to use multiple systems with |
4 |
>> identical hardware and manage them in some sort of an optimized way so |
5 |
>> that each set of identical hardware behaves as much like a single |
6 |
>> machine as possible for management. I could use small SoC systems so |
7 |
>> I don't have to worry about sourcing components later. Is there a |
8 |
>> good tool or framework for this sort of thing? |
9 |
> |
10 |
> The solution you pick depends heavily on how many of these identical |
11 |
> machines you have. |
12 |
> |
13 |
> For some small-ish number (gut feel tells me up to around 10 or so), you |
14 |
> could do what I do for my development vms[2]: |
15 |
|
16 |
Yes, under 10. |
17 |
|
18 |
> - have 1 decent spec'ed machine as the master and buildhost |
19 |
> - share /etc/portage/, $PORTDIR, /var/packages and /var/distfiles to all |
20 |
> clients from some central location (NFS works really well for this) |
21 |
> - for each package you want to have on a client, emerge it on the |
22 |
> buildhost with the -b option (create binary packages) |
23 |
> - emerge stuff on the clients with the -k (or possibly -K) option to use |
24 |
> binary packages. Everything should show up in purple. If anything is a |
25 |
> different colour, emerge that package on the buildhost and remerge it on |
26 |
> the client. |
27 |
> - for awesome street cred geek-points, install clusterssh and do all |
28 |
> your clients in parallel[1] |
29 |
> |
30 |
> As long as you share important directories to each client, things stay |
31 |
> consistent. What you essentially achieve is "build once-install many times" |
32 |
> |
33 |
> However, and I'm likely to get shot down for this here, I think you |
34 |
> *really* need to reconsider whether Gentoo is even what you should be |
35 |
> using for this. Put aside emotional attachments to your fav distro and |
36 |
> take a long hard critical look at your pain-gain ratio. If all you |
37 |
> really need is standard user-type gui stuffs on each client, what is |
38 |
> Gentoo really buying you (other than the thrill of watching gcc output |
39 |
> scroll by over and over and over....) |
40 |
> |
41 |
> Use gentoo by all means on your central server to get exactly the |
42 |
> features you want (Gentoo's strong point), but ona bunch of regular |
43 |
> clients... I dunno, Ubuntu or Fedora are hard to beat for that... |
44 |
|
45 |
I'm thinking of a different approach and I'm getting pretty excited. |
46 |
|
47 |
I realized I only need two types of systems in my life. One hosted |
48 |
server and bunch of identical laptops. My laptop, my wife's laptop, |
49 |
our HTPC, routers, and office workstations could all be on identical |
50 |
hardware, and what better choice than a laptop? Extremely |
51 |
space-efficient, portable, built-in UPS (battery), and no need to buy |
52 |
a separate monitor, keyboard, mouse, speakers, camera, etc. Some |
53 |
systems will use all of that stuff and some will use none, but it's |
54 |
OK, laptops are getting cheap, and keyboard/mouse/video comes in handy |
55 |
once in a while on any system. |
56 |
|
57 |
What if my laptop is the master system and I install any application |
58 |
that any of the other laptops need on my laptop and push its entire |
59 |
install to all of the other laptops via rsync whenever it changes? |
60 |
The only things that would vary by laptop would be users and |
61 |
configuration. Maybe puppet could help with that? It would almost be |
62 |
like my own distro. Some laptops would have stuff installed that they |
63 |
don't need but at least they aren't running Fedora! :) |
64 |
|
65 |
If I can make this work I will basically only admin my laptop and |
66 |
hosted server no matter how large the office grows. Huge time savings |
67 |
and huge scalability. No multiseat required. Please shoot this down! |
68 |
|
69 |
- Grant |