Open Stack

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+%253Copenstack-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: OpenStack-dev-request at lists.openstack.org?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