<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 20, 2016 at 9:28 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"><span class="">> 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, having real<br>
> info on the network usage/errors will give us insight to actually determine<br>
> what's the issue, and thus, what's the best solution.<br>
><br>
> @infra what do you think?<br>
><br>
<br>
</span>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>
<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br></div><div>I think we should prioritize mirroring the GIT (not gerrit) repos to PHX, this will help:</div><div><ol><li>Speed up all post merge jobs and reduce potential of errors from git clone (they will be in the same network)</li><li>Reduce load (?) from the gerrit server and perhaps reduce errors of the per patch jobs that will still run from <a href="http://gerrit.ovirt.org">gerrit.ovirt.org</a> (AMAZON)</li><li>A longer goal will be either to migrate the gerrit server to PHX or to find away to properly mirror the gerrit server (but then i fear there might be race/problem as mentioned)</li></ol></div><div> </div><div>We have an open ticket on that which was blocked due to not wanting to clone any private git repos as well, we need to look into that again.</div><div><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">
<br>
--<br>
Barak Korren<br>
<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a><br>
RHEV-CI Team<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org">Infra@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
<br>
<br>
</div></div></blockquote></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>