From: Nicolas MASSE <nicolas27.masse@laposte.net>
To: gentoo-server@lists.gentoo.org, Charles Duffy <cduffy@spamcop.net>
Subject: Re: [gentoo-server] Best practices in managing large server groups
Date: Sun, 20 May 2007 22:20:36 +0200 [thread overview]
Message-ID: <20070520222036.77vwf3haaswsscgw@imp.itix.fr> (raw)
In-Reply-To: <4650937E.80301@spamcop.net>
Quoting Charles Duffy <cduffy@spamcop.net>:
> [Apologies if this is a duplicate post; I tried posting this through
> GMANE yesterday without subscribing first, and it appears not to have
> gone through; likewise when I posted several hours ago today from a
> different address than the one I subscribed].
>
> All,
>
> I'm looking at replacing SuSE SLES9 with Gentoo for an enterprise
> application (for reasons of flexibility and licensing) (no, we don't
> have an enterprise application budget -- just the reliability
> requirements; yaaay, startups!). We're looking to be able to deploy and
> manage hundreds of geographically distributed servers.
>
> We have a QA department available to vet each configuration before it is
> deployed to the field. We have infrastructure for tracking the progress
> of code in svn from creation though QA to deployment; I'm anticipating
> tracking a local overlay (containing all packages we use), make.conf,
> /etc/portage/*, etc. through this system, autobuilding system images
> (either to run virtualized or on real hardware) from the contents of
> svn, building binary packages and deploying them to real hardware.
>
> I'm interested in best practices, suggested tools, and/or 3rd party
> experiences in this regard.
I have absolutely no experience with this, but during one of my
training courses, I found the following document :
- http://www.fernhilltec.com.au/~adrian/kara/kara.html
Maybe, it could give some ideas...
Nicolas.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--
gentoo-server@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-20 20:23 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 [this message]
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
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=20070520222036.77vwf3haaswsscgw@imp.itix.fr \
--to=nicolas27.masse@laposte.net \
--cc=cduffy@spamcop.net \
--cc=gentoo-server@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