<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 30 October 2015 at 23:59, Matt Riedemann <span dir="ltr"><<a href="mailto:mriedem@linux.vnet.ibm.com" target="_blank">mriedem@linux.vnet.ibm.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=""><br>
<br>
On 10/30/2015 7:41 AM, Armando M. wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
<br>
On 30 October 2015 at 18:41, Francesco Santoro<br></span><div><div class="h5">
<<a href="mailto:francesco.santoro@6wind.com" target="_blank">francesco.santoro@6wind.com</a> <mailto:<a href="mailto:francesco.santoro@6wind.com" target="_blank">francesco.santoro@6wind.com</a>>> wrote:<br>
<br>
<br>
Hi Armando,<br>
thanks for you answer.<br>
<br>
We actually just want approval for posting non voting comments to<br>
neutron.<br>
As you said we don't have a significant history on Gerrit because,<br>
after some successful tests, we stopped posting comments on neutron<br>
(and nova) waiting for core maintainers approval.<br>
Our current CI activity is obviously not long enough to request<br>
voting rights.<br>
<br>
We are still commenting back to Gerrit on ci-devstack but there is<br>
no big activity on this project.<br>
Since our idea (for future) is to obtain voting rights we need to<br>
post comments to have a stronger Gerrit activity and to let you<br>
evaluate the stability of our CI.<br>
<br>
Do you suggest to keep posting on ci-devstack or can we enable<br>
comments to neutron as well?<br>
<br>
<br>
I would be ok to have this voting for now.<br>
<br>
Having said that, Mike (cc-ed here) will be working closely with the<br>
Neutron team to re-align/improve Neutron 3rd party CI support, so stay<br>
tuned for progresses on this front.<br>
<br>
Cheers,<br>
Armando<br>
<br>
<br>
Regards,<br>
Francesco<br>
On Fri, Oct 30, 2015 at 1:17 AM, Armando M. <<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a><br></div></div><span class="">
<mailto:<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>>> wrote:<br>
<br>
<br>
<br>
On 30 October 2015 at 02:49, Matt Riedemann<br></span>
<<a href="mailto:mriedem@linux.vnet.ibm.com" target="_blank">mriedem@linux.vnet.ibm.com</a> <mailto:<a href="mailto:mriedem@linux.vnet.ibm.com" target="_blank">mriedem@linux.vnet.ibm.com</a>>><div><div class="h5"><br>
wrote:<br>
<br>
<br>
<br>
On 10/29/2015 12:13 PM, Francesco Santoro wrote:<br>
<br>
Dear Infra team,<br>
<br>
According to the requirements specified in [1] posting<br>
comments on<br>
patches needs approval from core maintainers of projects.<br>
<br>
Here at 6WIND we deployed and successfully tested [2]<br>
(using ci-sandbox<br>
project) our third party CI system [4] following all the<br>
steps defined<br>
in [1].<br>
We also run our CI on nova (and neutron) patches without<br>
posting<br>
comments just to test a bigger jobs load.<br>
Example artifacts are available at [3]<br>
<br>
For this reason we would like to get your official<br>
approval for posting<br>
non voting comments to both nova and neutron.<br>
<br>
<br>
The CI hasn't been doing this long enough [1] to really see how<br>
reliable it is, but it's been promising so far.<br>
<br>
<br>
[1]<br>
<a href="https://review.openstack.org/#/q/reviewer:%226WIND+Networking+CI+%253Copenstack-networking-ci%25406wind.com%253E%22+project:openstack/neutron,n,z" rel="noreferrer" target="_blank">https://review.openstack.org/#/q/reviewer:%226WIND+Networking+CI+%253Copenstack-networking-ci%25406wind.com%253E%22+project:openstack/neutron,n,z</a><br>
<br>
<br>
<br>
Kind regards,<br>
Francesco<br>
<br>
[1]<br>
<a href="http://docs.openstack.org/infra/system-config/third_party.html#requirements" rel="noreferrer" target="_blank">http://docs.openstack.org/infra/system-config/third_party.html#requirements</a><br>
[2] <a href="https://review.openstack.org/#/c/238139/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/238139/</a> or<br>
<a href="https://review.openstack.org/#/c/226956/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/226956/</a><br>
[3]<br>
<a href="http://openstack-ci.6wind.com/networking-6wind-ci/230537" rel="noreferrer" target="_blank">http://openstack-ci.6wind.com/networking-6wind-ci/230537</a> or<br>
<a href="http://openstack-ci.6wind.com/networking-6wind-ci/202098" rel="noreferrer" target="_blank">http://openstack-ci.6wind.com/networking-6wind-ci/202098</a><br>
[4]<br>
<a href="https://wiki.openstack.org/wiki/ThirdPartySystems/6WIND_Networking_CI" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/ThirdPartySystems/6WIND_Networking_CI</a><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br></div></div>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><span class=""><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
Do you have any code in nova that's specific to your<br>
configuration?<br>
<br>
--<br>
<br>
Thanks,<br>
<br>
Matt Riedemann<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br></span>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a> <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><span class=""><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br></span>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><span class=""><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br></span>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><span class=""><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</span></blockquote>
<br>
Personally I wouldn't want the noise in nova from a neutron 3rd party vendor CI until there is code in nova (whatever the monkey patch is). Things get a bit tricky when one project has a lot of out of tree stuff (neutron stadium) and another doesn't support that (nova), and the CI is caught in the middle.<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>Makes sense, but I wonder why nova chose the path of an implicit hook mechanism.</div><div><br></div><div>What was the purpose for it, if not to allow extensions to plug in without the need of being part of the nova tree? I might be missing something.</div><div><br></div><div>A.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
<br>
-- <br>
<br>
Thanks,<br>
<br>
Matt Riedemann<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>