public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Managing multiple systems with identical hardware
Date: Fri, 27 Sep 2013 03:37:15 -0700	[thread overview]
Message-ID: <CAN0CFw1JTGPt7B5DEHsX=20jbEU9E0urL2VaveGon9jA0q1G-g@mail.gmail.com> (raw)
In-Reply-To: <52449C1A.5000306@gmail.com>

>> I realized I only need two types of systems in my life.  One hosted
>> server and bunch of identical laptops.  My laptop, my wife's laptop,
>> our HTPC, routers, and office workstations could all be on identical
>> hardware, and what better choice than a laptop?  Extremely
>> space-efficient, portable, built-in UPS (battery), and no need to buy
>> a separate monitor, keyboard, mouse, speakers, camera, etc.  Some
>> systems will use all of that stuff and some will use none, but it's
>> OK, laptops are getting cheap, and keyboard/mouse/video comes in handy
>> once in a while on any system.
>
> Laptops are a good choice, desktops are almost dead out there, and thin
> clients nettops are just dead in the water for anything other than
> appliances and media servers
>
>> What if my laptop is the master system and I install any application
>> that any of the other laptops need on my laptop and push its entire
>> install to all of the other laptops via rsync whenever it changes?
>> The only things that would vary by laptop would be users and
>> configuration.
>
> Could work, but don't push *your* laptop's config to all the other
> laptops. they end up with your stuff which might not be what them to
> have. Rather have a completely separate area where you store portage
> configs, tree, packages and distfiles for laptops/clients and push from
> there.

I actually do want them all to have my stuff and I want to have all
their stuff.  That way everything is in sync and I can manage all of
them by just managing mine and pushing.  How about pushing only
portage configs and then letting each of them emerge unattended?  I
know unattended emerges are the kiss of death but if all of the
identical laptops have the same portage config and I emerge everything
successfully on my own laptop first, the unattended emerges should be
fine.

> I'd recommend if you have a decent-ish desktop lying around, you press
> that into service as your master build host. yeah, it takes 10% longer
> to build stuff, but so what? Do it overnight.

Well, my goal is to minimize the number of different systems I
maintain.  Hopefully just one type of laptop and a server.

>>  Maybe puppet could help with that?  It would almost be
>> like my own distro.  Some laptops would have stuff installed that they
>> don't need but at least they aren't running Fedora! :)
>
> DO NOT PROVISION GENTOO SYSTEMS FROM PUPPET.

OK, I'm thinking over how much variation there would be from laptop to laptop:

1. /etc/runlevels/default/* would vary of course.
2. /etc/conf.d/net would vary for the routers and my laptop which I
sometimes use as a router.
3. /etc/hostapd/hostapd.conf under the same conditions as #2.
4. Users and /home would vary but the office workstations could all be
identical in this regard.

Am I missing anything?  I can imagine everything else being totally identical.

What could I use to manage these differences?

> Rather keep your laptop as your laptop with it's own setup, and
> everything else as that own setup. You only need one small difference
> between what you want your laptop to have, and everything else to have,
> to crash that entire model.

I think it will work if I can find a way to manage the few differences
above.  Am I overlooking any potential issues?

- Grant


  parent reply	other threads:[~2013-09-27 10:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25 21:18 [gentoo-user] Managing multiple systems with identical hardware Grant
2013-09-25 21:42 ` Alan McKinnon
2013-09-26  9:08   ` Grant
2013-09-26 20:42     ` Alan McKinnon
2013-09-27  4:33       ` Johann Schmitz
2013-09-27  5:34         ` Alan McKinnon
2013-09-27 10:37       ` Grant [this message]
2013-09-27 19:44         ` Alan McKinnon
2013-09-27 20:30           ` [gentoo-user] " James
2013-09-29 18:36             ` Grant
2013-09-29 20:39               ` Alan McKinnon
2013-09-29 18:31           ` [gentoo-user] " Grant
2013-09-29 19:06             ` Neil Bothwick
2013-09-29 20:57             ` Alan McKinnon
2013-09-30 17:31               ` Grant
2013-09-30 19:28                 ` thegeezer
2013-09-30 19:31                 ` Alan McKinnon
2013-09-30 19:53                   ` Frank Steinmetzger
2013-10-01  6:19                     ` Grant
2013-10-01 14:04                       ` Michael Orlitzky
2013-10-01 15:00                         ` Neil Bothwick
2013-09-30 21:02                   ` Neil Bothwick
2013-10-01  6:26                     ` Grant
2013-10-01  6:07                   ` Grant
2013-10-01  6:20                     ` Alan McKinnon
2013-10-02 18:54                       ` Grant
2013-12-12 23:54                         ` Grant
2013-12-13  0:16                           ` Poison BL.
2013-12-13  0:34                             ` wraeth
2013-12-13  2:06                               ` Grant
2013-12-13  9:12                                 ` Neil Bothwick
2013-12-13  1:49                             ` Grant
2013-12-13  7:57                               ` Alan McKinnon
2013-12-13  9:18                               ` Neil Bothwick
2013-12-13  7:52                           ` Alan McKinnon
2013-10-01  7:43                     ` Neil Bothwick
2013-10-01 18:37                   ` joost

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAN0CFw1JTGPt7B5DEHsX=20jbEU9E0urL2VaveGon9jA0q1G-g@mail.gmail.com' \
    --to=emailgrant@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox