From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: kashani <kashani-list@badapple.net>
Subject: Re: [gentoo-user] Managing multiple Gentoo systems
Date: Thu, 07 Jul 2011 22:37:13 +0200 [thread overview]
Message-ID: <2206705.m0niYJH5nW@nazgul> (raw)
In-Reply-To: <4E15F993.1080901@badapple.net>
On Thursday 07 July 2011 11:23:15 kashani did opine thusly:
> On 7/2/2011 3:14 PM, Grant wrote:
> > After a frustrating experience with a Linksys WRT54GL, I've
> > decided to stick with Gentoo routers. This increases the
> > number of Gentoo systems I'm responsible for and they're
> > nearing double-digits. What can be done to make the management
> > of multiple Gentoo systems easier? I think identical hardware
> > in each system would help a lot but I'm not sure that's
> > practical. I need to put together a bunch of new workstations
> > and I'm thinking some sort of server/client arrangement with
> > the only Gentoo install being on the server could be
> > appropriate.
> >
> > - Grant
>
> You may want to look at something like a config management
system.
> I'm using Puppet these days, but Gentoo support isn't spectacular.
> It would be a bit complex to have Puppet install the packages with
> the correct USE flags. However you could use Puppet to manage all
> the text files and then manage the packages somewhat manually.
Give chef a try.
It overcomes a lot of the issue puppet ran into, and of course makes
new ones all of it's won, but by and large chef is more flexible.
>
> Here's a snippet of a template for nrpe.cfg
>
> <% if processorcount.to_i >= 12 then -%>
> command[check_load]=<%= scope.lookupvar('nrpe::params::pluginsdir')
> %>/check_load -w 35,25,25 -c 35,25,25
> <% elsif fqdn =~ /(.*)stage|demo(.*)/ then -%>
> command[check_load]=<%= scope.lookupvar('nrpe::params::pluginsdir')
> %>/check_load -w 10,10,10 -c 10,10,10
> <% else -%>
> command[check_load]=<%= scope.lookupvar('nrpe::params::pluginsdir')
> %>/check_load -w 10,7,5 -c 10,7,5
> <% end -%>
>
> If you were managing a make.conf you could set -j<%=
> processorcount*2 %> or whatever as well as pass in your own
> settings etc. Once you have things working it's pretty good at
> keeping your servers in sync and doing minor customization per
> server based on OS, hardware, IP, hostname, etc.
>
> kashani
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-07-07 20:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 22:14 [gentoo-user] Managing multiple Gentoo systems Grant
2011-07-03 0:32 ` Dale
2011-07-03 0:36 ` Alex Schuster
2011-07-03 10:09 ` Stroller
2011-07-06 19:46 ` Grant
2011-07-03 16:30 ` Roman Zilka
2011-07-03 20:46 ` Simon
2011-07-03 22:15 ` Neil Bothwick
2011-07-04 20:39 ` [gentoo-user] " Nicolas Sebrecht
2011-07-06 19:35 ` Grant
2011-07-07 9:31 ` Nicolas Sebrecht
2011-07-07 16:14 ` Grant
2011-07-08 19:03 ` Grant
2011-07-08 19:36 ` James Wall
2011-07-11 23:39 ` Grant
2011-07-12 2:45 ` James Wall
2011-07-12 3:30 ` Dale
2011-07-12 18:23 ` Grant
2011-07-12 22:48 ` Joshua Murphy
2011-07-13 19:38 ` Grant
2011-07-13 20:51 ` Bill Longman
2011-07-14 21:39 ` Mick
2011-07-07 18:23 ` [gentoo-user] " kashani
2011-07-07 20:37 ` Alan McKinnon [this message]
2011-07-07 21:01 ` kashani
2011-07-07 21:23 ` Alan McKinnon
2011-07-11 15:20 ` [gentoo-user] " James
2011-07-11 23:45 ` Grant
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=2206705.m0niYJH5nW@nazgul \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=kashani-list@badapple.net \
/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