Open Stack

Hi Kurt,

We (Arista) were one of the early adapters of the CI systems. We built our
system based upon the Neutron requirements as of late last year/early this
year. Our CI has been up and operational since January of this year. This
is before (or in parallel to Jay Pipes effort of Zuul based CIs).

We have invested a lot of effort in getting this done. In fact, I helped
many vendors setting up their Jenkin master/slaves, etc.
Additionally, we put an effort in coming up with a patch to support
"recheck" matching - as it was not supported in Gerritt Plugin.
Please see our wiki [1] which has a link to the Google doc describing the
recheck patch.

At the time the requirement was to support "recheck no bug/bug#". Our
system is built to support this syntax.
The current Neutron Third party test systems are described in [2] and if
you look at the requirements described in [3], it states that a single
recheck should trigger all test systems.

Having said that, I understand the rationale of your argument. on this
thread, and actually agree with your point.
I have seen similar comments on various ML threads.

My suggestion is that this should be done in a coordinated manner so that
everybody understands the requirements, rather than simply throwing it on
the mailing list and assuming it is accepted by everybody. This is what
leads to the confusion. Some people will take it as a marching orders,
others may miss the thread and completely miss the communication.

Kyle Mestry (Neutron PTL) and Edgar Magana (Neutron Core) are proposing a
session at Kilo Summit in Paris to cover third party CI systems.
I would propose that you please coordinate with them and get your point of
view incorporated into this session. I have copied them both on this email
so that they can share their wisdom on the subject as well.

Thanks for all the good work by you and the infra team - making things
easier for us.

regards..
-Sukhdev

[1] https://wiki.openstack.org/wiki/Arista-third-party-testing
[2] https://wiki.openstack.org/wiki/NeutronThirdPartyTesting
[3] http://ci.openstack.org/third_party.html




On Wed, Sep 3, 2014 at 4:59 AM, Kurt Taylor <krtaylor at us.ibm.com> wrote:

> Weidong Shao <weidongshao at gmail.com> wrote on 09/02/2014 09:35:30 PM:
>
> > From:
> >
> > Weidong Shao <weidongshao at gmail.com>
> >
>
> > Subject:
> >
> > [OpenStack-Infra] VMWare NSX CI - recheck info
>
> >
> > Hi,
> >
> > I have a CL (https://review.openstack.org/#/c/116094/) that fails in
> > VMWare NSX CI. I could not figure out the proper way to do a recheck
> > on that.  On the error log page, there is a link to the team's wiki,
> > from which this instruction is given:
> >     "To issue a recheck, submit a comment with the following text:
> > vmware-recheck"
> >
> > I did that but it did not trigger a recheck.
> > Could someone help me on this?
>
> As of today, all systems, project and third-party, should restart
> test jobs with just "recheck" comment. Including information after
> "recheck" doesn't break anything upstream.
>
> See: https://review.openstack.org/#/c/108724/  and
> the discussion at: https://review.openstack.org/#/c/100133/  and
> https://review.openstack.org/#/c/109565/
>
> Since most third-party systems are actually supporting some form of
> "recheck-<system name>" I am proposing a new change to the comment
> syntax to accommodate the need for triggering specific third-party
> system rechecks.
>
> Kurt Taylor (krtaylor)
>
>
> >
> > A related note on NSX CI:
> >
> > Apparently, the VMWare CI does not follow the guideline from http://
> > ci.openstack.org/third_party.html to include contacts, recheck
> > instruction etc. Some other CIs provide better messages on failure. e.g,
> >
> > A10
> > Contact: a10-openstack-ci at a10networks.com
> > Additional information: https://wiki.openstack.org/wiki/
> > ThirdPartySystems/A10_Networks_CI
> > Or from RYU CI
> > "Build failed. Leave a comment with 'recheck-ryu' to rerun a check.
> > ('recheck' will be ignored.)"
> > Could someone from the NSX/Openstack team make the necessary changes?
> >
> > Thanks,
> > Wei_______________________________________________
>
>
> _______________________________________________
> OpenStack-Infra mailing list
> OpenStack-Infra at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140903/388ab19b/attachment.html>