Re: [gentoo-dev] Proposal: patches.gentoo.org

[Chris Gianelloni <wolf31o2@gentoo.org>]

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

On Tue, 2004-10-12 at 16:57 -0400, Jeffrey Forman wrote:
> (1) A single point of distribution is just a bad idea imho. Imagine a
> critical patch that MUST GET OUT IMMEDIATELY (differing opinions of
> 'must get out now' apply). You get thousands, even tens of thousands of
> people hitting patches.g.o and you can wave goodbye to that machine.

Except for the idea would be to use a few machines as
"patches.gentoo.org" not a single machine.  I think you missed that
point in my posting.

> (2) The distribution network is there for a reason. Let me be the first
> one to admit that it isnt perfect. Once you place something on
> /space/distfiles-local, it hits two machines before it hits the world,
> taking between an hour and four hours (theoretically) to go public.
> Latency is involved in whichever solution we can propose, short of
> giving everyone write access to our master mirror.

Remember that we're talking patch files and only as a temporary store
until the files hit the main mirror infrastructure.

> (3) Whether we use distfiles mirrors, or the rsync rotation to
> distribute patches, this has not been decided upon. The idea was
> broached for a couple minutes earlier today but not even a preliminary
> solution was conjured.

Actually, we had a decent idea, which Kurt then asked someone to write
up, so I did.  The idea would be to use the rsync servers, which was the
reason I originally put information about something like /space/patches-
local as we do *not* want it to mirror distfiles, only the critical
patches that we say *have to get out quickly* and we don't want to wait
for the normal distfiles mirroring to take place.  Anything other than
this pretty much makes the whole system useless and adds a *ton* over
extra overhead that we were never discussing.

> Infra has complete control over the rsync.g.o rotation, so coming up
> with ways to improve it that way can be worked out. I am sure this will
> be a topic during the next dev meeting, if not listed, I will definitely
> mention it.

That's what this was supposed to be... ;]

> On Tue, 2004-10-12 at 16:10, Nicholas Jones wrote:
> > And rewritten for clarity:
> > 
> > 1. developer creates an ebuild which needs a patch
> > 2. SRC_URI="mirror://gentoo/patchname http://patches.gentoo.org/patchname"
> > 3. Uploads files to dev.gentoo.org:/space/distfiles-local
> > 4. developer commits ebuild(s) to cvs
> > 
> > Infra notes:
> > 
> > Immediate availability via the "secondary" host while the primary
> > host has yet to receive the files. Once the file is present on the
> > primary mirrors it may be deleted from the secondary.
> > 
> > Ensuring that the patch host is not the primary mirror will be a
> > concern, but a script can be devised to ensure duplication of
> > the patchname and that a primary mirror is listed prior to it.
> > 
> > The host for the files should not be accessable for any reason
> > except direct filename downloads. No listings (to discourage
> > setting it as a mirroring source).
> > 
-- 
Chris Gianelloni
Release Engineering - Operational/QA Manager
Games - Developer
Gentoo Linux

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