public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wendall Cada <wendallc@83864.com>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Best practices in managing large server groups
Date: Tue, 22 May 2007 10:23:47 -0700	[thread overview]
Message-ID: <1179854627.4647.13.camel@localhost> (raw)
In-Reply-To: <4653203B.5020700@spamcop.net>

[-- Attachment #1: Type: text/plain, Size: 2774 bytes --]

On Tue, 2007-05-22 at 11:54 -0500, Charles Duffy wrote:
> 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).
> 
I very much agree with his assessment here. This is what I do for binary
distribution to desktop systems. It is very effective. I have played
with Catalyst quite a bit, but agree that catalyst-2 is much more well
suited for this.

I use also use the method described here: http://m8y.org/gentoosync.txt
to filter the portage tree. It makes for faster sync times, but
primarily, it makes me take a look at any additions or changes to the
tree. I've caught potential problems with updates by simply keeping a
very clean tree, which is important on the build server.

I surprises me how little work has gone into the binary support in
portage with the sheer number of devs around here who use the features.
I asked over three years ago about some specific bugs, and was assured
that they would be fixed soon. I don't think there has been a single
significant change in that time. Would be nice if -g/G was fixed. Here
is the method I use for using -k/K:

For package/*.tbz2 format:
#!/bin/bash
cd /usr/portage/packages/All/
all=`emerge -p $@ | grep "\[ebuild " | sed -e "s/\[ebuild[^]]*] //" | /
awk '{print $1}'`
for pkg in ${all}
do
    `wget -nc http://binhost.tld/portage/packages/${pkg}.tbz2`
done

For *.tbz2 format:
#!/bin/bash
cd /usr/portage/packages/All/
all=`emerge $@ -p | grep "\[ebuild " | sed -e "s/\[ebuild[^]]*] //" / |
sed -e "s/.*\///g" | awk '{print $1}'`
for pkg in ${all}
do
    `wget -nc http://binhost.tld/packages/All/${pkg}.tbz2`
done


Maybe someday, I'll turn it into a proper script, but for now, this
works.

Wendall

-- 
Only wimps use tape backup: _real_ men just upload their important stuff
on ftp, and let the rest of the world mirror it ;)
        -- Linus Torvalds

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-22 17:26 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
2007-05-22 17:23     ` Wendall Cada [this message]
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=1179854627.4647.13.camel@localhost \
    --to=wendallc@83864.com \
    --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