Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: infrastructure-dev@apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Wed, 6 Jun 2012 13:47:25 +0300
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
Subject: Re: [2/2] git commit: 8817b8b - site/htdocs/index.html
Message-ID: <20120606104725.GA5686@tarsus.local2>
References: <20120605180145.79674FFEA@tyr.zones.apache.org>
 <20120605195107.GI3531@lp-shahaf.local>
 <1338934958.59763.YahooMailNeo@web160901.mail.bf1.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1338934958.59763.YahooMailNeo@web160901.mail.bf1.yahoo.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

[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).

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.