<html><body>
<p><tt><font size="2">Jay Pipes <jaypipes@gmail.com> wrote on 01/17/2014 04:32:55 PM:<br>
<br>
> From: Jay Pipes <jaypipes@gmail.com></font></tt><br>
<tt><font size="2">> To: "OpenStack Development Mailing List (not for usage questions)" <br>
> <openstack-dev@lists.openstack.org>, </font></tt><br>
<tt><font size="2">> Date: 01/17/2014 04:37 PM</font></tt><br>
<tt><font size="2">> Subject: Re: [openstack-dev] [neutron] [third-party-testing] Sharing<br>
> information</font></tt><br>
<tt><font size="2">> <br>
> On Thu, 2014-01-16 at 15:37 +0000, Sullivan, Jon Paul wrote:<br>
> > > From: Jay Pipes [<a href="mailto:jaypipes@gmail.com">mailto:jaypipes@gmail.com</a>]<br>
> > > On Thu, 2014-01-16 at 10:39 +0000, Sullivan, Jon Paul wrote:<br>
> > > > > From: Kyle Mestery [<a href="mailto:mestery@siliconloons.com">mailto:mestery@siliconloons.com</a>]<br>
> > > > > <br>
> > > > > FYI, here [1] are the meeting logs from today’s meeting.<br>
> > > > ><br>
> > > > > A couple of things have become apparent here:<br>
> > > > ><br>
> > > > > 1. No one has a working Neutron 3rd party testing rig yet which is<br>
> > > > > voting<br>
> > > > > consistently. If I’ve missed something, please, someone correct<br>
> > > me.<br>
> > > > > 2. People are still hung on issues around Jenkins/gerrit<br>
> > > integration.<br>
> > > ><br>
> > > > This issue can be very easily resolved if people were to use Jenkins<br>
> > > Job Builder [2] for the creation of their Jenkins testing jobs. This<br>
> > > would allow the reuse of simple macros already in existence to guarantee<br>
> > > correct configuration of Jenkins jobs at 3rd party sites. This would<br>
> > > also allow simple reuse of the code used by the infra team to create the<br>
> > > openstack review and gate jobs, ensuring 3rd party testers can generate<br>
> > > the correct code from the gerrit change and also publish results back in<br>
> > > a standard way.<br>
> > > ><br>
> > > > I can't recommend Jenkins Job Builder highly enough if you use<br>
> > > Jenkins.<br>
> > > ><br>
> > > > [2] <a href="https://github.com/openstack-infra/jenkins-job-builder">https://github.com/openstack-infra/jenkins-job-builder</a><br>
> > > <br>
> > > ++ It's a life-saver. We used it heavily in AT&T with our<br>
> > > Gerrit/Jenkins/Zuul CI system.<br>
> > > <br>
> > > -jay<br>
> > <br>
> > It seems to me that shared JJB macros could be the most concise <br>
> and simple way<br>
> > of describing 3rd party testing integration requirements.<br>
> > <br>
> > So the follow-on questions are:<br>
> > 1. Can the 3rd party testing blueprint enforce, or at least link to,<br>
> > use of specific JJB macros for integration to the openstack gerrit?<br>
> > 1a. Where should shared JJB code be stored?<br>
> <br>
> Well, technically, this already exists. The openstack-infra/config<br>
> project already has pretty much everything a 3rd party would ever need<br>
> to setup an OpenStack environment, execute Tempest (or other) tests<br>
> against the environment, save and publish artifacts, and send<br>
> notifications of test results upstream.<br>
> <br>
> > 2. Is it appropriate for 3rd party testers to share their tests as<br>
> > JJB code, if they are willing?<br>
> > 2a. Would this live in the same location as (1a)?<br>
> <br>
> Why would 3rd party testers be using anything other than Tempest for<br>
> integration testing? Put another way... if a 3rd party *is* using<br>
> something other than Tempest, why not put it in Tempest :)<br>
> <br>
> > For those unfamiliar with JJB, here is a little example of what <br>
> you might do:<br>
> > <br>
> > Example of (untested) JJB macro describing how to configure Jenkins to<br>
> > trigger from gerrit:<br>
> > <snip><br>
> <br>
> As much as JJB is total awesomesauce -- as it prevents people needing to<br>
> manually update Jenkins job config.xml files -- any 3rd party that is<br>
> attempting to put together a test environment/platform for which you<br>
> intend to interact with the upstream CI system should go check out<br>
> devstack-gate [1], read the scripts, and grok it.<br>
> <br>
> I'm working on some instructions to assist admins in 3rd party testing<br>
> labs in setting all of their platform up using the upstream tools like<br>
> devstack-gate and JJB, and this documentation should be done around<br>
> middle of next week. I'll post to the ML with links to that<br>
> documentation when it's done.<br>
> </font></tt><br>
<br>
<tt><font size="2">That would be great. Thanks. Please note that Icehouse-2 is the deadline for Neutron 3rd party test setups to be operational.</font></tt><br>
<tt><font size="2"><br>
> Best,<br>
> -jay<br>
> <br>
> [1] <a href="https://github.com/openstack-infra/devstack-gate">https://github.com/openstack-infra/devstack-gate</a><br>
> <br>
> <br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> OpenStack-dev@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></tt></body></html>