[openstack-dev] [neutron] [third-party-testing] Enabling voting for 3rd party testing
What is the criteria for this? The OpenDaylight Jenkins has been reliably voting for a few weeks now, I'm wondering how and when we can get it's voting rights approved. Thanks! Kyle ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Enabling voting for 3rd party testing
On 03/31/2014 06:02 PM, Kyle Mestery wrote: What is the criteria for this? The OpenDaylight Jenkins has been reliably voting for a few weeks now, I'm wondering how and when we can get it's voting rights approved. Thanks! Kyle ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev The criteria -infra is expecting is that the account in question would create an agenda item for the program weekly meeting. During the meeting, the account in question would present their data - test logs, commit history on sandbox repo, comment history on other repos and answer questions from the attendees about system fitness. There would then be some logged indication of the decision of the group/ptl (the meeting channels log votes, if a vote is called). The logged decision is then communicated to -infra (an -infra ml post is good for a link to the logs and follow up with a ping in -infra channel) to get your system moved to the voting group. Thanks for asking the question, Anita. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][third-party-testing] Third Party Test setup and details
Fellow developers, I just put together a wiki describing the Arista Third Party Setup. In the attached document we provide a link to the modified Gerrit Plugin to handle the regex matching for the Comment Added event so that recheck/reverify no bug/ can be handled. https://wiki.openstack.org/wiki/Arista-third-party-testing Have a look. Your feedback/comments will be appreciated. regards.. -Sukhdev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron] [third-party-testing] Which patchset triggered the test
Have a question regarding the Jenkins/Gerrit setup for third party testing setups. When Jenkins get triggered by a patchset through the Gerrit trigger plug-in, you can execute a set of shell scripts. How do you get the information about the patchset that triggered the test? In particular, in your scripts how do you figure out which patchset triggered the test. Here is why I am asking this question: During our earlier IRC calls we said, one approach for testing would be using devstack to install OpenStack and run appropriate tests. The devstack stack.sh brings in the master branch without the patchset which triggered the test. How do I access the patchset I want to test? Am I missing something here? Thanks, Mohammad___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Which patchset triggered the test
Mohammad, You can get the information you want from the environment variables that the Gerrit plugin sets. Just like it was mentioned here: https://etherpad.openstack.org/p/multi-node-neutron-tempest if you'll set NEUTRON_BRANCH=$GERRIT_REFSPEC in the localrc then Devstack will pull the change which triggered the build. Try env shell command to find out what are the rest of the environment variables. Best, --- Roey From: Mohammad Banikazemi [m...@us.ibm.com] Sent: Monday, January 20, 2014 9:32 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] [third-party-testing] Which patchset triggered the test Have a question regarding the Jenkins/Gerrit setup for third party testing setups. When Jenkins get triggered by a patchset through the Gerrit trigger plug-in, you can execute a set of shell scripts. How do you get the information about the patchset that triggered the test? In particular, in your scripts how do you figure out which patchset triggered the test. Here is why I am asking this question: During our earlier IRC calls we said, one approach for testing would be using devstack to install OpenStack and run appropriate tests. The devstack stack.sh brings in the master branch without the patchset which triggered the test. How do I access the patchset I want to test? Am I missing something here? Thanks, Mohammad ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Which patchset triggered the test
On Mon, 2014-01-20 at 14:26 -0500, Mohammad Banikazemi wrote: Have a question regarding the Jenkins/Gerrit setup for third party testing setups. When Jenkins get triggered by a patchset through the Gerrit trigger plug-in, you can execute a set of shell scripts. How do you get the information about the patchset that triggered the test? In particular, in your scripts how do you figure out which patchset triggered the test. Here is why I am asking this question: During our earlier IRC calls we said, one approach for testing would be using devstack to install OpenStack and run appropriate tests. The devstack stack.sh brings in the master branch without the patchset which triggered the test. How do I access the patchset I want to test? Am I missing something here? As mentioned by a previous poster, the Gerrit plugin populates some environment variables that you may use in your scripts in order to fetch and check out the appropriate git branch and SHA1 that corresponds to the changeset and patch number. For a great example of how this is done in the upstream CI system for the gate, check out the devstack-gate project and the setup_workspace() [1] Bash function. This function calls the setup_project() [2] Bash function for each project that is registered for devstack to construct. The devstack-gate-wrap.sh script is responsible for enumerating all of the projects that devstack will install [3]. setup_project() is responsible for setting the git checkouts for all of the OpenStack projects involved in the devstack installation -- including the project for which the triggering changeset is for. The function calls git clone on the project's upstream cgit repository URI [4], and then calls git fetch on the branch and SHA1 (ref) that represents the proposed changeset in Gerrit. In the setup_project() function, you will notice the use of the environment variables $ZUUL_BRANCH and $ZUUL_REF. The upstream CI system uses a Python service called Zuul [6] to manage the graph of in-progress changesets that are currently going through the gate testing process. While your in-house testing platform won't likely be using Zuul, the Gerrit plugin [7] to Jenkins *will* have a similar $GERRIT_BRANCH and $GERRIT_REFSPEC environment variable that you can use in your scripts that contains the git ref you can use in scripts in your in-house testing in the same way that devstack-gate uses $ZUUL_BRANCH and $ZUUL_REF. Finally, once your in-house setup script has constructed the devstack environment -- including all of the git checkout'd code trees, then to run the Neutron testing suite, simply do the following: cd /opt/stack/new/devstack sudo -H -u stack ./tools/configure_tempest.sh cd /opt/stack/new/tempest sudo -H -u tempest tox -esmoke-serial How did I know to run the above commands? Well, because that's what the check-tempest-dsvm-neutron-isolated (configured in the openstack-infra/config project here: [8]) test runs in the devstack-gate.sh script here: [9] :) All the best, -jay p.s. I'm putting together some documentation walking through how these many CI systems and gate projects all work together to configure and run tests against a devstack environment in the gate. I should be done by Wednesday or Thursday and will publish a link to the ML. Hopefully, the instructions will be helpful for Cinder, Neutron, and other contributors looking to set up 3rd party driver verification testing. [1] https://github.com/openstack-infra/devstack-gate/blob/master/functions.sh#L208 [2] https://github.com/openstack-infra/devstack-gate/blob/master/functions.sh#L164 [3] https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate-wrap.sh#L27 [4] https://github.com/openstack-infra/devstack-gate/blob/master/functions.sh#L96 [5] https://github.com/openstack-infra/devstack-gate/blob/master/functions.sh#L28 [6] http://ci.openstack.org/zuul.html [7] https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger [8] https://github.com/openstack-infra/config/blob/master/modules/openstack_project/files/jenkins_job_builder/config/devstack-gate.yaml#L184 and https://github.com/openstack-infra/config/blob/master/modules/openstack_project/files/jenkins_job_builder/config/devstack-gate.yaml#L203 [9] https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate.sh#L299 and https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate.sh#L344 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Which patchset triggered the test
Thanks a lot for answering my question and also for updating the multi-node/3rd party testing google doc as well. Mohammad From: Roey Chen ro...@mellanox.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org, Date: 01/20/2014 04:25 PM Subject:Re: [openstack-dev] [neutron] [third-party-testing] Which patchset triggered the test Mohammad, You can get the information you want from the environment variables that the Gerrit plugin sets. Just like it was mentioned here: https://etherpad.openstack.org/p/multi-node-neutron-tempest if you'll set NEUTRON_BRANCH=$GERRIT_REFSPEC in the localrc then Devstack will pull the change which triggered the build. Try env shell command to find out what are the rest of the environment variables. Best, --- Roey From: Mohammad Banikazemi [m...@us.ibm.com] Sent: Monday, January 20, 2014 9:32 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] [third-party-testing] Which patchset triggered the test Have a question regarding the Jenkins/Gerrit setup for third party testing setups. When Jenkins get triggered by a patchset through the Gerrit trigger plug-in, you can execute a set of shell scripts. How do you get the information about the patchset that triggered the test? In particular, in your scripts how do you figure out which patchset triggered the test. Here is why I am asking this question: During our earlier IRC calls we said, one approach for testing would be using devstack to install OpenStack and run appropriate tests. The devstack stack.sh brings in the master branch without the patchset which triggered the test. How do I access the patchset I want to test? Am I missing something here? Thanks, Mohammad___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev inline: graycol.gif___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
On Thu, 2014-01-16 at 15:37 +, Sullivan, Jon Paul wrote: From: Jay Pipes [mailto:jaypi...@gmail.com] On Thu, 2014-01-16 at 10:39 +, Sullivan, Jon Paul wrote: From: Kyle Mestery [mailto:mest...@siliconloons.com] FYI, here [1] are the meeting logs from today’s meeting. A couple of things have become apparent here: 1. No one has a working Neutron 3rd party testing rig yet which is voting consistently. If I’ve missed something, please, someone correct me. 2. People are still hung on issues around Jenkins/gerrit integration. This issue can be very easily resolved if people were to use Jenkins Job Builder [2] for the creation of their Jenkins testing jobs. This would allow the reuse of simple macros already in existence to guarantee correct configuration of Jenkins jobs at 3rd party sites. This would also allow simple reuse of the code used by the infra team to create the openstack review and gate jobs, ensuring 3rd party testers can generate the correct code from the gerrit change and also publish results back in a standard way. I can't recommend Jenkins Job Builder highly enough if you use Jenkins. [2] https://github.com/openstack-infra/jenkins-job-builder ++ It's a life-saver. We used it heavily in ATT with our Gerrit/Jenkins/Zuul CI system. -jay It seems to me that shared JJB macros could be the most concise and simple way of describing 3rd party testing integration requirements. So the follow-on questions are: 1. Can the 3rd party testing blueprint enforce, or at least link to, use of specific JJB macros for integration to the openstack gerrit? 1a. Where should shared JJB code be stored? Well, technically, this already exists. The openstack-infra/config project already has pretty much everything a 3rd party would ever need to setup an OpenStack environment, execute Tempest (or other) tests against the environment, save and publish artifacts, and send notifications of test results upstream. 2. Is it appropriate for 3rd party testers to share their tests as JJB code, if they are willing? 2a. Would this live in the same location as (1a)? Why would 3rd party testers be using anything other than Tempest for integration testing? Put another way... if a 3rd party *is* using something other than Tempest, why not put it in Tempest :) For those unfamiliar with JJB, here is a little example of what you might do: Example of (untested) JJB macro describing how to configure Jenkins to trigger from gerrit: snip As much as JJB is total awesomesauce -- as it prevents people needing to manually update Jenkins job config.xml files -- any 3rd party that is attempting to put together a test environment/platform for which you intend to interact with the upstream CI system should go check out devstack-gate [1], read the scripts, and grok it. I'm working on some instructions to assist admins in 3rd party testing labs in setting all of their platform up using the upstream tools like devstack-gate and JJB, and this documentation should be done around middle of next week. I'll post to the ML with links to that documentation when it's done. Best, -jay [1] https://github.com/openstack-infra/devstack-gate ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
Jay Pipes jaypi...@gmail.com wrote on 01/17/2014 04:32:55 PM: From: Jay Pipes jaypi...@gmail.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org, Date: 01/17/2014 04:37 PM Subject: Re: [openstack-dev] [neutron] [third-party-testing] Sharing information On Thu, 2014-01-16 at 15:37 +, Sullivan, Jon Paul wrote: From: Jay Pipes [mailto:jaypi...@gmail.com] On Thu, 2014-01-16 at 10:39 +, Sullivan, Jon Paul wrote: From: Kyle Mestery [mailto:mest...@siliconloons.com] FYI, here [1] are the meeting logs from today’s meeting. A couple of things have become apparent here: 1. No one has a working Neutron 3rd party testing rig yet which is voting consistently. If I’ve missed something, please, someone correct me. 2. People are still hung on issues around Jenkins/gerrit integration. This issue can be very easily resolved if people were to use Jenkins Job Builder [2] for the creation of their Jenkins testing jobs. This would allow the reuse of simple macros already in existence to guarantee correct configuration of Jenkins jobs at 3rd party sites. This would also allow simple reuse of the code used by the infra team to create the openstack review and gate jobs, ensuring 3rd party testers can generate the correct code from the gerrit change and also publish results back in a standard way. I can't recommend Jenkins Job Builder highly enough if you use Jenkins. [2] https://github.com/openstack-infra/jenkins-job-builder ++ It's a life-saver. We used it heavily in ATT with our Gerrit/Jenkins/Zuul CI system. -jay It seems to me that shared JJB macros could be the most concise and simple way of describing 3rd party testing integration requirements. So the follow-on questions are: 1. Can the 3rd party testing blueprint enforce, or at least link to, use of specific JJB macros for integration to the openstack gerrit? 1a. Where should shared JJB code be stored? Well, technically, this already exists. The openstack-infra/config project already has pretty much everything a 3rd party would ever need to setup an OpenStack environment, execute Tempest (or other) tests against the environment, save and publish artifacts, and send notifications of test results upstream. 2. Is it appropriate for 3rd party testers to share their tests as JJB code, if they are willing? 2a. Would this live in the same location as (1a)? Why would 3rd party testers be using anything other than Tempest for integration testing? Put another way... if a 3rd party *is* using something other than Tempest, why not put it in Tempest :) For those unfamiliar with JJB, here is a little example of what you might do: Example of (untested) JJB macro describing how to configure Jenkins to trigger from gerrit: snip As much as JJB is total awesomesauce -- as it prevents people needing to manually update Jenkins job config.xml files -- any 3rd party that is attempting to put together a test environment/platform for which you intend to interact with the upstream CI system should go check out devstack-gate [1], read the scripts, and grok it. I'm working on some instructions to assist admins in 3rd party testing labs in setting all of their platform up using the upstream tools like devstack-gate and JJB, and this documentation should be done around middle of next week. I'll post to the ML with links to that documentation when it's done. That would be great. Thanks. Please note that Icehouse-2 is the deadline for Neutron 3rd party test setups to be operational. Best, -jay [1] https://github.com/openstack-infra/devstack-gate ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
-Original Message- From: Kyle Mestery [mailto:mest...@siliconloons.com] Sent: 15 January 2014 22:53 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] [third-party-testing] Sharing information FYI, here [1] are the meeting logs from today’s meeting. A couple of things have become apparent here: 1. No one has a working Neutron 3rd party testing rig yet which is voting consistently. If I’ve missed something, please, someone correct me. 2. People are still hung on issues around Jenkins/gerrit integration. This issue can be very easily resolved if people were to use Jenkins Job Builder [2] for the creation of their Jenkins testing jobs. This would allow the reuse of simple macros already in existence to guarantee correct configuration of Jenkins jobs at 3rd party sites. This would also allow simple reuse of the code used by the infra team to create the openstack review and gate jobs, ensuring 3rd party testers can generate the correct code from the gerrit change and also publish results back in a standard way. I can't recommend Jenkins Job Builder highly enough if you use Jenkins. [2] https://github.com/openstack-infra/jenkins-job-builder 3. There are issues with devstack failing, but these seem to be Neutron plugin specific. I’ve encouraged people to reach out on both the #openstack-neutron and #openstack-qa channels with questions. 4. There is still some confusion on what tests to run. I think this is likely to be plugin dependent. 5. There is some confusion around what version of devstack to use. My assumption has always been upstream master. Another general issue which I wanted to highlight here, which has been brought up before, is that for companies/projects proposing plugins, MechanismDrivers, and/or service plugins you really need someone active on both the mailing list as well as the IRC channels. This will help if your testing rig has issues, or if people need help understanding why your test setup is failing with their patch. So, that’s the Neutron 3rd party testing update as we near the deadline next week. Thanks! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2 014/networking_third_party_testing.2014-01-15-22.00.log.html On Jan 14, 2014, at 10:34 AM, Kyle Mestery mest...@siliconloons.com wrote: Given the Tempest Sprint in Montreal, I still think we should have this meeting on IRC. So, lets nail down the time as 2200 UTC on #openstack-meeting-alt for tomorrow. If you can’t make it, I’ll send the meeting logs out. Thanks, look forward to seeing people there tomorrow! Kyle On Jan 14, 2014, at 9:49 AM, Lucas Eznarriaga lu...@midokura.com wrote: Hi, I will also be available for a meeting tomorrow. @Mohammad, we are still working on our 3rd party testing setup so do not take Midokura CI Bot votes too seriously yet. So far I have followed the links on the etherpad to have the jenkins+gerrit trigger plugin working with the current setup that's what I haven't added anything else yet. Cheers, Lucas On Tue, Jan 14, 2014 at 3:55 PM, Edgar Magana emag...@plumgrid.com wrote: I like it and I am in favor. Some of us, will be in Montreal attending the sprint tempest session. Hopefully we can all take it from there. Edgar On Jan 14, 2014, at 6:31 AM, Kyle Mestery mest...@siliconloons.com wrote: Thanks for sending this note Mohammad. I am all in favor of another 3rd party testing meeting on IRC. How about if we shoot for tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works for everyone. Thanks, Kyle On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi m...@us.ibm.com wrote: Hi everybody, I see that we already have at least two 3rd party testing setups (from Arista and Midokura) up and running. Noticed their votes on our newly submitted plugin. The etherpad which is to be used for sharing information about setting up 3rd party testing (as well as multi-node testing) [1] seems to have not been updated recently. Would those who have setup their 3rd party testing successfully be willing to share more information as to what they have done and possibly update the etherpad? Would it be of value to others if we have another IRC meeting to discuss this matter? (Kyle, I am sure you are busy so I took the liberty to send this note. Please let us know what you think.) Thanks, Mohammad [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest graycol.gifKyle Mestery ---12/19/2013 09:17:44 AM---Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. From:Kyle Mestery mest...@siliconloons.com To:OpenStack Development Mailing List \(not for usage questions\) openstack-dev@lists.openstack.org, Date:12/19/2013 09:17 AM Subject:Re: [openstack-dev] [neutron] [third-party
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
From: Mohammad Banikazemi [mailto:m...@us.ibm.com] Sullivan, Jon Paul jonpaul.sulli...@hp.commailto:jonpaul.sulli...@hp.com wrote on 01/16/2014 05:39:04 AM: I can't recommend Jenkins Job Builder highly enough if you use Jenkins. [2] https://github.com/openstack-infra/jenkins-job-builder Thanks for the pointer. When you say we could reuse the code used by the infra team, are you referring to the yaml files and/or build scripts? Is there a place where we could look at the yaml configuration (and other relevant) files that they may be using? The openstack-infra/config repository stores the openstack jjb code: https://github.com/openstack-infra/config/tree/master/modules/openstack_project/files/jenkins_job_builder/config I am writing another reply with a sample macro to trigger off a gerrit upload in a different reply… Thanks, Mohammad Thanks, Jon-Paul Sullivan ☺ Cloud Services - @hpcloud Postal Address: Hewlett-Packard Galway Limited, Ballybrit Business Park, Galway. Registered Office: Hewlett-Packard Galway Limited, 63-74 Sir John Rogerson's Quay, Dublin 2. Registered Number: 361933 The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated, you should consider this message and attachments as HP CONFIDENTIAL. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
From: Jay Pipes [mailto:jaypi...@gmail.com]
On Thu, 2014-01-16 at 10:39 +, Sullivan, Jon Paul wrote:
From: Kyle Mestery [mailto:mest...@siliconloons.com]
FYI, here [1] are the meeting logs from today’s meeting.
A couple of things have become apparent here:
1. No one has a working Neutron 3rd party testing rig yet which is
voting
consistently. If I’ve missed something, please, someone correct
me.
2. People are still hung on issues around Jenkins/gerrit
integration.
This issue can be very easily resolved if people were to use Jenkins
Job Builder [2] for the creation of their Jenkins testing jobs. This
would allow the reuse of simple macros already in existence to guarantee
correct configuration of Jenkins jobs at 3rd party sites. This would
also allow simple reuse of the code used by the infra team to create the
openstack review and gate jobs, ensuring 3rd party testers can generate
the correct code from the gerrit change and also publish results back in
a standard way.
I can't recommend Jenkins Job Builder highly enough if you use
Jenkins.
[2] https://github.com/openstack-infra/jenkins-job-builder
++ It's a life-saver. We used it heavily in ATT with our
Gerrit/Jenkins/Zuul CI system.
-jay
It seems to me that shared JJB macros could be the most concise and simple way
of describing 3rd party testing integration requirements.
So the follow-on questions are:
1. Can the 3rd party testing blueprint enforce, or at least link to,
use of specific JJB macros for integration to the openstack gerrit?
1a. Where should shared JJB code be stored?
2. Is it appropriate for 3rd party testers to share their tests as
JJB code, if they are willing?
2a. Would this live in the same location as (1a)?
For those unfamiliar with JJB, here is a little example of what you might do:
Example of (untested) JJB macro describing how to configure Jenkins to
trigger from gerrit:
- trigger:
name: 3rd-party-gerrit-review
triggers:
- gerrit:
triggerOnPatchsetUploadedEvent: true
triggerOnChangeMergedEvent: false
triggerOnRefUpdatedEvent: false
triggerOnCommentAddedEvent: false
overrideVotes: true
gerritBuildSuccessfulVerifiedValue: 0
gerritBuildFailedVerifiedValue: -1
projects:
- projectCompareType: 'PLAIN'
projectPattern: '{project_pattern}'
branchCompareType: 'ANT'
branchPattern: '**'
failureMessage: '3rd party test {test_name} failed. Contact is
{test_contact}. Test log is available at {test_log_url}'
Use of macro in JJB file (again untested):
-job:
name: my-test
triggers:
- 3rd-party-gerrit-review:
project_pattern: 'https://github.com/openstack/neutron.git'
test_name: 'my-3rd-party-test'
test_contact: 'my-em...@example.com'
test_log_url: 'http://mylogsarehere.com/'
3. There are issues with devstack failing, but these seem to be
Neutron
plugin specific. I’ve encouraged people to reach out on both the
#openstack-neutron and #openstack-qa channels with questions.
4. There is still some confusion on what tests to run. I think this
is
likely to be plugin dependent.
5. There is some confusion around what version of devstack to use.
My assumption has always been upstream master.
Another general issue which I wanted to highlight here, which has
been brought up before, is that for companies/projects proposing
plugins, MechanismDrivers, and/or service plugins you really need
someone active on both the mailing list as well as the IRC channels.
This will help if your testing rig has issues, or if people need
help understanding why your test setup is failing with their patch.
So, that’s the Neutron 3rd party testing update as we near the
deadline next week.
Thanks!
Kyle
[1]
http://eavesdrop.openstack.org/meetings/networking_third_party_testi
ng/2 014/networking_third_party_testing.2014-01-15-22.00.log.html
Thanks,
Jon-Paul Sullivan ☺ Cloud Services - @hpcloud
Postal Address: Hewlett-Packard Galway Limited, Ballybrit Business Park, Galway.
Registered Office: Hewlett-Packard Galway Limited, 63-74 Sir John Rogerson's
Quay, Dublin 2.
Registered Number: 361933
The contents of this message and any attachments to it are confidential and may
be legally privileged. If you have received this message in error you should
delete it from your system immediately and advise the sender.
To any recipient of this message within HP, unless otherwise stated, you should
consider this message and attachments as HP CONFIDENTIAL.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
Apologies for an almost duplicate post, I corrected the mistake in the example.
Ooops.
-Original Message-
From: Sullivan, Jon Paul
Sent: 16 January 2014 15:38
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] [third-party-testing] Sharing
information
From: Jay Pipes [mailto:jaypi...@gmail.com] On Thu, 2014-01-16 at
10:39 +, Sullivan, Jon Paul wrote:
From: Kyle Mestery [mailto:mest...@siliconloons.com]
FYI, here [1] are the meeting logs from today’s meeting.
A couple of things have become apparent here:
1. No one has a working Neutron 3rd party testing rig yet which is
voting
consistently. If I’ve missed something, please, someone
correct
me.
2. People are still hung on issues around Jenkins/gerrit
integration.
This issue can be very easily resolved if people were to use Jenkins
Job Builder [2] for the creation of their Jenkins testing jobs. This
would allow the reuse of simple macros already in existence to
guarantee correct configuration of Jenkins jobs at 3rd party sites.
This would also allow simple reuse of the code used by the infra team
to create the openstack review and gate jobs, ensuring 3rd party
testers can generate the correct code from the gerrit change and also
publish results back in a standard way.
I can't recommend Jenkins Job Builder highly enough if you use
Jenkins.
[2] https://github.com/openstack-infra/jenkins-job-builder
++ It's a life-saver. We used it heavily in ATT with our
Gerrit/Jenkins/Zuul CI system.
-jay
It seems to me that shared JJB macros could be the most concise and
simple way of describing 3rd party testing integration requirements.
So the follow-on questions are:
1. Can the 3rd party testing blueprint enforce, or at least link to,
use of specific JJB macros for integration to the openstack gerrit?
1a. Where should shared JJB code be stored?
2. Is it appropriate for 3rd party testers to share their tests as
JJB code, if they are willing?
2a. Would this live in the same location as (1a)?
For those unfamiliar with JJB, here is a little example of what you
might do:
Example of (untested) JJB macro describing how to configure Jenkins to
trigger from gerrit:
- trigger:
name: 3rd-party-gerrit-review
triggers:
- gerrit:
triggerOnPatchsetUploadedEvent: true
triggerOnChangeMergedEvent: false
triggerOnRefUpdatedEvent: false
triggerOnCommentAddedEvent: false
overrideVotes: true
gerritBuildSuccessfulVerifiedValue: 0
gerritBuildFailedVerifiedValue: -1
projects:
- projectCompareType: 'PLAIN'
projectPattern: '{project_pattern}'
branchCompareType: 'ANT'
branchPattern: '**'
failureMessage: '3rd party test {test_name} failed. Contact is
{test_contact}. Test log is available at {test_log_url}'
Corrected example:
Use of macro in JJB file (again untested):
-job:
name: my-test
triggers:
- 3rd-party-gerrit-review:
project_pattern: 'openstack/neutron.git'
test_name: 'my-3rd-party-test'
test_contact: 'my-em...@example.com'
test_log_url: 'http://mylogsarehere.com/'
3. There are issues with devstack failing, but these seem to be
Neutron
plugin specific. I’ve encouraged people to reach out on both
the
#openstack-neutron and #openstack-qa channels with questions.
4. There is still some confusion on what tests to run. I think
this
is
likely to be plugin dependent.
5. There is some confusion around what version of devstack to use.
My assumption has always been upstream master.
Another general issue which I wanted to highlight here, which has
been brought up before, is that for companies/projects proposing
plugins, MechanismDrivers, and/or service plugins you really need
someone active on both the mailing list as well as the IRC
channels.
This will help if your testing rig has issues, or if people need
help understanding why your test setup is failing with their
patch.
So, that’s the Neutron 3rd party testing update as we near the
deadline next week.
Thanks!
Kyle
[1]
http://eavesdrop.openstack.org/meetings/networking_third_party_tes
ti
ng/2 014/networking_third_party_testing.2014-01-15-22.00.log.html
Thanks,
Jon-Paul Sullivan ☺ Cloud Services - @hpcloud
Postal Address: Hewlett-Packard Galway Limited, Ballybrit Business Park,
Galway.
Registered Office: Hewlett-Packard Galway Limited, 63-74 Sir John
Rogerson's Quay, Dublin 2.
Registered Number: 361933
The contents of this message and any attachments to it are confidential
and may be legally privileged. If you have received this message in
error you
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
Hi, does anyone knows if the multi-node environnement is targeted by the openstack-infra team? On Tue, Jan 14, 2014 at 6:22 PM, Anita Kuno ante...@anteaya.info wrote: On 01/14/2014 11:34 AM, Kyle Mestery wrote: Given the Tempest Sprint in Montreal, I still think we should have this meeting on IRC. Shouldn't this be, given OpenStack is an open project [0], this meeting will take place on irc, just like all our other meetings.? Thanks, Anita. [0] https://wiki.openstack.org/wiki/Governance/Foundation/Mission So, lets nail down the time as 2200 UTC on #openstack-meeting-alt for tomorrow. If you can’t make it, I’ll send the meeting logs out. Thanks, look forward to seeing people there tomorrow! Kyle On Jan 14, 2014, at 9:49 AM, Lucas Eznarriaga lu...@midokura.com wrote: Hi, I will also be available for a meeting tomorrow. @Mohammad, we are still working on our 3rd party testing setup so do not take Midokura CI Bot votes too seriously yet. So far I have followed the links on the etherpad to have the jenkins+gerrit trigger plugin working with the current setup that's what I haven't added anything else yet. Cheers, Lucas On Tue, Jan 14, 2014 at 3:55 PM, Edgar Magana emag...@plumgrid.com wrote: I like it and I am in favor. Some of us, will be in Montreal attending the sprint tempest session. Hopefully we can all take it from there. Edgar On Jan 14, 2014, at 6:31 AM, Kyle Mestery mest...@siliconloons.com wrote: Thanks for sending this note Mohammad. I am all in favor of another 3rd party testing meeting on IRC. How about if we shoot for tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works for everyone. Thanks, Kyle On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi m...@us.ibm.com wrote: Hi everybody, I see that we already have at least two 3rd party testing setups (from Arista and Midokura) up and running. Noticed their votes on our newly submitted plugin. The etherpad which is to be used for sharing information about setting up 3rd party testing (as well as multi-node testing) [1] seems to have not been updated recently. Would those who have setup their 3rd party testing successfully be willing to share more information as to what they have done and possibly update the etherpad? Would it be of value to others if we have another IRC meeting to discuss this matter? (Kyle, I am sure you are busy so I took the liberty to send this note. Please let us know what you think.) Thanks, Mohammad [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest graycol.gifKyle Mestery ---12/19/2013 09:17:44 AM---Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. From:Kyle Mestery mest...@siliconloons.com To:OpenStack Development Mailing List \(not for usage questions\) openstack-dev@lists.openstack.org, Date:12/19/2013 09:17 AM Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Don Kehn 303-442-0060
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
Hi, Resending on this thread Below are the set of steps we are using for Jenkins setup and would like some clarifications reg some of the steps. Under Jenkins/Configure 1. Source Code Management: to be git and point to the devstack URL 2. Build Triggers: Gerrit Event 3. Build/Execute Shell: Sequence of commands to be executed 1. unstack.sh 2. configure localrc 3. configure 3rd party plugin 4. stack.sh 5. sequence of nosetests cmds with the tests to be run. 4. Post build Actions: Gerrit Integration to post the event (not configured currently) For step 3/5, is the right procedure. Or is there a way to use a cmd to run all the tests and use a different mechanism to specify a filter for the tests to be run. Thanks, -hemanth On Wed, Jan 15, 2014 at 2:49 AM, Mathieu Rohon mathieu.ro...@gmail.comwrote: Hi, does anyone knows if the multi-node environnement is targeted by the openstack-infra team? On Tue, Jan 14, 2014 at 6:22 PM, Anita Kuno ante...@anteaya.info wrote: On 01/14/2014 11:34 AM, Kyle Mestery wrote: Given the Tempest Sprint in Montreal, I still think we should have this meeting on IRC. Shouldn't this be, given OpenStack is an open project [0], this meeting will take place on irc, just like all our other meetings.? Thanks, Anita. [0] https://wiki.openstack.org/wiki/Governance/Foundation/Mission So, lets nail down the time as 2200 UTC on #openstack-meeting-alt for tomorrow. If you can’t make it, I’ll send the meeting logs out. Thanks, look forward to seeing people there tomorrow! Kyle On Jan 14, 2014, at 9:49 AM, Lucas Eznarriaga lu...@midokura.com wrote: Hi, I will also be available for a meeting tomorrow. @Mohammad, we are still working on our 3rd party testing setup so do not take Midokura CI Bot votes too seriously yet. So far I have followed the links on the etherpad to have the jenkins+gerrit trigger plugin working with the current setup that's what I haven't added anything else yet. Cheers, Lucas On Tue, Jan 14, 2014 at 3:55 PM, Edgar Magana emag...@plumgrid.com wrote: I like it and I am in favor. Some of us, will be in Montreal attending the sprint tempest session. Hopefully we can all take it from there. Edgar On Jan 14, 2014, at 6:31 AM, Kyle Mestery mest...@siliconloons.com wrote: Thanks for sending this note Mohammad. I am all in favor of another 3rd party testing meeting on IRC. How about if we shoot for tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works for everyone. Thanks, Kyle On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi m...@us.ibm.com wrote: Hi everybody, I see that we already have at least two 3rd party testing setups (from Arista and Midokura) up and running. Noticed their votes on our newly submitted plugin. The etherpad which is to be used for sharing information about setting up 3rd party testing (as well as multi-node testing) [1] seems to have not been updated recently. Would those who have setup their 3rd party testing successfully be willing to share more information as to what they have done and possibly update the etherpad? Would it be of value to others if we have another IRC meeting to discuss this matter? (Kyle, I am sure you are busy so I took the liberty to send this note. Please let us know what you think.) Thanks, Mohammad [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest graycol.gifKyle Mestery ---12/19/2013 09:17:44 AM---Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. From:Kyle Mestery mest...@siliconloons.com To:OpenStack Development Mailing List \(not for usage questions\) openstack-dev@lists.openstack.org, Date:12/19/2013 09:17 AM Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder:Meeting tomorrow Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
On 01/15/2014 05:49 AM, Mathieu Rohon wrote: Hi, does anyone knows if the multi-node environnement is targeted by the openstack-infra team? The last time multi-node testing was discussed at an -infra meeting was November 26, 2013. [0] The timestamp for the agenda item is 19:47:55 The understanding I have is that Kyle Mestery is gathering requirements and will get back to -infra once he has them. I do not believe that has happened. If someone feels this needs to be discussed, please co-ordinate with Kyle and add an item to the openstack-infra meeting agenda. [1] Thanks, Anita. [0] http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-11-26-19.02.log.html [1] https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting On Tue, Jan 14, 2014 at 6:22 PM, Anita Kuno ante...@anteaya.info wrote: On 01/14/2014 11:34 AM, Kyle Mestery wrote: Given the Tempest Sprint in Montreal, I still think we should have this meeting on IRC. Shouldn't this be, given OpenStack is an open project [0], this meeting will take place on irc, just like all our other meetings.? Thanks, Anita. [0] https://wiki.openstack.org/wiki/Governance/Foundation/Mission So, lets nail down the time as 2200 UTC on #openstack-meeting-alt for tomorrow. If you can’t make it, I’ll send the meeting logs out. Thanks, look forward to seeing people there tomorrow! Kyle On Jan 14, 2014, at 9:49 AM, Lucas Eznarriaga lu...@midokura.com wrote: Hi, I will also be available for a meeting tomorrow. @Mohammad, we are still working on our 3rd party testing setup so do not take Midokura CI Bot votes too seriously yet. So far I have followed the links on the etherpad to have the jenkins+gerrit trigger plugin working with the current setup that's what I haven't added anything else yet. Cheers, Lucas On Tue, Jan 14, 2014 at 3:55 PM, Edgar Magana emag...@plumgrid.com wrote: I like it and I am in favor. Some of us, will be in Montreal attending the sprint tempest session. Hopefully we can all take it from there. Edgar On Jan 14, 2014, at 6:31 AM, Kyle Mestery mest...@siliconloons.com wrote: Thanks for sending this note Mohammad. I am all in favor of another 3rd party testing meeting on IRC. How about if we shoot for tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works for everyone. Thanks, Kyle On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi m...@us.ibm.com wrote: Hi everybody, I see that we already have at least two 3rd party testing setups (from Arista and Midokura) up and running. Noticed their votes on our newly submitted plugin. The etherpad which is to be used for sharing information about setting up 3rd party testing (as well as multi-node testing) [1] seems to have not been updated recently. Would those who have setup their 3rd party testing successfully be willing to share more information as to what they have done and possibly update the etherpad? Would it be of value to others if we have another IRC meeting to discuss this matter? (Kyle, I am sure you are busy so I took the liberty to send this note. Please let us know what you think.) Thanks, Mohammad [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest graycol.gifKyle Mestery ---12/19/2013 09:17:44 AM---Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. From:Kyle Mestery mest...@siliconloons.com To:OpenStack Development Mailing List \(not for usage questions\) openstack-dev@lists.openstack.org, Date:12/19/2013 09:17 AM Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder:Meeting tomorrow Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
FYI, here [1] are the meeting logs from today’s meeting. A couple of things have become apparent here: 1. No one has a working Neutron 3rd party testing rig yet which is voting consistently. If I’ve missed something, please, someone correct me. 2. People are still hung on issues around Jenkins/gerrit integration. 3. There are issues with devstack failing, but these seem to be Neutron plugin specific. I’ve encouraged people to reach out on both the #openstack-neutron and #openstack-qa channels with questions. 4. There is still some confusion on what tests to run. I think this is likely to be plugin dependent. 5. There is some confusion around what version of devstack to use. My assumption has always been upstream master. Another general issue which I wanted to highlight here, which has been brought up before, is that for companies/projects proposing plugins, MechanismDrivers, and/or service plugins you really need someone active on both the mailing list as well as the IRC channels. This will help if your testing rig has issues, or if people need help understanding why your test setup is failing with their patch. So, that’s the Neutron 3rd party testing update as we near the deadline next week. Thanks! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2014/networking_third_party_testing.2014-01-15-22.00.log.html On Jan 14, 2014, at 10:34 AM, Kyle Mestery mest...@siliconloons.com wrote: Given the Tempest Sprint in Montreal, I still think we should have this meeting on IRC. So, lets nail down the time as 2200 UTC on #openstack-meeting-alt for tomorrow. If you can’t make it, I’ll send the meeting logs out. Thanks, look forward to seeing people there tomorrow! Kyle On Jan 14, 2014, at 9:49 AM, Lucas Eznarriaga lu...@midokura.com wrote: Hi, I will also be available for a meeting tomorrow. @Mohammad, we are still working on our 3rd party testing setup so do not take Midokura CI Bot votes too seriously yet. So far I have followed the links on the etherpad to have the jenkins+gerrit trigger plugin working with the current setup that's what I haven't added anything else yet. Cheers, Lucas On Tue, Jan 14, 2014 at 3:55 PM, Edgar Magana emag...@plumgrid.com wrote: I like it and I am in favor. Some of us, will be in Montreal attending the sprint tempest session. Hopefully we can all take it from there. Edgar On Jan 14, 2014, at 6:31 AM, Kyle Mestery mest...@siliconloons.com wrote: Thanks for sending this note Mohammad. I am all in favor of another 3rd party testing meeting on IRC. How about if we shoot for tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works for everyone. Thanks, Kyle On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi m...@us.ibm.com wrote: Hi everybody, I see that we already have at least two 3rd party testing setups (from Arista and Midokura) up and running. Noticed their votes on our newly submitted plugin. The etherpad which is to be used for sharing information about setting up 3rd party testing (as well as multi-node testing) [1] seems to have not been updated recently. Would those who have setup their 3rd party testing successfully be willing to share more information as to what they have done and possibly update the etherpad? Would it be of value to others if we have another IRC meeting to discuss this matter? (Kyle, I am sure you are busy so I took the liberty to send this note. Please let us know what you think.) Thanks, Mohammad [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest graycol.gifKyle Mestery ---12/19/2013 09:17:44 AM---Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. From:Kyle Mestery mest...@siliconloons.com To:OpenStack Development Mailing List \(not for usage questions\) openstack-dev@lists.openstack.org, Date:12/19/2013 09:17 AM Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
Thanks for sending this note Mohammad. I am all in favor of another 3rd party testing meeting on IRC. How about if we shoot for tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works for everyone. Thanks, Kyle On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi m...@us.ibm.com wrote: Hi everybody, I see that we already have at least two 3rd party testing setups (from Arista and Midokura) up and running. Noticed their votes on our newly submitted plugin. The etherpad which is to be used for sharing information about setting up 3rd party testing (as well as multi-node testing) [1] seems to have not been updated recently. Would those who have setup their 3rd party testing successfully be willing to share more information as to what they have done and possibly update the etherpad? Would it be of value to others if we have another IRC meeting to discuss this matter? (Kyle, I am sure you are busy so I took the liberty to send this note. Please let us know what you think.) Thanks, Mohammad [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest graycol.gifKyle Mestery ---12/19/2013 09:17:44 AM---Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. From: Kyle Mestery mest...@siliconloons.com To: OpenStack Development Mailing List \(not for usage questions\) openstack-dev@lists.openstack.org, Date: 12/19/2013 09:17 AM Subject: Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Don Kehn 303-442-0060 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
I like it and I am in favor. Some of us, will be in Montreal attending the sprint tempest session. Hopefully we can all take it from there. Edgar On Jan 14, 2014, at 6:31 AM, Kyle Mestery mest...@siliconloons.com wrote: Thanks for sending this note Mohammad. I am all in favor of another 3rd party testing meeting on IRC. How about if we shoot for tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works for everyone. Thanks, Kyle On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi m...@us.ibm.com wrote: Hi everybody, I see that we already have at least two 3rd party testing setups (from Arista and Midokura) up and running. Noticed their votes on our newly submitted plugin. The etherpad which is to be used for sharing information about setting up 3rd party testing (as well as multi-node testing) [1] seems to have not been updated recently. Would those who have setup their 3rd party testing successfully be willing to share more information as to what they have done and possibly update the etherpad? Would it be of value to others if we have another IRC meeting to discuss this matter? (Kyle, I am sure you are busy so I took the liberty to send this note. Please let us know what you think.) Thanks, Mohammad [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest graycol.gifKyle Mestery ---12/19/2013 09:17:44 AM---Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. From:Kyle Mestery mest...@siliconloons.com To:OpenStack Development Mailing List \(not for usage questions\) openstack-dev@lists.openstack.org, Date:12/19/2013 09:17 AM Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Don Kehn 303-442-0060 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
Sounds good. Thanks. Mohammad From: Kyle Mestery mest...@siliconloons.com To: Mohammad Banikazemi/Watson/IBM@IBMUS, Cc: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 01/14/2014 09:31 AM Subject:Re: [openstack-dev] [neutron] [third-party-testing] Sharing information Thanks for sending this note Mohammad. I am all in favor of another 3rd party testing meeting on IRC. How about if we shoot for tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works for everyone. Thanks, Kyle On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi m...@us.ibm.com wrote: Hi everybody, I see that we already have at least two 3rd party testing setups (from Arista and Midokura) up and running. Noticed their votes on our newly submitted plugin. The etherpad which is to be used for sharing information about setting up 3rd party testing (as well as multi-node testing) [1] seems to have not been updated recently. Would those who have setup their 3rd party testing successfully be willing to share more information as to what they have done and possibly update the etherpad? Would it be of value to others if we have another IRC meeting to discuss this matter? (Kyle, I am sure you are busy so I took the liberty to send this note. Please let us know what you think.) Thanks, Mohammad [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest graycol.gifKyle Mestery ---12/19/2013 09:17:44 AM---Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. From: Kyle Mestery mest...@siliconloons.com To:OpenStack Development Mailing List \(not for usage questions \) openstack-dev@lists.openstack.org, Date: 12/19/2013 09:17 AM Subject: Re: [openstack-dev] [neutron] [third-party-testing] Reminder:Meeting tomorrow Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Don Kehn 303-442-0060 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev inline: graycol.gif___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
Hi Kyle: I want to confirm about the meeting time(Wednesday the 15, at 2200 UTC). Some of colleagues are trying to setup the testing infra, they are very interested in this topic and would like to attend the meeting. 2014/1/14 Edgar Magana emag...@plumgrid.com I like it and I am in favor. Some of us, will be in Montreal attending the sprint tempest session. Hopefully we can all take it from there. Edgar On Jan 14, 2014, at 6:31 AM, Kyle Mestery mest...@siliconloons.com wrote: Thanks for sending this note Mohammad. I am all in favor of another 3rd party testing meeting on IRC. How about if we shoot for tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works for everyone. Thanks, Kyle On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi m...@us.ibm.com wrote: Hi everybody, I see that we already have at least two 3rd party testing setups (from Arista and Midokura) up and running. Noticed their votes on our newly submitted plugin. The etherpad which is to be used for sharing information about setting up 3rd party testing (as well as multi-node testing) [1] seems to have not been updated recently. Would those who have setup their 3rd party testing successfully be willing to share more information as to what they have done and possibly update the etherpad? Would it be of value to others if we have another IRC meeting to discuss this matter? (Kyle, I am sure you are busy so I took the liberty to send this note. Please let us know what you think.) Thanks, Mohammad [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest graycol.gifKyle Mestery ---12/19/2013 09:17:44 AM---Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. From:Kyle Mestery mest...@siliconloons.com To:OpenStack Development Mailing List \(not for usage questions\) openstack-dev@lists.openstack.org, Date:12/19/2013 09:17 AM Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder:Meeting tomorrow Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Don Kehn 303-442-0060 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- *---* *Lingxian Kong* Huawei Technologies Co.,LTD. IT Product Line CloudOS PDU China, Xi'an Mobile: +86-18602962792 Email: konglingx...@huawei.com; anlin.k
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
Hi, I will also be available for a meeting tomorrow. @Mohammad, we are still working on our 3rd party testing setup so do not take Midokura CI Bot votes too seriously yet. So far I have followed the links on the etherpad to have the jenkins+gerrit trigger plugin working with the current setup that's what I haven't added anything else yet. Cheers, Lucas On Tue, Jan 14, 2014 at 3:55 PM, Edgar Magana emag...@plumgrid.com wrote: I like it and I am in favor. Some of us, will be in Montreal attending the sprint tempest session. Hopefully we can all take it from there. Edgar On Jan 14, 2014, at 6:31 AM, Kyle Mestery mest...@siliconloons.com wrote: Thanks for sending this note Mohammad. I am all in favor of another 3rd party testing meeting on IRC. How about if we shoot for tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works for everyone. Thanks, Kyle On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi m...@us.ibm.com wrote: Hi everybody, I see that we already have at least two 3rd party testing setups (from Arista and Midokura) up and running. Noticed their votes on our newly submitted plugin. The etherpad which is to be used for sharing information about setting up 3rd party testing (as well as multi-node testing) [1] seems to have not been updated recently. Would those who have setup their 3rd party testing successfully be willing to share more information as to what they have done and possibly update the etherpad? Would it be of value to others if we have another IRC meeting to discuss this matter? (Kyle, I am sure you are busy so I took the liberty to send this note. Please let us know what you think.) Thanks, Mohammad [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest graycol.gifKyle Mestery ---12/19/2013 09:17:44 AM---Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. From:Kyle Mestery mest...@siliconloons.com To:OpenStack Development Mailing List \(not for usage questions\) openstack-dev@lists.openstack.org, Date:12/19/2013 09:17 AM Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder:Meeting tomorrow Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Don Kehn 303-442-0060 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
Given the Tempest Sprint in Montreal, I still think we should have this meeting on IRC. So, lets nail down the time as 2200 UTC on #openstack-meeting-alt for tomorrow. If you can’t make it, I’ll send the meeting logs out. Thanks, look forward to seeing people there tomorrow! Kyle On Jan 14, 2014, at 9:49 AM, Lucas Eznarriaga lu...@midokura.com wrote: Hi, I will also be available for a meeting tomorrow. @Mohammad, we are still working on our 3rd party testing setup so do not take Midokura CI Bot votes too seriously yet. So far I have followed the links on the etherpad to have the jenkins+gerrit trigger plugin working with the current setup that's what I haven't added anything else yet. Cheers, Lucas On Tue, Jan 14, 2014 at 3:55 PM, Edgar Magana emag...@plumgrid.com wrote: I like it and I am in favor. Some of us, will be in Montreal attending the sprint tempest session. Hopefully we can all take it from there. Edgar On Jan 14, 2014, at 6:31 AM, Kyle Mestery mest...@siliconloons.com wrote: Thanks for sending this note Mohammad. I am all in favor of another 3rd party testing meeting on IRC. How about if we shoot for tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works for everyone. Thanks, Kyle On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi m...@us.ibm.com wrote: Hi everybody, I see that we already have at least two 3rd party testing setups (from Arista and Midokura) up and running. Noticed their votes on our newly submitted plugin. The etherpad which is to be used for sharing information about setting up 3rd party testing (as well as multi-node testing) [1] seems to have not been updated recently. Would those who have setup their 3rd party testing successfully be willing to share more information as to what they have done and possibly update the etherpad? Would it be of value to others if we have another IRC meeting to discuss this matter? (Kyle, I am sure you are busy so I took the liberty to send this note. Please let us know what you think.) Thanks, Mohammad [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest graycol.gifKyle Mestery ---12/19/2013 09:17:44 AM---Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. From:Kyle Mestery mest...@siliconloons.com To:OpenStack Development Mailing List \(not for usage questions\) openstack-dev@lists.openstack.org, Date:12/19/2013 09:17 AM Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Don Kehn 303-442-0060 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
On 01/14/2014 11:34 AM, Kyle Mestery wrote: Given the Tempest Sprint in Montreal, I still think we should have this meeting on IRC. Shouldn't this be, given OpenStack is an open project [0], this meeting will take place on irc, just like all our other meetings.? Thanks, Anita. [0] https://wiki.openstack.org/wiki/Governance/Foundation/Mission So, lets nail down the time as 2200 UTC on #openstack-meeting-alt for tomorrow. If you can’t make it, I’ll send the meeting logs out. Thanks, look forward to seeing people there tomorrow! Kyle On Jan 14, 2014, at 9:49 AM, Lucas Eznarriaga lu...@midokura.com wrote: Hi, I will also be available for a meeting tomorrow. @Mohammad, we are still working on our 3rd party testing setup so do not take Midokura CI Bot votes too seriously yet. So far I have followed the links on the etherpad to have the jenkins+gerrit trigger plugin working with the current setup that's what I haven't added anything else yet. Cheers, Lucas On Tue, Jan 14, 2014 at 3:55 PM, Edgar Magana emag...@plumgrid.com wrote: I like it and I am in favor. Some of us, will be in Montreal attending the sprint tempest session. Hopefully we can all take it from there. Edgar On Jan 14, 2014, at 6:31 AM, Kyle Mestery mest...@siliconloons.com wrote: Thanks for sending this note Mohammad. I am all in favor of another 3rd party testing meeting on IRC. How about if we shoot for tomorrow, Wednesday the 15, at 2200 UTC? Please ack if that works for everyone. Thanks, Kyle On Jan 13, 2014, at 5:08 PM, Mohammad Banikazemi m...@us.ibm.com wrote: Hi everybody, I see that we already have at least two 3rd party testing setups (from Arista and Midokura) up and running. Noticed their votes on our newly submitted plugin. The etherpad which is to be used for sharing information about setting up 3rd party testing (as well as multi-node testing) [1] seems to have not been updated recently. Would those who have setup their 3rd party testing successfully be willing to share more information as to what they have done and possibly update the etherpad? Would it be of value to others if we have another IRC meeting to discuss this matter? (Kyle, I am sure you are busy so I took the liberty to send this note. Please let us know what you think.) Thanks, Mohammad [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest graycol.gifKyle Mestery ---12/19/2013 09:17:44 AM---Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. From:Kyle Mestery mest...@siliconloons.com To:OpenStack Development Mailing List \(not for usage questions\) openstack-dev@lists.openstack.org, Date:12/19/2013 09:17 AM Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Don Kehn 303-442-0060 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Sharing information
Hi everybody, I see that we already have at least two 3rd party testing setups (from Arista and Midokura) up and running. Noticed their votes on our newly submitted plugin. The etherpad which is to be used for sharing information about setting up 3rd party testing (as well as multi-node testing) [1] seems to have not been updated recently. Would those who have setup their 3rd party testing successfully be willing to share more information as to what they have done and possibly update the etherpad? Would it be of value to others if we have another IRC meeting to discuss this matter? (Kyle, I am sure you are busy so I took the liberty to send this note. Please let us know what you think.) Thanks, Mohammad [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest From: Kyle Mestery mest...@siliconloons.com To: OpenStack Development Mailing List \(not for usage questions \) openstack-dev@lists.openstack.org, Date: 12/19/2013 09:17 AM Subject:Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Don Kehn 303-442-0060 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev inline: graycol.gif___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron] [third-party-testing] Tests against vendor controller
Hi, We are developing a neutron plugin that works with our network controller. Do we need to have 2 sets of tests for the plugin i) tests that can be run against the network controller in our third party test setup (to vote on changes to the plugin) ii) tests that can be run in the OpenStack test setup Thanks, -hemanth ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow
Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Don Kehn 303-442-0060 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow
Hi, I'm sorry I could not make it to meeting. However, I can see clearly see the progress being made from gerrit! One thing which might be worth mentioning is that some of the new jobs are already voting. However, in some cases the logs are either not accessible, and in other cases the job seem to be a work-in-progress. For instance I've seen some just launching devstack; nevertheless the job still votes. I think publicly available logs and execution of the tempest smoke suite or a reasonable subset of it should be a required condition for voting. Is this something which was also discussed at today's meeting? Salvatore On 19 December 2013 15:12, Kyle Mestery mest...@siliconloons.com wrote: Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Don Kehn 303-442-0060 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow
Salvatore, Agreed that a visible job-log should be a requirement, otherwise who knows what was actually run. -Shiv From: Salvatore Orlando [mailto:sorla...@nicira.com] Sent: Thursday, December 19, 2013 4:50 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow Hi, I'm sorry I could not make it to meeting. However, I can see clearly see the progress being made from gerrit! One thing which might be worth mentioning is that some of the new jobs are already voting. However, in some cases the logs are either not accessible, and in other cases the job seem to be a work-in-progress. For instance I've seen some just launching devstack; nevertheless the job still votes. I think publicly available logs and execution of the tempest smoke suite or a reasonable subset of it should be a required condition for voting. Is this something which was also discussed at today's meeting? Salvatore On 19 December 2013 15:12, Kyle Mestery mest...@siliconloons.commailto:mest...@siliconloons.com wrote: Apologies folks, I meant 2200 UTC Thursday. We'll still do the meeting today. On Dec 18, 2013, at 4:40 PM, Don Kehn dek...@gmail.commailto:dek...@gmail.com wrote: Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jpmailto:o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.commailto:mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.commailto:mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jpmailto:o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Don Kehn 303-442-0060 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow
Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow
Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow
Wouldn't 2200 UTC be in about 20 mins? On Wed, Dec 18, 2013 at 3:32 PM, Itsuro ODA o...@valinux.co.jp wrote: Hi, It seems the meeting was not held on 2200 UTC on Wednesday (today). Do you mean 2200 UTC on Thursday ? Thanks. On Thu, 12 Dec 2013 11:43:03 -0600 Kyle Mestery mest...@siliconloons.com wrote: Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev On Wed, 18 Dec 2013 15:10:46 -0600 Kyle Mestery mest...@siliconloons.com wrote: Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Itsuro ODA o...@valinux.co.jp ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Don Kehn 303-442-0060 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron] [third-party-testing] Meeting Minutes for our first meeting
Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items relevant to you before then. Thanks again! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/ [2] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Third-party testing
Hi Yoshihiro, In my opinion the use of filters on changes is allowed by the smoketesting policy we defined. Notwithstanding that the approach of testing every patch is definitely the safest, I understand in some cases the volume of patchsets uploaded to gerrit might overwhelm the plugin-specific testing system, especially in cases where not much resources are dedicated to it. I would suggest to test every patch which has changes in the following packages: neutron.db neutron.api neutron.extensions neutron.plugin.your-plugin neutron.openstack neutron.agent (if your plugin uses any of the agents) Regards, Salvatore On 10 December 2013 06:09, Yoshihiro Kaneko ykaneko0...@gmail.com wrote: 2013/12/10 Matt Riedemann mrie...@linux.vnet.ibm.com: On Sunday, December 08, 2013 11:32:50 PM, Yoshihiro Kaneko wrote: Hi Neutron team, I'm working on building Third-party testing for Neutron Ryu plugin. I intend to use Jenkins and gerrit-trigger plugin. It is required that Third-party testing provides verify vote for all changes to a plugin/driver's code, and all code submissions by the jenkins user. https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Testing_Requirements For this requirements, what kind of filter for the trigger should I set? It is easy to set a file path of the plugin/driver: project: plain:neutron branch: plain:master file:path:neutron/plugins/ryu/** However, this is not enough because it lacks dependencies. It is difficult to judge a patchset which affects the plugin/driver. In addition, gerrit trigger has a file path filter, but there is no patchset owner filter, so it is not able to set a trigger to a patchset which is submitted by the jenkins user. Can Third-party testing execute tests for all patchset including the thing which may not affect the plugin/driver? Thanks, Kaneko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev I can't speak for the Neutron team, but in Nova the requirement is to run all patches through the vendor plugin third party CI, not just vendor-specific patches. Thanks for the reply, Matt. I believe that it is the right way for a smoke testing. https://wiki.openstack.org/wiki/HypervisorSupportMatrix/DeprecationPlan -- Thanks, Matt Riedemann ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Third-party testing
Hi Salvatore, Thank you for your reply. 2013/12/11 Salvatore Orlando sorla...@nicira.com: Hi Yoshihiro, In my opinion the use of filters on changes is allowed by the smoketesting policy we defined. Notwithstanding that the approach of testing every patch is definitely the safest, I understand in some cases the volume of patchsets uploaded to gerrit might overwhelm the plugin-specific testing system, especially in cases where not much resources are dedicated to it. Ah, I have not considered a heavy load. I would suggest to test every patch which has changes in the following packages: neutron.db neutron.api neutron.extensions neutron.plugin.your-plugin neutron.openstack neutron.agent (if your plugin uses any of the agents) Thank you for the details. It helps me very much. Many thanks! Regards, Salvatore On 10 December 2013 06:09, Yoshihiro Kaneko ykaneko0...@gmail.com wrote: 2013/12/10 Matt Riedemann mrie...@linux.vnet.ibm.com: On Sunday, December 08, 2013 11:32:50 PM, Yoshihiro Kaneko wrote: Hi Neutron team, I'm working on building Third-party testing for Neutron Ryu plugin. I intend to use Jenkins and gerrit-trigger plugin. It is required that Third-party testing provides verify vote for all changes to a plugin/driver's code, and all code submissions by the jenkins user. https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Testing_Requirements For this requirements, what kind of filter for the trigger should I set? It is easy to set a file path of the plugin/driver: project: plain:neutron branch: plain:master file:path:neutron/plugins/ryu/** However, this is not enough because it lacks dependencies. It is difficult to judge a patchset which affects the plugin/driver. In addition, gerrit trigger has a file path filter, but there is no patchset owner filter, so it is not able to set a trigger to a patchset which is submitted by the jenkins user. Can Third-party testing execute tests for all patchset including the thing which may not affect the plugin/driver? Thanks, Kaneko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev I can't speak for the Neutron team, but in Nova the requirement is to run all patches through the vendor plugin third party CI, not just vendor-specific patches. Thanks for the reply, Matt. I believe that it is the right way for a smoke testing. https://wiki.openstack.org/wiki/HypervisorSupportMatrix/DeprecationPlan -- Thanks, Matt Riedemann ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Third-party testing
On Sunday, December 08, 2013 11:32:50 PM, Yoshihiro Kaneko wrote: Hi Neutron team, I'm working on building Third-party testing for Neutron Ryu plugin. I intend to use Jenkins and gerrit-trigger plugin. It is required that Third-party testing provides verify vote for all changes to a plugin/driver's code, and all code submissions by the jenkins user. https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Testing_Requirements For this requirements, what kind of filter for the trigger should I set? It is easy to set a file path of the plugin/driver: project: plain:neutron branch: plain:master file:path:neutron/plugins/ryu/** However, this is not enough because it lacks dependencies. It is difficult to judge a patchset which affects the plugin/driver. In addition, gerrit trigger has a file path filter, but there is no patchset owner filter, so it is not able to set a trigger to a patchset which is submitted by the jenkins user. Can Third-party testing execute tests for all patchset including the thing which may not affect the plugin/driver? Thanks, Kaneko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev I can't speak for the Neutron team, but in Nova the requirement is to run all patches through the vendor plugin third party CI, not just vendor-specific patches. https://wiki.openstack.org/wiki/HypervisorSupportMatrix/DeprecationPlan -- Thanks, Matt Riedemann ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Third-party testing
2013/12/10 Matt Riedemann mrie...@linux.vnet.ibm.com: On Sunday, December 08, 2013 11:32:50 PM, Yoshihiro Kaneko wrote: Hi Neutron team, I'm working on building Third-party testing for Neutron Ryu plugin. I intend to use Jenkins and gerrit-trigger plugin. It is required that Third-party testing provides verify vote for all changes to a plugin/driver's code, and all code submissions by the jenkins user. https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Testing_Requirements For this requirements, what kind of filter for the trigger should I set? It is easy to set a file path of the plugin/driver: project: plain:neutron branch: plain:master file:path:neutron/plugins/ryu/** However, this is not enough because it lacks dependencies. It is difficult to judge a patchset which affects the plugin/driver. In addition, gerrit trigger has a file path filter, but there is no patchset owner filter, so it is not able to set a trigger to a patchset which is submitted by the jenkins user. Can Third-party testing execute tests for all patchset including the thing which may not affect the plugin/driver? Thanks, Kaneko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev I can't speak for the Neutron team, but in Nova the requirement is to run all patches through the vendor plugin third party CI, not just vendor-specific patches. Thanks for the reply, Matt. I believe that it is the right way for a smoke testing. https://wiki.openstack.org/wiki/HypervisorSupportMatrix/DeprecationPlan -- Thanks, Matt Riedemann ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
