| 1 |
On Thursday 07 July 2011 11:23:15 kashani did opine thusly: |
| 2 |
> On 7/2/2011 3:14 PM, Grant wrote: |
| 3 |
> > After a frustrating experience with a Linksys WRT54GL, I've |
| 4 |
> > decided to stick with Gentoo routers. This increases the |
| 5 |
> > number of Gentoo systems I'm responsible for and they're |
| 6 |
> > nearing double-digits. What can be done to make the management |
| 7 |
> > of multiple Gentoo systems easier? I think identical hardware |
| 8 |
> > in each system would help a lot but I'm not sure that's |
| 9 |
> > practical. I need to put together a bunch of new workstations |
| 10 |
> > and I'm thinking some sort of server/client arrangement with |
| 11 |
> > the only Gentoo install being on the server could be |
| 12 |
> > appropriate. |
| 13 |
> > |
| 14 |
> > - Grant |
| 15 |
> |
| 16 |
> You may want to look at something like a config management |
| 17 |
system. |
| 18 |
> I'm using Puppet these days, but Gentoo support isn't spectacular. |
| 19 |
> It would be a bit complex to have Puppet install the packages with |
| 20 |
> the correct USE flags. However you could use Puppet to manage all |
| 21 |
> the text files and then manage the packages somewhat manually. |
| 22 |
|
| 23 |
Give chef a try. |
| 24 |
|
| 25 |
It overcomes a lot of the issue puppet ran into, and of course makes |
| 26 |
new ones all of it's won, but by and large chef is more flexible. |
| 27 |
|
| 28 |
|
| 29 |
> |
| 30 |
> Here's a snippet of a template for nrpe.cfg |
| 31 |
> |
| 32 |
> <% if processorcount.to_i >= 12 then -%> |
| 33 |
> command[check_load]=<%= scope.lookupvar('nrpe::params::pluginsdir') |
| 34 |
> %>/check_load -w 35,25,25 -c 35,25,25 |
| 35 |
> <% elsif fqdn =~ /(.*)stage|demo(.*)/ then -%> |
| 36 |
> command[check_load]=<%= scope.lookupvar('nrpe::params::pluginsdir') |
| 37 |
> %>/check_load -w 10,10,10 -c 10,10,10 |
| 38 |
> <% else -%> |
| 39 |
> command[check_load]=<%= scope.lookupvar('nrpe::params::pluginsdir') |
| 40 |
> %>/check_load -w 10,7,5 -c 10,7,5 |
| 41 |
> <% end -%> |
| 42 |
> |
| 43 |
> If you were managing a make.conf you could set -j<%= |
| 44 |
> processorcount*2 %> or whatever as well as pass in your own |
| 45 |
> settings etc. Once you have things working it's pretty good at |
| 46 |
> keeping your servers in sync and doing minor customization per |
| 47 |
> server based on OS, hardware, IP, hostname, etc. |
| 48 |
> |
| 49 |
> kashani |
| 50 |
-- |
| 51 |
alan dot mckinnon at gmail dot com |
Archives