<html><body>
<p><tt><font size="2">"Sullivan, Jon Paul" <JonPaul.Sullivan@hp.com> wrote on 01/16/2014 05:39:04 AM:<br>
<br>
> From: "Sullivan, Jon Paul" <JonPaul.Sullivan@hp.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/16/2014 05:46 AM</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>
> > -----Original Message-----<br>
> > From: Kyle Mestery [<a href="mailto:mestery@siliconloons.com">mailto:mestery@siliconloons.com</a>]<br>
> > Sent: 15 January 2014 22:53<br>
> > To: OpenStack Development Mailing List (not for usage questions)<br>
> > Subject: Re: [openstack-dev] [neutron] [third-party-testing] Sharing<br>
> > information<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 me.<br>
> > 2. People are still hung on issues around Jenkins/gerrit 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. <br>
> This would allow the reuse of simple macros already in existence to <br>
> guarantee correct configuration of Jenkins jobs at 3rd party sites. <br>
> This would also allow simple reuse of the code used by the infra <br>
> team to create the openstack review and gate jobs, ensuring 3rd <br>
> party testers can generate the correct code from the gerrit change <br>
> and also publish results back in a standard way.<br>
> <br>
> I can't recommend Jenkins Job Builder highly enough if you use Jenkins.<br>
> <br>
> [2] <a href="https://github.com/openstack-infra/jenkins-job-builder">https://github.com/openstack-infra/jenkins-job-builder</a><br>
> </font></tt><br>
<br>
<br>
<tt><font size="2">Thanks for the pointer. </font></tt><br>
<tt><font size="2">When you say we could reuse the code used by the infra team, are you referring to the yaml files and/or build scripts?</font></tt><br>
<tt><font size="2">Is there a place where we could look at the yaml configuration (and other relevant) files that they may be using?</font></tt><br>
<br>
<tt><font size="2">Thanks,</font></tt><br>
<br>
<tt><font size="2">Mohammad</font></tt><br>
<br>
<tt><font size="2"><br>
> > 3. There are issues with devstack failing, but these seem to be Neutron<br>
> > plugin specific. I’ve encouraged people to reach out on both the<br>
> > #openstack-neutron and #openstack-qa channels with questions.<br>
> > 4. There is still some confusion on what tests to run. I think this is<br>
> > likely to be plugin dependent.<br>
> > 5. There is some confusion around what version of devstack to use.<br>
> > My assumption has always been upstream master.<br>
> > <br>
> > Another general issue which I wanted to highlight here, which has been<br>
> > brought up before, is that for companies/projects proposing plugins,<br>
> > MechanismDrivers, and/or service plugins you really need someone active<br>
> > on both the mailing list as well as the IRC channels. This will help if<br>
> > your testing rig has issues, or if people need help understanding why<br>
> > your test setup is failing with their patch.<br>
> > <br>
> > So, that’s the Neutron 3rd party testing update as we near the deadline<br>
> > next week.<br>
> > <br>
> > Thanks!<br>
> > Kyle<br>
> > <br>
> > [1]<br>
> > <a href="http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2">http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2</a><br>
> > 014/networking_third_party_testing.2014-01-15-22.00.log.html<br>
> > <br>
> > On Jan 14, 2014, at 10:34 AM, Kyle Mestery <mestery@siliconloons.com><br>
> > wrote:<br>
> > <br>
> > > Given the Tempest Sprint in Montreal, I still think we should have<br>
> > > this meeting on IRC. So, lets nail down the time as 2200 UTC on<br>
> > > #openstack-meeting-alt for tomorrow. If you can’t make it, I’ll send<br>
> > the meeting logs out.<br>
> > ><br>
> > > Thanks, look forward to seeing people there tomorrow!<br>
> > ><br>
> > > Kyle<br>
> > ><br>
> > > On Jan 14, 2014, at 9:49 AM, Lucas Eznarriaga <lucas@midokura.com><br>
> > wrote:<br>
> > ><br>
> > >> Hi,<br>
> > >> I will also be available for a meeting tomorrow.<br>
> > >> @Mohammad, we are still working on our 3rd party testing setup so do<br>
> > not take Midokura CI Bot votes too seriously yet.<br>
> > >> So far I have followed the links on the etherpad to have the<br>
> > jenkins+gerrit trigger plugin working with the current setup that's what<br>
> > I haven't added anything else yet.<br>
> > >><br>
> > >> Cheers,<br>
> > >> Lucas<br>
> > >><br>
> > >><br>
> > >><br>
> > >> On Tue, Jan 14, 2014 at 3:55 PM, Edgar Magana <emagana@plumgrid.com><br>
> > wrote:<br>
> > >> I like it and I am in favor.<br>
> > >> Some of us, will be in Montreal attending the sprint tempest session.<br>
> > Hopefully we can all take it from there.<br>
> > >><br>
> > >> Edgar<br>
> > >><br>
> > >>> On Jan 14, 2014, at 6:31 AM, Kyle Mestery <mestery@siliconloons.com><br>
> > wrote:<br>
> > >>><br>
> > >>> Thanks for sending this note Mohammad. I am all in favor of another<br>
> > >>> 3rd party testing meeting on IRC. How about if we shoot for<br>
> > >>> tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works<br>
> > for everyone.<br>
> > >>><br>
> > >>> Thanks,<br>
> > >>> Kyle<br>
> > >>><br>
> > >>>> On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi <mb@us.ibm.com><br>
> > wrote:<br>
> > >>>><br>
> > >>>> Hi everybody,<br>
> > >>>><br>
> > >>>> I see that we already have at least two 3rd party testing setups<br>
> > (from Arista and Midokura) up and running. Noticed their votes on our<br>
> > newly submitted plugin.<br>
> > >>>> The etherpad which is to be used for sharing information about<br>
> > setting up 3rd party testing (as well as multi-node testing) [1] seems<br>
> > to have not been updated recently. Would those who have setup their 3rd<br>
> > party testing successfully be willing to share more information as to<br>
> > what they have done and possibly update the etherpad?<br>
> > >>>><br>
> > >>>> Would it be of value to others if we have another IRC meeting to<br>
> > discuss this matter?<br>
> > >>>> (Kyle, I am sure you are busy so I took the liberty to send this<br>
> > >>>> note. Please let us know what you think.)<br>
> > >>>><br>
> > >>>> Thanks,<br>
> > >>>><br>
> > >>>> Mohammad<br>
> > >>>><br>
> > >>>><br>
> > >>>> [1] <a href="https://etherpad.openstack.org/p/multi-node-neutron-tempest">https://etherpad.openstack.org/p/multi-node-neutron-tempest</a><br>
> > >>>><br>
> > >>>> <graycol.gif>Kyle Mestery ---12/19/2013 09:17:44 AM---Apologies<br>
> > folks, I meant 2200 UTC Thursday. We'll still do the meeting today.<br>
> > >>>><br>
> > >>>> From: Kyle Mestery <mestery@siliconloons.com><br>
> > >>>> To: "OpenStack Development Mailing List \(not for usage<br>
> > questions\)" <openstack-dev@lists.openstack.org>,<br>
> > >>>> Date: 12/19/2013 09:17 AM<br>
> > >>>> Subject: Re: [openstack-dev] [neutron] [third-party-testing]<br>
> > Reminder: Meeting tomorrow<br>
> > >>>><br>
> > >>>><br>
> > >>>><br>
> > >>>> Apologies folks, I meant 2200 UTC Thursday. We'll still do the<br>
> > >>>> meeting today.<br>
> > >>>><br>
> > >>>>> On Dec 18, 2013, at 4:40 PM, Don Kehn <dekehn@gmail.com> wrote:<br>
> > >>>>><br>
> > >>>>> Wouldn't 2200 UTC be in about 20 mins?<br>
> > >>>>><br>
> > >>>>><br>
> > >>>>> On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA <oda@valinux.co.jp><br>
> > wrote:<br>
> > >>>>> Hi,<br>
> > >>>>><br>
> > >>>>> It seems the meeting was not held on 2200 UTC on Wednesday<br>
> > (today).<br>
> > >>>>><br>
> > >>>>> Do you mean 2200 UTC on Thursday ?<br>
> > >>>>><br>
> > >>>>> Thanks.<br>
> > >>>>><br>
> > >>>>> On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery<br>
> > >>>>> <mestery@siliconloons.com> wrote:<br>
> > >>>>><br>
> > >>>>>> Hi everyone:<br>
> > >>>>>><br>
> > >>>>>> We had a meeting around Neutron Third-Party testing today on IRC.<br>
> > >>>>>> The logs are available here [1]. We plan to host another meeting<br>
> > >>>>>> next week, and it will be at 2200 UTC on Wednesday in the<br>
> > >>>>>> #openstack-meeting-alt channel on IRC. Please attend and update<br>
> > >>>>>> the etherpad [2] with any items relevant to you before then.<br>
> > >>>>>><br>
> > >>>>>> Thanks again!<br>
> > >>>>>> Kyle<br>
> > >>>>>><br>
> > >>>>>> [1]<br>
> > >>>>>> <a href="http://eavesdrop.openstack.org/meetings/networking_third_party_te">http://eavesdrop.openstack.org/meetings/networking_third_party_te</a><br>
> > >>>>>> sting/2013/ [2]<br>
> > >>>>>> <a href="https://etherpad.openstack.org/p/multi-node-neutron-tempest">https://etherpad.openstack.org/p/multi-node-neutron-tempest</a><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>
> > >>>>><br>
> > >>>>> On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery<br>
> > >>>>> <mestery@siliconloons.com> wrote:<br>
> > >>>>><br>
> > >>>>>> Just a reminder, we'll be meeting at 2200 UTC on #openstack-<br>
> > meeting-alt.<br>
> > >>>>>> We'll be looking at this etherpad [1] again, and continuing<br>
> > >>>>>> discussions from last week.<br>
> > >>>>>><br>
> > >>>>>> Thanks!<br>
> > >>>>>> Kyle<br>
> > >>>>>><br>
> > >>>>>> [1] <a href="https://etherpad.openstack.org/p/multi-node-neutron-tempest">https://etherpad.openstack.org/p/multi-node-neutron-tempest</a><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>
> > >>>>><br>
> > >>>>> --<br>
> > >>>>> Itsuro ODA <oda@valinux.co.jp><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>
> > >>>>><br>
> > >>>>><br>
> > >>>>><br>
> > >>>>> --<br>
> > >>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
> > >>>>> Don Kehn<br>
> > >>>>> 303-442-0060<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>
> > >>>><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>
> > >>><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>
> > >><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>
> > >><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>
> > ><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>
> > <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>
> <br>
> <br>
> Thanks, <br>
> Jon-Paul Sullivan ☺ Cloud Services - @hpcloud<br>
> <br>
> Postal Address: Hewlett-Packard Galway Limited, Ballybrit Business <br>
> Park, Galway.<br>
> Registered Office: Hewlett-Packard Galway Limited, 63-74 Sir John <br>
> Rogerson's Quay, Dublin 2. <br>
> Registered Number: 361933<br>
> <br>
> The contents of this message and any attachments to it are <br>
> confidential and may be legally privileged. If you have received <br>
> this message in error you should delete it from your system <br>
> immediately and advise the sender.<br>
> <br>
> To any recipient of this message within HP, unless otherwise stated,<br>
> you should consider this message and attachments as "HP CONFIDENTIAL".<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>