<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 1, 2016 at 4:39 AM, Fox, Kevin M <span dir="ltr"><<a href="mailto:Kevin.Fox@pnnl.gov" target="_blank">Kevin.Fox@pnnl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":vp" class="a3s aXjCH m158b6f9e490c069e">So, longer term, I'd really like to see a set of smaller pieces of gate'ness that co-check each other.<br></div></blockquote><div><br></div><div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;display:inline">yes this is neccessary.</div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":vp" class="a3s aXjCH m158b6f9e490c069e">
<br>
one gate that periodically checks that kolla:trunk builds (nightly?) sans modification. As the containers themselves depend on a lot of packages/repositories outside of kolla's control and therefore can break at any time. These would be ran against the kolla-ansible/kolla-kubernetes trunk gate checks. showing bugs in the potentially changing containers against known good deployment tests.<br></div></blockquote><div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;display:inline"><br></div></div><div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;display:inline">Agree. periodically checks need check the stable branch too, since they are not update too much.</div></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":vp" class="a3s aXjCH m158b6f9e490c069e">
<br>
A similar periodic check should be done for kolla-ansible/kolla-kubetes gates to ensure things like a new version of kubeadm getting released doesn't break things, and cause the other gate checks to produce misleading failures.<br></div></blockquote><div><br></div><div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">On master branch, we can depend on zuul's cross project test feature. Now kolla project run kolla-ansible deployment in its gate for every patch set. Hope we can add kolla-k8s too.</div></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":vp" class="a3s aXjCH m158b6f9e490c069e">
<br>
The results of the periodic gates, should be cached somewhere and used as input to the kolla-ansible and kolla-kubernetes gates used to check incoming reviews. You can then rely more on breakages in kolla-ansible/kolla-kubernetes gate checks being actually caused by the patches incoming, and not some outside influence.<br></div></blockquote><div><br></div><div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">inc0 is trying to set up docker registry in openstack infra. when it is done, we can speed up the deployment gate in kolla-ansible/kolla-kubernetes.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">another workaround inc0 proposed is publishing /var/lib/registry to <a href="http://tarballs.openstack.org">tarballs.openstack.org</a>, which can be download by kolla-ansible/kolla-k8s.</div></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":vp" class="a3s aXjCH m158b6f9e490c069e">
<br>
This should make it much quicker to iterate though issues.<br>
<br>
Thanks,<br>
Kevin</div></blockquote></div><br><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><span style="font-size:13px;border-collapse:collapse"><font face="monospace, monospace">Regards,</font></span></div><div><span style="font-size:13px;border-collapse:collapse"><font face="monospace, monospace">Jeffrey Zhang</font></span></div><div><span style="font-family:monospace,monospace;font-size:12.8px">Blog: </span><a href="http://xcodest.me/" style="font-family:monospace,monospace;font-size:12.8px" target="_blank">http://xcodest.me</a><font face="monospace, monospace"><br></font></div></div></div></div></div></div></div></div></div>
</div></div>