public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: Charles Duffy <cduffy@spamcop.net>
To: Ramon van Alteren <ramon@vanalteren.nl>
Cc: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Best practices in managing large server groups
Date: Tue, 22 May 2007 11:54:19 -0500	[thread overview]
Message-ID: <4653203B.5020700@spamcop.net> (raw)
In-Reply-To: <4652270A.7020906@vanalteren.nl>

Thank you for your advice. It's good to hear that someone else is in a 
similar scenario.

The only thing that's going to be a hard sell around here is Catalyst -- 
our senior sysadmin (who is a considerably more seasoned Gentoo user 
than myself) has taken the position that using Catalyst is unnecessary 
and that emerge (targeting a chroot, with appropriate FEATURES set to 
generate binary packages) should be adequate. He's not immovable on such 
things -- but I'll need to have a very solid understanding of the 
benefits of using Catalyst before arguing any case to the contrary. 
(I've also contacted the author of gentoo-buildhoster to find out why he 
abandoned it, what he's using in its place, and whether he believes the 
project to be worth picking up; if he believes catalyst-2 to be more 
suitable for his use cases, understanding the reasoning behind that 
decision may provide some powerful arguments).

Much of your other advice (ie. quickstart) is completely in line with 
our preexisting plans; thanks again for answering. (As for some of the 
items you're curious about -- such as our staff-to-server ratio -- I'm 
not entirely comfortable discussing all of that on an archived list; 
perhaps on IRC).
-- 
gentoo-server@gentoo.org mailing list



  parent reply	other threads:[~2007-05-22 16:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-20 18:29 [gentoo-server] Best practices in managing large server groups Charles Duffy
2007-05-20 20:20 ` Nicolas MASSE
2007-05-20 20:34   ` Charles Duffy
2007-05-20 21:25 ` Ramon van Alteren
2007-05-21  9:04   ` Ronan Mullally
2007-05-21 13:44     ` Thilo Bangert
2007-05-21 14:30       ` Ronan Mullally
2007-05-21 14:36         ` Arturo 'Buanzo' Busleiman
2007-05-21 14:53           ` Ronan Mullally
2007-05-21 15:01             ` Arturo 'Buanzo' Busleiman
2007-05-21 15:28               ` Christian Bricart
2007-05-21 15:54                 ` Arturo 'Buanzo' Busleiman
2007-05-22  4:19             ` Justin Cataldo
2007-05-22  4:59             ` Brian Kroth
2007-05-21 15:10     ` Karl Holz
2007-05-21 15:51       ` Ronan Mullally
2007-05-21 16:27         ` Ryan Gibbons
2007-05-21 17:29           ` Ronan Mullally
2007-05-21 17:35             ` Petteri Räty
2007-05-21 17:46               ` Ronan Mullally
2007-05-21 17:47             ` José Costa
2007-05-21 17:54               ` José Costa
2007-05-21 22:58           ` Karl Holz
2007-05-21 23:11 ` Ramon van Alteren
2007-05-22  5:10   ` Brian Kroth
2007-05-22 16:54   ` Charles Duffy [this message]
2007-05-22 17:23     ` Wendall Cada
2007-05-22 21:06       ` [gentoo-server] " Charles Duffy
2007-05-23  1:33         ` Wendall Cada
2007-05-23  7:37     ` [gentoo-server] " Ramon van Alteren
2007-05-23 12:28       ` Andrew Gaffney
2007-05-23 13:03         ` Ramon van Alteren
2007-05-23 13:46           ` Andrew Gaffney
2007-05-26  9:53       ` Thilo Bangert
2007-05-22 12:58 ` Tomasz Szymczak

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=4653203B.5020700@spamcop.net \
    --to=cduffy@spamcop.net \
    --cc=gentoo-server@lists.gentoo.org \
    --cc=ramon@vanalteren.nl \
    /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