www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Schaefer <joe_schae...@yahoo.com>
Subject Re: [2/2] git commit: 8817b8b - site/htdocs/index.html
Date Wed, 06 Jun 2012 23:16:39 GMT
----- Original Message -----

> From: Paul Davis <paul.joseph.davis@gmail.com>
> To: infrastructure-dev@apache.org; Joe Schaefer <joe_schaefer@yahoo.com>
> Cc: Daniel Shahaf <d.s@daniel.shahaf.name>; "rubys@apache.org" <rubys@apache.org>
> Sent: Wednesday, June 6, 2012 7:13 PM
> Subject: Re: [2/2] git commit: 8817b8b - site/htdocs/index.html
> 
>T his should be a lot simpler than pubsub. If we really want EU mirrors
> then we can just add a post-receive hook that'll mirror the updates
> over. There's a special git push --mirror thing that'll take care of
> the odds and ends for us.
> 
> The bigger question is whether we even need it at all. Given that Git
> is distributed the interaction with the server is generally less
> frequent than SVN. I'm also not sure about SVN's protocol, but Git
> does push/pull in a single HTTP request which means that latency isn't
> a big factor. And IIUC SVN writes from the EU are still proxied
> through to the US anyway.
> 
> The other thing to consider is that we already have mirrors on GitHub.
> I'm not sure how much (if at all) they mirror over to the EU but I've
> never seen Europeans complain about it. So perhaps that's good enough
> for our needs?

Yes I tend to lean toward YAGNI regarding geo-ns service for git.  The only
complaints I've seen so far that were performance related were client-side
bugs in git.

> 
> 
> On Wed, Jun 6, 2012 at 5:52 AM, Joe Schaefer <joe_schaefer@yahoo.com> 
> wrote:
>> 
>> 
>> 
>> 
>>  ----- Original Message -----
>>>  From: Daniel Shahaf <d.s@daniel.shahaf.name>
>>>  To: Joe Schaefer <joe_schaefer@yahoo.com>
>>>  Cc: "rubys@apache.org" <rubys@apache.org>; 
> infrastructure-dev@apache.org
>>>  Sent: Wednesday, June 6, 2012 6:47 AM
>>>  Subject: Re: [2/2] git commit: 8817b8b - site/htdocs/index.html
>>> 
>>>  [switching list with joe's ok]
>>> 
>>>  I don't know the git http protocol well enough.  So you're 
> saying that
>>>  pushes can be made to always happen on the .us mirror first by standard
>>>  mod_proxy application?  And for pulls (.us -> .eu), I would prefer 
> they
>>>  happen even if no one pulls from .eu (think projects with large
>>>  committership entirely in .us).
>> 
>>  Good point Daniel.  I guess we really will need a gitpubsub like
>>  feature to support this properly ;-(.
>> 
>>> 
>>>  Joe Schaefer wrote on Tue, Jun 05, 2012 at 15:22:38 -0700:
>>>>   If we need to geo-ns distribute our git service
>>>>   across the two hosts, we simply need to write
>>>>   a little "filter" httpd module that will trigger a
>>>>   git pull operation based on the request url.
>>>> 
>>>>   Combining that with a standardproxy setup for
>>>>   push operations will suffice.
>>>> 
>>>>   No we haven't done this yet, because so far we
>>>>   haven't needed it- it's just a performance enhancement.
>>>>   But it won't be hard for us to add it if we need to.
>>>> 
>>>> 
>>>> 
>>>>   > How do you intend to consolidate the git services on _both_ 
> of those
>>>>   > hosts?  I am not aware that we have any support for US->EU
>>>  replication
>>>>   > in git-wip-us.
>>> 
> 

Mime
View raw message