| 1 |
On 26/09/2013 11:08, Grant wrote: |
| 2 |
> I'm thinking of a different approach and I'm getting pretty excited. |
| 3 |
> |
| 4 |
> I realized I only need two types of systems in my life. One hosted |
| 5 |
> server and bunch of identical laptops. My laptop, my wife's laptop, |
| 6 |
> our HTPC, routers, and office workstations could all be on identical |
| 7 |
> hardware, and what better choice than a laptop? Extremely |
| 8 |
> space-efficient, portable, built-in UPS (battery), and no need to buy |
| 9 |
> a separate monitor, keyboard, mouse, speakers, camera, etc. Some |
| 10 |
> systems will use all of that stuff and some will use none, but it's |
| 11 |
> OK, laptops are getting cheap, and keyboard/mouse/video comes in handy |
| 12 |
> once in a while on any system. |
| 13 |
|
| 14 |
Laptops are a good choice, desktops are almost dead out there, and thin |
| 15 |
clients nettops are just dead in the water for anything other than |
| 16 |
appliances and media servers |
| 17 |
|
| 18 |
|
| 19 |
> What if my laptop is the master system and I install any application |
| 20 |
> that any of the other laptops need on my laptop and push its entire |
| 21 |
> install to all of the other laptops via rsync whenever it changes? |
| 22 |
> The only things that would vary by laptop would be users and |
| 23 |
> configuration. |
| 24 |
|
| 25 |
Could work, but don't push *your* laptop's config to all the other |
| 26 |
laptops. they end up with your stuff which might not be what them to |
| 27 |
have. Rather have a completely separate area where you store portage |
| 28 |
configs, tree, packages and distfiles for laptops/clients and push from |
| 29 |
there. |
| 30 |
|
| 31 |
I'd recommend if you have a decent-ish desktop lying around, you press |
| 32 |
that into service as your master build host. yeah, it takes 10% longer |
| 33 |
to build stuff, but so what? Do it overnight. |
| 34 |
|
| 35 |
> Maybe puppet could help with that? It would almost be |
| 36 |
> like my own distro. Some laptops would have stuff installed that they |
| 37 |
> don't need but at least they aren't running Fedora! :) |
| 38 |
|
| 39 |
Errr no. Do not do that. Do not use puppet for Gentoo systems. Let me |
| 40 |
make that clear :-) |
| 41 |
|
| 42 |
DO NOT PROVISION GENTOO SYSTEMS FROM PUPPET. |
| 43 |
|
| 44 |
You will break things horribly and will curse the day you tried. |
| 45 |
Basically, puppet and portage will get in each other's way and clobber |
| 46 |
each other. Puppet has no concept of USE flags worth a damn, cannot |
| 47 |
determine in advance what an ebuild will provide and the whole thing |
| 48 |
breaks puppet's 100% deterministic model. |
| 49 |
|
| 50 |
Puppet is designed to work awesomely well with binary distros, that is |
| 51 |
where it excels. Keep within those constraints. Same goes for chef, |
| 52 |
cfengine and various others things that accomplish the same end. |
| 53 |
|
| 54 |
|
| 55 |
> If I can make this work I will basically only admin my laptop and |
| 56 |
> hosted server no matter how large the office grows. Huge time savings |
| 57 |
> and huge scalability. No multiseat required. Please shoot this down! |
| 58 |
|
| 59 |
Rather keep your laptop as your laptop with it's own setup, and |
| 60 |
everything else as that own setup. You only need one small difference |
| 61 |
between what you want your laptop to have, and everything else to have, |
| 62 |
to crash that entire model. |
| 63 |
|
| 64 |
|
| 65 |
|
| 66 |
-- |
| 67 |
Alan McKinnon |
| 68 |
alan.mckinnon@×××××.com |
Archives