Hi Matt et al, Thanks for taking the time to have a chat about it in Nova meeting yesterday. In relation to your two points below...
1. tempest-dsvm-ovsdpdk-nfv-networking job in our Intel NFV CI was broken for about a day till we troubleshooted the issue, to find out merge of this [1] change started to cause our troubles. We set Q_USE_PROVIDERNET_FOR_PUBLIC back to False to let the job get green again and test what it should be testing - nova/neutron changes and not giving false negatives because of that devstack change. We saw a REVERT [2] of the above change shortly after as it was breaking Jenkins neutron's linuxbridge tempest too [3]. 2. Our aim is to have two things tested when new change is proposed to devstack: NFV and OVS+DPDK. For better clarity we'll run two separate jobs instead of having NFV+OVSDPDK together. Currently we run OVSDPDK+ODL on devstack changes to discover potential issues with configuring these two together with each devstack change proposed. We've discussed this internally and we can add/(replace OVSDPDK+ODL job) with a 'tempest-dsvm-full-nfv' one (currently running on Nova changes) that does devstack + runs full tempest test suite (1100+ tests) on NFV enabled flavors. It should test properly proposed devstack changes with NFV features (as per wiki [4]) we have enabled in Openstack. Let me know if there are other questions, concerns, asks or suggestions. Thanks Waldek [1] https://review.openstack.org/#/c/343072/ [2] https://review.openstack.org/#/c/345820/ [3] https://bugs.launchpad.net/devstack/+bug/1605423 [4] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI >-----Original Message----- >From: Matt Riedemann [mailto:[email protected]] >Sent: Thursday, July 28, 2016 4:14 PM >To: [email protected] >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission > >On 7/21/2016 5:38 AM, Znoinski, Waldemar wrote: >> Hi Nova cores et al, >> >> >> >> I would like to acquire voting (+/-1 Verified) permission for our >> Intel NFV CI. >> >> >> >> 1. It's running since Q1'2015. >> >> 2. Wiki [1]. >> >> 3. It's using openstack-infra/puppet-openstackci >> <https://github.com/openstack-infra/puppet-openstackci> with Zuul >> 2.1.1 for last 4 months: zuul, gearman, Jenkins, nodepool, local Openstack >cloud. >> >> 4. We have a team of 2 people + me + Nagios looking after it. Its >> problems are fixed promptly and rechecks triggered after non-code >> related issues. It's being reconciled against ci-watch [2]. >> >> 5. Reviews [3]. >> >> >> >> Let me know if further questions. >> >> >> >> 1. https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI >> >> 2. http://ci-watch.tintri.com/project?project=nova >> >> 3. >> https://review.openstack.org/#/q/reviewer:%22Intel+NFV- >CI+%253Copensta >> ck-nfv-ci%2540intel.com%253E%22 >> >> >> >> >> >> >> *Waldek* >> >> >> >> -------------------------------------------------------------- >> Intel Research and Development Ireland Limited Registered in Ireland >> Registered Office: Collinstown Industrial Park, Leixlip, County >> Kildare Registered Number: 308263 >> >> This e-mail and any attachments may contain confidential material for >> the sole use of the intended recipient(s). Any review or distribution >> by others is strictly prohibited. If you are not the intended >> recipient, please contact the sender and delete all copies. >> >> >> >> >__________________________________________________________ >____________ >> ____ OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >We talked about this in the nova meeting today. I don't have a great grasp on >how the Intel NFV CI has been performing, but making it voting will help with >that. Looking at the 7 day results: > >http://ci-watch.tintri.com/project?project=nova&time=7+days > >Everything looks pretty good except for tempest-dsvm-ovsdpdk-nfv- >networking but Waldemar pointed out there was a change in devstack that >broke the CI for a day or so: > >https://github.com/openstack- >dev/devstack/commit/130a11f8aaf08ea529b6ce60dd9052451cb7bb5c > >I would like to know a little more about why we don't run the Intel NFV CI on >devstack changes to catch stuff like this before it becomes a breaking >problem? The team worked around it for now, but it is a concern of mine. I >think at least the Xen and PowerKVM CIs also run on devstack changes to >avoid problems like this. > >So please give me some details on running against devstack changes and >then I'll ack or nack the request. > >-- > >Thanks, > >Matt Riedemann > > >__________________________________________________________ >________________ >OpenStack Development Mailing List (not for usage questions) >Unsubscribe: OpenStack-dev- >[email protected]?subject:unsubscribe >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------------------------------------------------------- Intel Research and Development Ireland Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
