<div dir="ltr">VMware minesweeper has filters which have been designed to cover the largest possible subset of submissions without add unnecessary load to our scarce resources for CI validation. This is probably why the analysis reveals not all patches are covered.<div>
<br></div><div>Therefore our filters exclude neutral changes such as those in README.rst (they're unlikely to crash neutron are they?), or changes in wsgi.py. The latter is because the wsgi framework is shared with all plugins, and when it breaks the NSX plugin it's very likely upstream tests will break too.</div>
<div><br></div><div>I think the areas which are important to cover are:</div><div>- neutron/agents/.* (or at least the agents you use)</div><div>- neutron/openstack/common/.*</div><div>- neutron/notifiers/.* (if your drivers report vif plugging events to nova)</div>
<div>- neutron/db/.*</div><div>- neutron/services/${thepluginsyouruninyourci_eveniftheyrenotyours}</div><div>- your plugin patch</div><div><br></div><div>Salvatore</div><div><br></div><div>PS: Openstack proposal bot submission's checks have been suspended for vmware minesweeper about 2 days ago. They will resume soon.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 16 August 2014 01:02, Edgar Magana <span dir="ltr"><<a href="mailto:edgar.magana@workday.com" target="_blank">edgar.magana@workday.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>Ivar,</div>
<div><br>
</div>
<div>Very valid point. This is why I need clarification from those CI owner.</div>
<div>I will run a new test with a basic change in the Neutron DB code. That should be covered by almost all CI systems.</div>
<div><br>
</div>
<div>Edgar</div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>Ivar Lazzaro <<a href="mailto:ivarlazzaro@gmail.com" target="_blank">ivarlazzaro@gmail.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Friday, August 15, 2014 at 3:47 PM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [neutron] [third-party] What tests are required to be run<br>
</div><div><div class="h5">
<div><br>
</div>
<div>
<div>
<div dir="ltr">Hi Edgar,
<div><br>
</div>
<div>Nice shot, to be the inquisitor is not necessarily a bad thing :)</div>
<div><br>
</div>
<div>I know some CIs are 'stuck' waiting for bugs to be fixed or certain patches to be merged, but I was wondering if it is a requirement that CIs vote *ALL* the Neutron patches. Some may have missed your call just because of their filters (see [0] section
'what changes to run against').</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Ivar.</div>
<div><br>
</div>
<div><span>[0] <a href="https://wiki.openstack.org/wiki/NeutronThirdPartyTesting" target="_blank">https://wiki.openstack.org/wiki/NeutronThirdPartyTesting</a></span></div>
<div><br>
</div>
<div> </div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Sat, Aug 16, 2014 at 12:35 AM, Edgar Magana <span dir="ltr">
<<a href="mailto:edgar.magana@workday.com" target="_blank">edgar.magana@workday.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Team,<br>
<br>
I did a quick audit on the Neutron CI. Very sad results. Only few plugins<br>
and drivers are running properly and testing all Neutron commits.<br>
I created a report here:<br>
<a href="https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Existing_Plugin" target="_blank">https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Existing_Plugin</a><br>
_and_Drivers<br>
<br>
<br>
We will discuss the actions to take on the next Neutron IRC meeting. So<br>
please, reach me out to clarify what is the status of your CI.<br>
I had two commits to quickly verify the CI reliability:<br>
<br>
<a href="https://review.openstack.org/#/c/114393/" target="_blank">https://review.openstack.org/#/c/114393/</a><br>
<br>
<a href="https://review.openstack.org/#/c/40296/" target="_blank">https://review.openstack.org/#/c/40296/</a><br>
<br>
<br>
I would expect all plugins and drivers passing on the first one and<br>
failing for the second but I got so many surprises.<br>
<br>
Neutron code quality and reliability is a top priority, if you ignore this<br>
report that plugin/driver will be candidate to be remove from Neutron tree.<br>
<br>
Cheers,<br>
<br>
Edgar<br>
<br>
P.s. I hate to be the inquisitor hereŠ but someone has to do the dirty job!<br>
<div>
<div><br>
<br>
On 8/14/14, 8:30 AM, "Kyle Mestery" <<a href="mailto:mestery@mestery.com" target="_blank">mestery@mestery.com</a>> wrote:<br>
<br>
>Folks, I'm not sure if all CI accounts are running sufficient tests.<br>
>Per the requirements wiki page here [1], everyone needs to be running<br>
>more than just Tempest API tests, which I still see most neutron<br>
>third-party CI setups doing. I'd like to ask everyone who operates a<br>
>third-party CI account for Neutron to please look at the link below<br>
>and make sure you are running appropriate tests. If you have<br>
>questions, the weekly third-party meeting [2] is a great place to ask<br>
>questions.<br>
><br>
>Thanks,<br>
>Kyle<br>
><br>
>[1] <a href="https://wiki.openstack.org/wiki/NeutronThirdPartyTesting" target="_blank">
https://wiki.openstack.org/wiki/NeutronThirdPartyTesting</a><br>
>[2] <a href="https://wiki.openstack.org/wiki/Meetings/ThirdParty" target="_blank">
https://wiki.openstack.org/wiki/Meetings/ThirdParty</a><br>
><br>
>_______________________________________________<br>
>OpenStack-dev mailing list<br>
><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div></div></span>
</div>
<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>