<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 20, 2016 at 10:20 AM, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 20 April 2016 at 10:16, Eyal Edri <<a href="mailto:eedri@redhat.com">eedri@redhat.com</a>> wrote:<br>
><br>
><br>
> On Wed, Apr 20, 2016 at 9:28 AM, Barak Korren <<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a>> wrote:<br>
>><br>
>> > I'd try that approach first, though the mirror is a good idea that will<br>
>> > probably have to be implemented anyhow once we start adding slaves,<br>
>> > having real<br>
>> > info on the network usage/errors will give us insight to actually<br>
>> > determine<br>
>> > what's the issue, and thus, what's the best solution.<br>
>> ><br>
>> > @infra what do you think?<br>
>> ><br>
>><br>
>> The issue with mirroring is how can you make sure that you mirror fast<br>
>> enough to enable CI. Even if Gerrit can push to the mirror on patch<br>
>> submission, there will still be some time delta between the submission<br>
>> happening (and the patch event showing up in Jenins) and the mirror<br>
>> being synced. This looks like a nasty race condition.<br>
>> What the mirror essentially does is make sure that bits are copied<br>
>> from Amazom to PHX just once. I wonder if we can get the same benefit<br>
>> with a simple HTTP proxy, how proxy-able is the Git HTTP protocol?<br>
>><br>
><br>
> I think we should prioritize mirroring the GIT (not gerrit) repos to PHX,<br>
> this will help:<br>
><br>
> Speed up all post merge jobs and reduce potential of errors from git clone<br>
> (they will be in the same network)<br>
> Reduce load (?) from the gerrit server and perhaps reduce errors of the per<br>
> patch jobs that will still run from <a href="http://gerrit.ovirt.org" rel="noreferrer" target="_blank">gerrit.ovirt.org</a> (AMAZON)<br>
> A longer goal will be either to migrate the gerrit server to PHX or to find<br>
> away to properly mirror the gerrit server (but then i fear there might be<br>
> race/problem as mentioned)<br>
><br>
<br>
</div></div>Please look at my comment about possible race conditions caused by<br>
mirroring. Simple mirroring may cause more trouble then its worth. We<br>
need to consider proxying instead.<br></blockquote><div><br></div><div>I don't see how a race condition can occur with a merge commit,</div><div>Can you elaborate? </div><div> </div></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHEV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div>
</div></div>