<div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 11, 2014 at 4:31 PM, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">A few weeks ago we realized one of the wrecking balls in the gate were<br>

non overlapping requirements changes, like this -<br>
<a href="https://review.openstack.org/#/c/72475/" target="_blank">https://review.openstack.org/#/c/72475/</a><br>
<br>
Regular jobs in the gate have to use the OpenStack mirror. Requirements<br>
repo doesn't, because it needs to be able to test things not in the mirror.<br>
<br>
So when a requirements job goes into the gate, everything behind it will<br>
be using the new requirements. But the mirror isn't updated until the<br>
requirements change merges.<br>
<br>
So if you make a non overlapping change like that, for 1hr (or more)<br>
everything in the wake of the requirements job gets blown up in global<br>
requirements because it can't install that from the mirror.<br>
<br>
This issue is partially synthetic, however it does raise a good issue<br>
for continuous deployed environments, because assuming atomic upgrade of<br>
2 code bases isn't a good assumption.<br>
<br>
Anyway, the point of this email is we really shouldn't be approving<br>
requirements changes that are disjoint upgrades like that, because they<br>
basically mean they'll trigger 10 - 20 -2s of other people's patches in<br>
the gate.<br></blockquote><div><br></div><div><div class="gmail_default" style="font-size:small">Good point, Sean. I added this to the requirements project review checklist (<a href="https://wiki.openstack.org/wiki/Requirements#Review_Criteria">https://wiki.openstack.org/wiki/Requirements#Review_Criteria</a>).</div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Doug</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<span class=""><font color="#888888"><br>
        -Sean<br>
<br>
--<br>
Sean Dague<br>
Samsung Research America<br>
<a href="mailto:sean@dague.net">sean@dague.net</a> / <a href="mailto:sean.dague@samsung.com">sean.dague@samsung.com</a><br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br>
</font></span><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>