Re: [openstack-dev] [infra][neutron] Intel NFV CI voting permission in Neutron

[Znoinski, Waldemar]

Hi Ihar et al,
Apologies for late reply. We were fighting couple of issues with the CI in last 
couple of days. The networking problem mentioned by Ihar was one of them.
We're running fine as of yesterday [1]. To stay on the safe side let's wait a 
few days so CI proves stable before making it voting. I'll ping you this Friday 
- hope that's ok.


1. http://ci-watch.tintri.com/project?project=neutron&time=7+days

 >-Original Message-
 >From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
 >Sent: Monday, November 28, 2016 4:24 PM
 >To: OpenStack Development Mailing List (not for usage questions)
 >
 >Cc: openstack-in...@lists.openstack.org
 >Subject: Re: [openstack-dev] [infra][neutron] Intel NFV CI voting permission
 >in Neutron
 >
 >
 >> On 28 Nov 2016, at 12:18, Ihar Hrachyshka  wrote:
 >>
 >> I suggest we disable votes for the setup until it’s fixed.
 >
 >UPD: done, the CI is disabled for voting.
 >
 >Ihar
 >__
 >
 >OpenStack Development Mailing List (not for usage questions)
 >Unsubscribe: OpenStack-dev-
 >requ...@lists.openstack.org?subject:unsubscribe
 >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] [infra][neutron] Intel NFV CI voting permission in Neutron

[Znoinski, Waldemar]

 >-Original Message-
 >From: Jeremy Stanley [mailto:fu...@yuggoth.org]
 >Sent: Monday, November 14, 2016 3:40 PM
 >To: openstack-in...@lists.openstack.org; openstack-dev@lists.openstack.org
 >Subject: Re: [openstack-dev] [OpenStack-Infra] [infra][neutron] Intel NFV CI
 >voting permission in Neutron
 >
 >On 2016-11-14 10:44:42 + (+0000), Znoinski, Waldemar wrote:
 >> I would like to acquire voting (+/-1 Verified) permission for our
 >> Intel NFV CI.
 >[...]
 >
 >The requested permission is configured by addition to
 >https://review.openstack.org/#/admin/groups/neutron-ci which is
 >controlled by the members of the
 >https://review.openstack.org/#/admin/groups/neutron-release group.
 >The Infra team tries not to be involved in these decisions and instead prefers
 >to leave them up to the project team(s) involved.
[WZ] thanks for explanation Jeremy, that was my intention - the ask is to 
Neutron(-release) guys, with Infra as FYI

 >
 >> 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.
 >[...]
 >
 >This seems wholly inappropriate for a public mailing list. I strongly
 >recommend not sending messages to our mailing lists in which you strictly
 >prohibit review or distribution by others, as it is guaranteed to happen and
 >we cannot prevent that (nor would we want to).
[WZ] requested removal of that footer, thanks

 >--
 >Jeremy Stanley
 >
 >__
 >
 >OpenStack Development Mailing List (not for usage questions)
 >Unsubscribe: OpenStack-dev-
 >requ...@lists.openstack.org?subject:unsubscribe
 >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [infra][neutron] Intel NFV CI voting permission in Neutron

[Znoinski, Waldemar]

Hi Neutron, Infra Cores et al,
I would like to acquire voting (+/-1 Verified) permission for our Intel NFV CI.

1. It's running on Neutron changes since Q1'2015.
2. Wiki [1].
3. It's using openstack-infra/puppet-openstackci [2] with Zuul 2.1.1 for last 8 
months: zuul, gearman, Jenkins, nodepool, local Openstack cloud with VMs and 
baremetal servers (where needed).
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 [3] and gerrit using [4].
5. It has a good record of testing for Nova, also voting for last 4 months [5].

[1] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI
[2] https://github.com/openstack-infra/puppet-openstackci
[3] http://ci-watch.tintri.com/project?project=neutron
[4] https://review.openstack.org/#/c/382262/
[5] 
https://review.openstack.org/#/q/reviewer:%22Intel+NFV-CI+%253Copenstack-nfv-ci%2540intel.com%253E%22

Regards
Waldek

Waldemar Znoinski
Software Applications Engineer
+353 (0) 6 1477 782
Intel Research and Development Ireland Ltd
Dromore House, East Park
Shannon, Co. Clare, Ireland

--
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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-infra][nova][tempest][qa][infra] NUMA topology, cpu pinning, hugepages tempest tests upstream or plugin

[Znoinski, Waldemar]

I'd like to invite everybody to collaborate around nfv feature testing in 
OpenStack in etherpad [1].



[1] https://etherpad.openstack.org/p/nfv-tests


From: Znoinski, Waldemar [mailto:waldemar.znoin...@intel.com]
Sent: Tuesday, November 8, 2016 12:26 PM
To: openstack...@lists.openstack.org; openstack-dev@lists.openstack.org; 
openstack-in...@lists.openstack.org
Subject: [openstack-dev] [openstack-infra][nova][tempest][qa][infra] NUMA 
topology, cpu pinning, hugepages tempest tests upstream or plugin

Hi all,

Due to recent discussions around Enhanced Platform Awareness (EPA) and their 
testing in OpenStack thinking was started to take what Intel NFV 3rd party CI 
[1] runs at this moment and merge some/all into upstream Tempest. Currently 
intel-nfv-ci-tests is a Tempest plugin [2] [3] and it's running on all Nova 
changes , sample [4]. Merging them with upstream Tempest would give testing 
environments an option to turn them on with a flip of a switch in tempest.conf 
rather than pip install  + tempest run with all-plugin (to enable 
site_packages).

While some of them may be easier from technical stand point (hugepages) some of 
them may not be possible in cloud providers used by OpenStack Infra.

Both options: Tempest plugin, upstream Tempest have pros and cos and we'd like 
to get broader community to comment on that.
If you have any feedback, suggestions, ideas please follow up here.


[1] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI
[2] https://github.com/openstack/intel-nfv-ci-tests
[3] http://docs.openstack.org/developer/tempest/plugin-registry.html
[4] 
http://intel-openstack-ci-logs.ovh/51/393951/2/check/tempest-dsvm-intel-nfv-xenial/2982905/

thanks
wznoinsk

--
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.
--
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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Nova-MultiJob CI (non-voting) request to comment

[Znoinski, Waldemar]

Hi Lenny, Matt et al,

We've touched the same NFV features testing topic on live-migration meeting 
today and apart a ML [1] post we'd invite everybody to collaborate around nfv 
tests in etherpad [2].

[1] 
http://lists.openstack.org/pipermail/openstack-dev/2016-November/106949.html 
[2] https://etherpad.openstack.org/p/nfv-tests 

 >-Original Message-
 >From: Lenny Verkhovsky [mailto:len...@mellanox.com]
 >Sent: Sunday, November 6, 2016 7:50 AM
 >To: OpenStack Development Mailing List (not for usage questions)
 >
 >Subject: Re: [openstack-dev] [nova] Nova-MultiJob CI (non-voting) request
 >to comment
 >
 >Matt, Chris,
 >Thanks, your filtering suggestion will be added when possible.
 >
 >> -Original Message-
 >> From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 >> Sent: Friday, November 04, 2016 9:42 PM
 >> To: openstack-dev@lists.openstack.org
 >> Subject: Re: [openstack-dev] [nova] Nova-MultiJob CI (non-voting)
 >> request to comment
 >>
 >> On 11/4/2016 2:04 AM, Lenny Verkhovsky wrote:
 >> > It uses 2 physical servers with 2 compute nodes And runs migration
 >> > tests only.
 >> > Other Mellanox CI jobs run on a single allinone server, thus
 >> > migration tests
 >> are skipped.
 >> >
 >>
 >> I think this was mentioned at the summit. In general we have a major
 >> gap in multinode testing for NFV features like PCI so this would be a
 >> welcome addition. As noted elsewhere there are other ares of nova to
 >> expand the coverage for this, like I'd recommend any changes to
 >> nova/compute/* and nova/network/* to be tested under this. But
 >> starting small makes sense.
 >>
 >> --
 >>
 >> Thanks,
 >>
 >> Matt Riedemann
 >>
 >>
 >>
 >__
 >> 
 >> OpenStack Development Mailing List (not for usage questions)
 >> Unsubscribe: OpenStack-dev-
 >> requ...@lists.openstack.org?subject:unsubscribe
 >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 >
 >__
 >
 >OpenStack Development Mailing List (not for usage questions)
 >Unsubscribe: OpenStack-dev-
 >requ...@lists.openstack.org?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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [openstack-infra][nova][tempest][qa][infra] NUMA topology, cpu pinning, hugepages tempest tests upstream or plugin

[Znoinski, Waldemar]

Hi all,

Due to recent discussions around Enhanced Platform Awareness (EPA) and their 
testing in OpenStack thinking was started to take what Intel NFV 3rd party CI 
[1] runs at this moment and merge some/all into upstream Tempest. Currently 
intel-nfv-ci-tests is a Tempest plugin [2] [3] and it's running on all Nova 
changes , sample [4]. Merging them with upstream Tempest would give testing 
environments an option to turn them on with a flip of a switch in tempest.conf 
rather than pip install  + tempest run with all-plugin (to enable 
site_packages).

While some of them may be easier from technical stand point (hugepages) some of 
them may not be possible in cloud providers used by OpenStack Infra.

Both options: Tempest plugin, upstream Tempest have pros and cos and we'd like 
to get broader community to comment on that.
If you have any feedback, suggestions, ideas please follow up here.


[1] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI
[2] https://github.com/openstack/intel-nfv-ci-tests
[3] http://docs.openstack.org/developer/tempest/plugin-registry.html
[4] 
http://intel-openstack-ci-logs.ovh/51/393951/2/check/tempest-dsvm-intel-nfv-xenial/2982905/

thanks
wznoinsk
--
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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Mirror issues with Intel NFV CI?

[Znoinski, Waldemar]

We've fixed the subnet pools issue and left all the jobs in non-voting for 
testing yesterday. There are issues with cinder volumes highlighted by tempest 
tests but we'll skip them for the time they're being trobuleshooted and we've 
put the jobs back to voting.

Thanks


 >-Original Message-
 >From: Znoinski, Waldemar
 >Sent: Tuesday, September 27, 2016 9:27 PM
 >To: OpenStack Development Mailing List (not for usage questions)
 >
 >Subject: RE: [openstack-dev] [nova] Mirror issues with Intel NFV CI?
 >
 >Hi Matt,
 >
 >Introduction of using subnetpools in devstack [1] is causing issues like
 >'Connection to proxy timed out. ' in our setup. We are working on it and
 >will update ML soon. Thanks for pinging.
 >
 >[1] https://review.openstack.org/#/c/356026/
 >
 >
 > >-Original Message-
 > >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 > >Sent: Tuesday, September 27, 2016 2:34 PM
 > >To: OpenStack Development Mailing List (not for usage questions)
 >>
 > >Subject: [openstack-dev] [nova] Mirror issues with Intel NFV CI?
 > >
 > >I'm seeing a pretty high failure rate with some of the Intel NFV CI jobs
 >today,  >the pattern looks like a pypi mirror issue getting packages to setup
 >tempest:
 > >
 > >http://intel-openstack-ci-logs.ovh/94/375894/2/check/tempest-dsvm-
 >intel-
 > >nfv-xenial/a0bffb3/logs/devstacklog.txt.gz
 > >
 > >2016-09-27 02:11:52.127 | Collecting hacking<0.12,>=0.11.0 (from -r
 >>/opt/stack/new/tempest/test-requirements.txt (line 4))
 > >2016-09-27 02:12:07.144 |   Retrying (Retry(total=4, connect=None,
 > >read=None, redirect=None)) after connection broken by
 >>'ConnectTimeoutError(V
 > >erifiedHTTPSConnection
 > >object at 0x7faca5b7fd10>, 'Connection to proxy.ir.intel.com timed out.
 > >(connect timeout=15)')': /simple/hacking/
 > >2016-09-27 02:12:22.654 |   Retrying (Retry(total=3, connect=None,
 > >read=None, redirect=None)) after connection broken by
 >>'ConnectTimeoutError(V
 > >erifiedHTTPSConnection
 > >object at 0x7faca5b7fe10>, 'Connection to proxy.ir.intel.com timed out.
 > >(connect timeout=15)')': /simple/hacking/
 > >2016-09-27 02:12:38.657 |   Retrying (Retry(total=2, connect=None,
 > >read=None, redirect=None)) after connection broken by
 >>'ConnectTimeoutError(V
 > >erifiedHTTPSConnection
 > >object at 0x7faca5b7ff10>, 'Connection to proxy.ir.intel.com timed out.
 > >(connect timeout=15)')': /simple/hacking/
 > >2016-09-27 02:12:55.674 |   Retrying (Retry(total=1, connect=None,
 > >read=None, redirect=None)) after connection broken by
 >>'ConnectTimeoutError(V
 > >erifiedHTTPSConnection
 > >object at 0x7faca59e9050>, 'Connection to proxy.ir.intel.com timed out.
 > >(connect timeout=15)')': /simple/hacking/
 > >2016-09-27 02:13:14.682 |   Retrying (Retry(total=0, connect=None,
 > >read=None, redirect=None)) after connection broken by
 >>'ConnectTimeoutError(V
 > >erifiedHTTPSConnection
 > >object at 0x7faca59e9150>, 'Connection to proxy.ir.intel.com timed out.
 > >(connect timeout=15)')': /simple/hacking/
 > >2016-09-27 02:13:29.687 |   Could not find a version that satisfies the
 > >requirement hacking<0.12,>=0.11.0 (from -r
 >/opt/stack/new/tempest/test-  >requirements.txt (line 4)) (from versions: )
 > >2016-09-27 02:13:29.687 | No matching distribution found for
 > >hacking<0.12,>=0.11.0 (from -r
 > >/opt/stack/new/tempest/test-requirements.txt (line 4))  >  >Is this a
 >known issue that the CI maintainers are fixing?
 > >
 > >--
 > >
 > >Thanks,
 > >
 > >Matt Riedemann
 > >
 > >
 >
 >>_
 >_
 > >
 > >OpenStack Development Mailing List (not for usage questions)
 > >Unsubscribe: OpenStack-dev-
 > >requ...@lists.openstack.org?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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Mirror issues with Intel NFV CI?

[Znoinski, Waldemar]

Hi Matt,

Introduction of using subnetpools in devstack [1] is causing issues like 
'Connection to proxy timed out. ' in our setup. We are working on it and 
will update ML soon. Thanks for pinging.

[1] https://review.openstack.org/#/c/356026/


 >-Original Message-
 >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 >Sent: Tuesday, September 27, 2016 2:34 PM
 >To: OpenStack Development Mailing List (not for usage questions)
 >
 >Subject: [openstack-dev] [nova] Mirror issues with Intel NFV CI?
 >
 >I'm seeing a pretty high failure rate with some of the Intel NFV CI jobs 
 >today,
 >the pattern looks like a pypi mirror issue getting packages to setup tempest:
 >
 >http://intel-openstack-ci-logs.ovh/94/375894/2/check/tempest-dsvm-intel-
 >nfv-xenial/a0bffb3/logs/devstacklog.txt.gz
 >
 >2016-09-27 02:11:52.127 | Collecting hacking<0.12,>=0.11.0 (from -r
 >/opt/stack/new/tempest/test-requirements.txt (line 4))
 >2016-09-27 02:12:07.144 |   Retrying (Retry(total=4, connect=None,
 >read=None, redirect=None)) after connection broken by
 >'ConnectTimeoutError(erifiedHTTPSConnection
 >object at 0x7faca5b7fd10>, 'Connection to proxy.ir.intel.com timed out.
 >(connect timeout=15)')': /simple/hacking/
 >2016-09-27 02:12:22.654 |   Retrying (Retry(total=3, connect=None,
 >read=None, redirect=None)) after connection broken by
 >'ConnectTimeoutError(erifiedHTTPSConnection
 >object at 0x7faca5b7fe10>, 'Connection to proxy.ir.intel.com timed out.
 >(connect timeout=15)')': /simple/hacking/
 >2016-09-27 02:12:38.657 |   Retrying (Retry(total=2, connect=None,
 >read=None, redirect=None)) after connection broken by
 >'ConnectTimeoutError(erifiedHTTPSConnection
 >object at 0x7faca5b7ff10>, 'Connection to proxy.ir.intel.com timed out.
 >(connect timeout=15)')': /simple/hacking/
 >2016-09-27 02:12:55.674 |   Retrying (Retry(total=1, connect=None,
 >read=None, redirect=None)) after connection broken by
 >'ConnectTimeoutError(erifiedHTTPSConnection
 >object at 0x7faca59e9050>, 'Connection to proxy.ir.intel.com timed out.
 >(connect timeout=15)')': /simple/hacking/
 >2016-09-27 02:13:14.682 |   Retrying (Retry(total=0, connect=None,
 >read=None, redirect=None)) after connection broken by
 >'ConnectTimeoutError(erifiedHTTPSConnection
 >object at 0x7faca59e9150>, 'Connection to proxy.ir.intel.com timed out.
 >(connect timeout=15)')': /simple/hacking/
 >2016-09-27 02:13:29.687 |   Could not find a version that satisfies the
 >requirement hacking<0.12,>=0.11.0 (from -r /opt/stack/new/tempest/test-
 >requirements.txt (line 4)) (from versions: )
 >2016-09-27 02:13:29.687 | No matching distribution found for
 >hacking<0.12,>=0.11.0 (from -r
 >/opt/stack/new/tempest/test-requirements.txt (line 4))
 >
 >Is this a known issue that the CI maintainers are fixing?
 >
 >--
 >
 >Thanks,
 >
 >Matt Riedemann
 >
 >
 >__
 >
 >OpenStack Development Mailing List (not for usage questions)
 >Unsubscribe: OpenStack-dev-
 >requ...@lists.openstack.org?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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

[Znoinski, Waldemar]

We’ll disable testing on nova stable/liberty till I have a moment to look into 
the problem(s) properly – should happen in next few days.
CI had some trouble on stable/mitaka for a moment couple of weeks back but it’s 
fixed since.

From: Znoinski, Waldemar
Sent: Monday, August 22, 2016 9:17 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: RE: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

I’ll have a look.

From: Timofei Durakov [mailto:tdura...@mirantis.com]
Sent: Monday, August 22, 2016 8:03 PM
To: OpenStack Development Mailing List (not for usage questions) 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

Hi everyone,

got a question on that Intel NFV CI: has statistics for stable branches been 
checked either?
I have a patch to stable/liberty [1] that failed on all Intel NFV CI jobs 2 
times in a row. Who could help me to figure out the root cause for that?

Thanks in advance,
Timofey.

[1] - https://review.openstack.org/#/c/358439/

On Mon, Aug 8, 2016 at 6:27 PM, Ptacek, MichalX 
mailto:michalx.pta...@intel.com>> wrote:
Change deployed,
Thanks for your comments,

Michal

-Original Message-
From: Markus Zoeller 
[mailto:mzoel...@linux.vnet.ibm.com<mailto:mzoel...@linux.vnet.ibm.com>]
Sent: Monday, August 08, 2016 3:15 PM
To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

On 03.08.2016 22:02, Znoinski, Waldemar wrote:
> Thanks
> Much appreciated
>
> Making use of the opportunity here... what's the next big thing a CI
> (like one testing NFV) should be doing? (multinode or there's
> something else more important?)

Two tiny nits on the comment the CI is giving a change:

"Build failed (check pipeline). To recheck leave a comment with
intel-nfv-ci recheck. For more info go to
https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-NFV-CI.";

1) Could you put the recheck command in quotation? Like:
   To recheck leave a comment with 'intel-nfv-ci recheck'.
2) The link to the wiki seems to be wrong (hyphen vs. underscore):
   https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI

--
Regards, Markus Zoeller (markus_z)

>  >-Original Message-
>  >From: Matt Riedemann 
> [mailto:mrie...@linux.vnet.ibm.com<mailto:mrie...@linux.vnet.ibm.com>]
>  >Sent: Wednesday, August 3, 2016 8:28 PM
>  >To: 
> openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
>  >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting
> permission  >  >On 8/3/2016 8:18 AM, Znoinski, Waldemar wrote:
>  >> [WZ] Hi Matt, do we need, a Gerrit-style, +2 on that from someone?
>  >> Infra Team doesn't keep these settings in their puppet/config
> files on git -  >all the Gerrit changes are done via Gerrit GUI so
> they rely on Cores to add CIs  >to the appropriate ci group, nova-ci in this 
> case.
>  >>
>  >>
>  >
>  >Sorry, I wasn't sure what the next step here was, I guess it was the
> nova-ci  >membership change, which is done now:
>  >
>  >https://review.openstack.org/#/admin/groups/511,members
>  >
>  >--
>  >
>  >Thanks,
>  >
>  >Matt Riedemann
>  >
>  >
>  >__
>  >
>  >OpenStack Development Mailing List (not for usage questions)
>  >Unsubscribe: OpenStack-dev-
>  
> >requ...@lists.openstack.org?subject:unsubscribe<http://requ...@lists.openstack.org?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:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>




__
OpenStack Development Mailing L

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

[Znoinski, Waldemar]

I’ll have a look.

From: Timofei Durakov [mailto:tdura...@mirantis.com]
Sent: Monday, August 22, 2016 8:03 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

Hi everyone,

got a question on that Intel NFV CI: has statistics for stable branches been 
checked either?
I have a patch to stable/liberty [1] that failed on all Intel NFV CI jobs 2 
times in a row. Who could help me to figure out the root cause for that?

Thanks in advance,
Timofey.

[1] - https://review.openstack.org/#/c/358439/

On Mon, Aug 8, 2016 at 6:27 PM, Ptacek, MichalX 
mailto:michalx.pta...@intel.com>> wrote:
Change deployed,
Thanks for your comments,

Michal

-Original Message-
From: Markus Zoeller 
[mailto:mzoel...@linux.vnet.ibm.com<mailto:mzoel...@linux.vnet.ibm.com>]
Sent: Monday, August 08, 2016 3:15 PM
To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

On 03.08.2016 22:02, Znoinski, Waldemar wrote:
> Thanks
> Much appreciated
>
> Making use of the opportunity here... what's the next big thing a CI
> (like one testing NFV) should be doing? (multinode or there's
> something else more important?)

Two tiny nits on the comment the CI is giving a change:

"Build failed (check pipeline). To recheck leave a comment with
intel-nfv-ci recheck. For more info go to
https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-NFV-CI.";

1) Could you put the recheck command in quotation? Like:
   To recheck leave a comment with 'intel-nfv-ci recheck'.
2) The link to the wiki seems to be wrong (hyphen vs. underscore):
   https://wiki.openstack.org/wiki/ThirdPartySystems/Intel_NFV_CI

--
Regards, Markus Zoeller (markus_z)

>  >-Original Message-
>  >From: Matt Riedemann 
> [mailto:mrie...@linux.vnet.ibm.com<mailto:mrie...@linux.vnet.ibm.com>]
>  >Sent: Wednesday, August 3, 2016 8:28 PM
>  >To: 
> openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
>  >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting
> permission  >  >On 8/3/2016 8:18 AM, Znoinski, Waldemar wrote:
>  >> [WZ] Hi Matt, do we need, a Gerrit-style, +2 on that from someone?
>  >> Infra Team doesn't keep these settings in their puppet/config
> files on git -  >all the Gerrit changes are done via Gerrit GUI so
> they rely on Cores to add CIs  >to the appropriate ci group, nova-ci in this 
> case.
>  >>
>  >>
>  >
>  >Sorry, I wasn't sure what the next step here was, I guess it was the
> nova-ci  >membership change, which is done now:
>  >
>  >https://review.openstack.org/#/admin/groups/511,members
>  >
>  >--
>  >
>  >Thanks,
>  >
>  >Matt Riedemann
>  >
>  >
>  >__
>  >
>  >OpenStack Development Mailing List (not for usage questions)
>  >Unsubscribe: OpenStack-dev-
>  
> >requ...@lists.openstack.org?subject:unsubscribe<http://requ...@lists.openstack.org?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:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?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-ma

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

[Znoinski, Waldemar]

Thanks
Much appreciated

Making use of the opportunity here... what's the next big thing a CI (like one 
testing NFV) should be doing? (multinode or there's something else more 
important?)

 >-Original Message-
 >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 >Sent: Wednesday, August 3, 2016 8:28 PM
 >To: openstack-dev@lists.openstack.org
 >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission
 >
 >On 8/3/2016 8:18 AM, Znoinski, Waldemar wrote:
 >> [WZ] Hi Matt, do we need, a Gerrit-style, +2 on that from someone?
 >> Infra Team doesn't keep these settings in their puppet/config files on git -
 >all the Gerrit changes are done via Gerrit GUI so they rely on Cores to add 
 >CIs
 >to the appropriate ci group, nova-ci in this case.
 >>
 >>
 >
 >Sorry, I wasn't sure what the next step here was, I guess it was the nova-ci
 >membership change, which is done now:
 >
 >https://review.openstack.org/#/admin/groups/511,members
 >
 >--
 >
 >Thanks,
 >
 >Matt Riedemann
 >
 >
 >__
 >
 >OpenStack Development Mailing List (not for usage questions)
 >Unsubscribe: OpenStack-dev-
 >requ...@lists.openstack.org?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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

[Znoinski, Waldemar]

 >-Original Message-
 >From: Znoinski, Waldemar [mailto:waldemar.znoin...@intel.com]
 >Sent: Monday, August 1, 2016 6:52 PM
 >To: OpenStack Development Mailing List (not for usage questions)
 >
 >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission
 >
 >
 > >-Original Message-
 > >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 > >Sent: Friday, July 29, 2016 6:37 PM
 > >To: openstack-dev@lists.openstack.org
 > >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission
 >>  >On 7/29/2016 10:47 AM, Znoinski, Waldemar wrote:
 > >> 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:mrie...@linux.vnet.ibm.com]
 > >>  >Sent: Thursday, July 28, 2016 4:14 PM  >>  >To: openstack-
 >d...@lists.openstack.org  >>  >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
 > 

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

[Znoinski, Waldemar]

 >-Original Message-
 >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 >Sent: Friday, July 29, 2016 6:37 PM
 >To: openstack-dev@lists.openstack.org
 >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission
 >
 >On 7/29/2016 10:47 AM, Znoinski, Waldemar wrote:
 >> 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:mrie...@linux.vnet.ibm.com]
 >>  >Sent: Thursday, July 28, 2016 4:14 PM
 >>  >To: openstack-dev@lists.openstack.org
 >>  >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  >> b

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

[Znoinski, Waldemar]

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:mrie...@linux.vnet.ibm.com]
 >Sent: Thursday, July 28, 2016 4:14 PM
 >To: openstack-dev@lists.openstack.org
 >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:
 >> openstack-dev-requ...@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
 

[openstack-dev] [nova] [infra] Intel NFV CI voting permission

[Znoinski, Waldemar]

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
 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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Intel NFV CI failing all shelve/unshelve tests

[Znoinski, Waldemar]

Hi all,

I'll disable the shelve/unshelve failing tests in Intel NFV CI for the time 
being till we have clarity on the problem.
Stephen Finucane will be working on that in next week or so.

 >-Original Message-
 >From: Chris Friesen [mailto:chris.frie...@windriver.com]
 >Sent: Wednesday, May 25, 2016 5:40 PM
 >To: openstack-dev@lists.openstack.org
 >Subject: Re: [openstack-dev] [nova] Intel NFV CI failing all shelve/unshelve
 >tests
 >
 >On 05/22/2016 05:41 PM, Jay Pipes wrote:
 >> Hello Novaites,
 >>
 >> I've noticed that the Intel NFV CI has been failing all test runs for
 >> quite some time (at least a few days), always failing the same tests
 >> around shelve/unshelve operations.
 >
 >
 >
 >> I looked through the conductor and compute logs to see if I could find
 >> any possible reasons for the errors and found a number of the
 >> following errors in the compute logs:
 >>
 >> 2016-05-22 22:18:59.403 8145 ERROR nova.compute.manager [instance:
 >> cae6fd47-0968-4922-a03e-3f2872e4eb52] Traceback (most recent call last):
 >> 2016-05-22 22:18:59.403 8145 ERROR nova.compute.manager [instance:
 >> cae6fd47-0968-4922-a03e-3f2872e4eb52]   File
 >> "/opt/stack/new/nova/nova/compute/manager.py", line 4230, in
 >> _unshelve_instance
 >> 2016-05-22 22:18:59.403 8145 ERROR nova.compute.manager [instance:
 >> cae6fd47-0968-4922-a03e-3f2872e4eb52] with rt.instance_claim(context,
 >> instance, limits):
 >
 >
 >
 >> 2016-05-22 22:18:59.403 8145 ERROR nova.compute.manager [instance:
 >> cae6fd47-0968-4922-a03e-3f2872e4eb52]
 >newcell.unpin_cpus(pinned_cpus)
 >> 2016-05-22 22:18:59.403 8145 ERROR nova.compute.manager [instance:
 >> cae6fd47-0968-4922-a03e-3f2872e4eb52]   File
 >> "/opt/stack/new/nova/nova/objects/numa.py", line 94, in unpin_cpus
 >> 2016-05-22 22:18:59.403 8145 ERROR nova.compute.manager [instance:
 >> cae6fd47-0968-4922-a03e-3f2872e4eb52] pinned=list(self.pinned_cpus))
 >> 2016-05-22 22:18:59.403 8145 ERROR nova.compute.manager [instance:
 >> cae6fd47-0968-4922-a03e-3f2872e4eb52] CPUPinningInvalid: Cannot
 >> pin/unpin cpus [6] from the following pinned set [0, 2, 4]
 >>
 >> on or around the time of the failures in Tempest.
 >>
 >> Perhaps tomorrow morning we can look into handling the above exception
 >> properly from the compute manager, since clearly we shouldn't be
 >> allowing CPUPinningInvalid to be raised in the resource tracker's
 >_update_usage() call
 >
 >First, it seems wrong to me that an _unshelve_instance() call would result in
 >unpinning any CPUs.  If the instance was using pinned CPUs then I would
 >expect the CPUs to be unpinned when doing the "shelve" operation.  When
 >we do an instance claim as part of the "unshelve" operation we should be
 >pinning CPUs, not unpinning them.
 >
 >Second, the reason why CPUPinningInvalid gets raised in _update_usage() is
 >that it has discovered an inconsistency in its view of resources.  In this 
 >case,
 >it's trying to unpin CPU 6 from a set of pinned cpus that doesn't include CPU
 >6.  I think this is a valid concern and should result in an error log.  
 >Whether it
 >should cause the unshelve operation to fail is a separate question, but it's
 >definitely a symptom that something is wrong with resource tracking on this
 >compute node.
 >
 >Chris
 >
 >
 >__
 >
 >OpenStack Development Mailing List (not for usage questions)
 >Unsubscribe: OpenStack-dev-
 >requ...@lists.openstack.org?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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] [infra] resolving issues with Intel NFV CI

[Znoinski, Waldemar]

The issue is now resolved.

Apparently the job wasn't registered with gearman server as there weren't any 
slaves available in Jenkins to run it at the time of zuul restart (as some old 
nodepool nodes were left over and no new VMs were spawned).



From: Znoinski, Waldemar [mailto:waldemar.znoin...@intel.com]
Sent: Tuesday, May 24, 2016 9:31 AM
To: openstack-in...@lists.openstack.org; OpenStack Development Mailing List 
(not for usage questions) 
Subject: [openstack-dev] [nova] [infra] resolving issues with Intel NFV CI

Hi all,

There is an issue with jobs under Intel NFV CI not being registered.
The issue is currently being investigated. ThirdPartySystems Wiki was updated.

Updates to follow.


Waldemar Znoinski


--
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.
--
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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova] [infra] resolving issues with Intel NFV CI

[Znoinski, Waldemar]

Hi all,

There is an issue with jobs under Intel NFV CI not being registered.
The issue is currently being investigated. ThirdPartySystems Wiki was updated.

Updates to follow.


Waldemar Znoinski

--
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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what does it test?

[Znoinski, Waldemar]

 >-Original Message-
 >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
 >Sent: Wednesday, March 30, 2016 4:22 PM
 >To: OpenStack Development Mailing List (not for usage questions)
 >
 >Cc: Feng, Shaohe 
 >Subject: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what
 >does it test?
 >
 >Intel has a few third party CIs in the third party systems wiki [1].
 >
 >I was talking with Moshe Levi today about expanding coverage for mellanox
 >CI in nova, today they run an SRIOV CI for vnic type 'direct'.
 >I'd like them to also start running their 'macvtap' CI on the same nova
 >changes (that job only runs in neutron today I think).
 >
 >I'm trying to see what we have for coverage on these different NFV
 >configurations, and because of limited resources to run NFV CI, don't want to
 >duplicate work here.
 >
 >So I'm wondering what the various Intel NFV CI jobs run, specifically the 
 >Intel
 >Networking CI [2], Intel NFV CI [3] and Intel SRIOV CI [4].
[WZ] See comments below about full/small wiki but would the below is enough or 
you'd want or to see more:
- networking-ci runs (with exceptions): 
tempest.api.network 
tempest.scenario.test_network_basic_ops 

- nfv-ci runs (with exceptions):
tempest.api.compute on standard flavors with NFV features enabled
tempest.scenario (including intel-nfv-ci-tests - 
https://github.com/openstack/intel-nfv-ci-tests) on standard flavors with NFV 
features enabled

>
 > From the wiki it looks like the Intel Networking CI tests ovs-dpdk but only 
 > for
 >Neutron. Could that be expanded to also test on Nova changes that hit a sub-
 >set of the nova tree?
[WZ] Yes, Networking CI is for neutron to test ovs-dpdk. It was also configured 
to trigger on openstack/nova changes when they affect nova/virt/libvirt/vif.py. 
It's currently disabled due to issue with Jenkins plugin we're seeing when 
having two jobs pointing at the same project simultaneously which causes to 
missed comments. Example [5]. We're still investigating one last option to get 
it working properly with the current setup. Even if we fail we're currently 
migrating to new CI setup (Openstack Infra's downstream-ci suite) and we'll 
reenable that ovs-dpdk testing on nova changes once we're migrated, 6 - 8 weeks 
from now.
Is there more you feel we should be testing our ovs-dpdk on when it comes to 
nova changes?

 >
 >I really don't know what the latter two jobs test as far as configuration is
 >concerned, the descriptions in the wikis are pretty empty (please update
 >those to be more specific).
[WZ] I see some CIs have a full wiki pages [6] for their CIs apart from the 
usual shim wiki overview table [7]. Is that what you're suggesting or extended 
info about tests in the 'small' wiki [2] is ok? 

 >
 >Please also include in the wiki the recheck method for each CI so I don't have
 >to dig through Gerrit comments to find one.
[WZ] Done

 >
 >[1] https://wiki.openstack.org/wiki/ThirdPartySystems
 >[2] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-Networking-CI
 >[3] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-NFV-CI
 >[4] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-SRIOV-CI
[5] https://review.openstack.org/#/c/294312 
[6] https://wiki.openstack.org/wiki/PowerKVM 
[7] https://wiki.openstack.org/wiki/ThirdPartySystems/IBMPowerKVMCI 
 >
 >--
 >
 >Thanks,
 >
 >Matt Riedemann
[WZ] thanks
>
 >
 >__
 >
 >OpenStack Development Mailing List (not for usage questions)
 >Unsubscribe: OpenStack-dev-
 >requ...@lists.openstack.org?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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] [infra] The same SRIOV / NFV CI failures missed a regression, why?

[Znoinski, Waldemar]

 >-Original Message-
 >From: Monty Taylor [mailto:mord...@inaugust.com]
 >Sent: Saturday, March 26, 2016 3:27 PM
 >To: openstack-dev@lists.openstack.org
 >Subject: Re: [openstack-dev] [nova] [infra] The same SRIOV / NFV CI failures
 >missed a regression, why?
 >
 >On 03/25/2016 03:52 PM, Jeremy Stanley wrote:
 >> On 2016-03-25 16:33:44 -0400 (-0400), Jay Pipes wrote:
 >> [...]
 >>> What I'm proposing isn't using or needing a custom OpenStack
 >>> deployment. There's nothing non-standard at all about the PCI or NFV
 >>> stuff besides the hardware required to functionally test it.
 >>
 >> What you _are_ talking about though is maintaining physical servers in
 >> a data center running an OpenStack environment (and if you want it
 >> participating in gating/preventing changes from merging you need more
 >> than one environment so we don't completely shutdown development
 >when
 >> one of them collapses). This much has been a challenge for the TripleO
 >> team, such that the jobs running for them are still not voting on
 >> their changes.
 >>
 >>> What we're talking about here is using the same upstream Infra Puppet
 >>> modules, installed on a long-running server in a lab that can
 >>> interface with upstream Gerrit, respond to new change events in the
 >>> Gerrit stream, and trigger devstack-gate[-like] builds on some
 >>> bare-metal gear.
 >>
 >> It's possible I'm misunderstanding you... you're talking about
 >> maintaining a deployment of OpenStack with specific hardware to be
 >> able to run these jobs in, right? That's not as trivial an effort as
 >> it sounds, and I'm skeptical "a couple of operators" is sufficient to
 >> sustain such an endeavor.
 >
 >Two things:
 >
 >- Rhere is no current concept of "a long-lived machine running that we run
 >devstack on from time to time" - everything in Infra is designed around using
 >OpenStack APIs to get compute resources. So if we want to run jobs on
 >hardware in this lab, as it stands right now, that hardware would need to be
 >provided by Ironic+Nova.
 >
 >Last time we did the math (and Jim can maybe correct my numbers) in order
 >to keep up with the demand similar to our VM environments, I believe such
 >an env would need at least 83 Ironic nodes. And as Jeremy said, we'd need at
 >least 2 envs for redundancy - so in looking at getting it funded, looking for
 >approximately 200 machines is likely about right.
[WZ] Could you share the formula and data for this? What projects/events/jobs 
and their times you were taking into calculations?

 >
 >- zuul v3 does introduce the concept of statically available resources that 
 >can
 >be checked out of nodepool - specifically to address the question of people
 >wanting to use long-lived servers as test resources for things. The machine
 >count is still likely to remain static - but once we have zuul v3 out, it 
 >might
 >reduce the need for the operators to operate 2 100-node Ironic-based
 >OpenStack clouds. (This implies that help with zuul v3 might be seen as an
 >accelerant to this project)
 >
 >Also keep in mind, if/when resources are sought out, that every underlying
 >OS config would double the amount of resources. So if we got
 >2 sets of 100 nodes to start with, and started running NFV config'd devstack
 >tests on them on ubuntu trusty, and then our friends at RedHat request that
 >we test the same on a RH-baed distro, the cost for that would be an
 >additional 100 nodes in each DC.
 >
 >>> Is that something that is totally out of the question for the
 >>> upstream Infra team to be a guide for?
 >>
 >> We've stated in the past that we're willing to accept this level of
 >> integration as long as our requirements for redundancy/uptime are met.
 >> We mostly just don't want to see issues with the environment block
 >> development for projects relying on it because it's the only place
 >> those jobs can run, so multiple environments in different data centers
 >> would be a necessity (right now our gating jobs are able to run in any
 >> of 9 regions from 6 providers, which mitigates this risk).
 >>
 >
 >
 >__
 >
 >OpenStack Development Mailing List (not for usage questions)
 >Unsubscribe: OpenStack-dev-
 >requ...@lists.openstack.org?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 questi

Re: [openstack-dev] [nova][infra] The same SRIOV / NFV CI failures missed a regression, why?

[Znoinski, Waldemar]

Hi Jay, Matt, Levi et al,

The Intel NFV CI problems were fixed last week.
Also, I think if the CIs would have voting right it would attract more 
attention.

I'd be happy to work with OpenStack Infra team on getting our NFV CI the voting 
level/rights. To do it right, though, it'd be great to have some form of SLA. 
This would help maintaining only the 3rdparty CIs that meet the SLA voting. Is 
there one or discussed? I'd imagine there would be a need for one anyways if 
we'd go with Jay's proposal of collocated hardware/engineers.

Waldek

 >-Original Message-
 >From: Moshe Levi [mailto:mosh...@mellanox.com]
 >Sent: Tuesday, March 29, 2016 8:41 AM
 >To: OpenStack Development Mailing List (not for usage questions)
 >
 >Subject: Re: [openstack-dev] [nova] The same SRIOV / NFV CI failures missed
 >a regression, why?
 >
 >
 >
 >> -Original Message-
 >> From: Jay Pipes [mailto:jaypi...@gmail.com]
 >> Sent: Friday, March 25, 2016 10:20 PM
 >> To: openstack-dev@lists.openstack.org
 >> Subject: Re: [openstack-dev] [nova] The same SRIOV / NFV CI failures
 >> missed a regression, why?
 >>
 >> On 03/24/2016 09:35 AM, Matt Riedemann wrote:
 >> > We have another mitaka-rc-potential bug [1] due to a regression when
 >> > detaching SR-IOV interfaces in the libvirt driver.
 >> >
 >> > There were two NFV CIs that ran on the original change [2].
 >> >
 >> > Both failed with the same devstack setup error [3][4].
 >> >
 >> > So it sucks that we have a regression, it sucks that no one watched
 >> > for those CI results before approving the change, and it really
 >> > sucks in this case since it was specifically reported from mellanox
 >> > for sriov which failed in [4]. But it happens.
 >> >
 >> > What I'd like to know is, have the CI problems been fixed? There is
 >> > a change up to fix the regression [5] and this time the Mellanox CI
 >> > check is passing [6]. The Intel NFV CI hasn't reported, but with the
 >> > mellanox one also testing the suspend scenario, it's probably good
 >enough.
 >>
 >>  From the commit message of the original patch that introduced the
 >> regression:
 >>
 >> "This fix was tested on a real environment containing the above type of
 >VMs.
 >> test_driver.test_detach_sriov_ports was slightly modified so that the
 >> VIF from which data is sent to _detach_pci_devices will contain the
 >> correct SRIOV values (pci_slot, vlan and hw_veb VIF type)"
 >>
 >> I'm not sure if the above statement could ever have been true
 >> considering the AttributeError that occurred in the bug...
 >>
 >> In any case, I think that it's pretty clear that the CI systems for
 >> NFV and PCI have been less than reliable at functionally testing the
 >> PCI and NFV-specific functionality in Nova.
 >>
 >> This isn't trying to put down the people that work on those systems --
 >> I know first hand that it can be difficult to build and maintain CI
 >> systems that report in to upstream, and I appreciate the effort that goes
 >into this.
 >>
 >> But, going forward, I think we need to do something as a concerned
 >> community.
 >>
 >> How about this for a proposal?
 >>
 >> 1) We establish a joint lab environment that contains heterogeneous
 >> hardware to which all interested hardware vendors must provide
 >hardware.
 >>
 >> 2) The OpenStack Foundation and the hardware vendors each foot some
 >> portion of the bill to hire 2 or more systems administrators to
 >> maintain this lab environment.
 >>
 >> 3) The upstream Infrastructure team works with the hired system
 >> administrators to create a single CI system that can spawn functional
 >> test jobs on the lab hardware and report results back to upstream
 >> Gerrit
 >>
 >> Given the will to do this, I think the benefits of more trusted
 >> testing results for the PCI and SR-IOV/NFV areas would more than make up
 >for the cost.
 >+1 I like this proposal. We can help by providing Mellanox hardware and
 >share our CI knowledge.
 >
 >>
 >> Best,
 >> -jay
 >>
 >>
 >__
 >__
 >> __
 >> OpenStack Development Mailing List (not for usage questions)
 >> Unsubscribe:
 >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 >
 >__
 >
 >OpenStack Development Mailing List (not for usage questions)
 >Unsubscribe: OpenStack-dev-
 >requ...@lists.openstack.org?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 inten

Re: [openstack-dev] [kuryr] gerrit/git review problem error code 10061

[Znoinski, Waldemar]

Hi Baohua
If you have a socks proxy to hand then you could check ‘tsocks’ - 
http://tsocks.sourceforge.net/ or check your distro’s package manager.
It’s quite ‘transparent’ proxying (over socks 4 or 5) of pretty much any 
process you run with it, i.e.:

tsocks scp -P29418 
yangbao...@review.openstack.org:hooks/commit-msg
> .git\hooks\commit-msg"

From: Baohua Yang [mailto:yangbao...@gmail.com]
Sent: Wednesday, November 11, 2015 2:15 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [kuryr] gerrit/git review problem error code 10061

Thanks to all!
It seems network connectivity problem. How sad again!  :(
i will try other ways.

On Tue, Nov 10, 2015 at 12:52 AM, Jeremy Stanley 
mailto:fu...@yuggoth.org>> wrote:
On 2015-11-09 10:13:33 +0800 (+0800), Baohua Yang wrote:
> Anyone recently meet such problem after cloning the latest code
> from kuryr? Try proxy also, but not solved.
[...]
> The following command failed with exit code 1
> "scp -P29418 
> yangbao...@review.openstack.org:hooks/commit-msg
> .git\hooks\commit-msg"
> ---
> FATAL: Unable to connect to relay host, errno=10061
> ssh_exchange_identification: Connection closed by remote host
[...]

I've checked our Gerrit SSH API authentication logs from the past 30
days and find no record of any yangbaohua authenticating. Chances
are this is a broken local proxy or some sort of intercepting
firewall which is preventing your 29418/tcp connection from even
reaching review.openstack.org.

If you use Telnet or NetCat to connect to port 29418 on
review.openstack.org directly, do you see an SSH 
banner starting
with a string like "SSH-2.0-GerritCodeReview_2.8.4-19-g4548330
(SSHD-CORE-0.9.0.201311081)" or something else?
--
Jeremy Stanley

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Best wishes!
Baohua
--
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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [infra] Try to introduce RFC mechanism to CI.

[Znoinski, Waldemar]

 >-Original Message-
 >From: Jeremy Stanley [mailto:fu...@yuggoth.org]
 >Sent: Friday, October 9, 2015 1:17 PM
 >To: OpenStack Development Mailing List (not for usage questions)
 >
 >Subject: Re: [openstack-dev] [infra] Try to introduce RFC mechanism to CI.
 >
 >On 2015-10-09 18:06:55 +0800 (+0800), Tang Chen wrote:
 >[...]
 >> It is just a waste of resource if reviewers are discussing about where
 >> this function should be, or what the function should be named. After
 >> all these details are agreed on, run the CI.
 >[...]
 
[WZ] I'm maintaining 2 3rdparty CIs here, for Nova and Neutron each, and to me 
there's no big difference in maintaining/supporting a CI that runs 5 or 150 
times a day. The only difference may be in resources required to keep up with 
the Gerrit stream. In my opinion (3rdparty) CIs should help early-discover the 
problems so should run on all patchsets as they appear - that's their main 
purpose to me.

 >As one of the people maintaining the upstream CI and helping coordinate our
 >resources/quotas, I don't see that providing early test feedback is a waste.
 >We're steadily increasing the instance quotas available to us, so check
 >pipeline utilization should continue to become less and less of a concern
 >anyway.
 >
 >For a change which is still under debate, feel free to simply ignore test 
 >results
 >until you get it to a point where you see them start to become relevant.
 >--
 >Jeremy Stanley
 >
 >__
 >
 >OpenStack Development Mailing List (not for usage questions)
 >Unsubscribe: OpenStack-dev-
 >requ...@lists.openstack.org?subject:unsubscribe
 >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova][infra] Intel NFV CI, testing hugepages, numa topology, cpu pinning

[Znoinski, Waldemar]

Hi cores et al,

As discussed briefly with Jay Pipes in Vancouver, we were about to provide CI 
and tests for features such as: hugepages, cpu pinning, numa topology. We since 
worked on NFV CI here at Intel. The work on the CI and tests is now completed.

A few details about the CI and tests.
* CI WIKI [1]
* last issues with the tests[2] were resolved two weeks ago and the CI is 
stable since
* currently the CI is NOT commenting back to Gerrit
* changes and artifacts samples below[3]
* Intel NFV CI is based on the infrastructure used by Intel Networking CI [4] - 
see comments left by this CI for comment form and content


[1] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-NFV-CI
[2] https://github.com/stackforge/intel-nfv-ci-tests
[3]
https://review.openstack.org/#/c/115484/ , 
http://intel-openstack-ci-logs.ovh/compute-ci/refs/changes/84/115484/28/
https://review.openstack.org/#/c/228168/ , 
http://intel-openstack-ci-logs.ovh/compute-ci/refs/changes/68/228168/2/
https://review.openstack.org/#/c/227138/ , 
http://intel-openstack-ci-logs.ovh/compute-ci/refs/changes/38/227138/3

[4] 
https://review.openstack.org/#/q/reviewer:%22Intel+Networking+CI+%253Copenstack-networking-ci%2540intel.com%253E%22,n,z

Unless there are  doubt and/or blockers we'd like to enable our CI commenting 
back with results and links to Nova in Openstack Gerrit.
All feedback welcome. I'll be attending Nova meeting this Thurs 1400 UTC for 
any follow ups as well.


Thanks
Waldek

--
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-infra][Infra][Neutron] Nominating intel-networking-ci for voting rights

[Znoinski, Waldemar]

Hi Kyle, Neutron Cores and Infra Team,


a)  Was there a final decision/conclusion on the matter?

b)  Do we make jodavidg’s suggestion[1] a rule and we change it in Neutron 
third party policy[2].

c)   I can’t see any recent changes in policy[2] and if there are no plans 
to change the guidelines on how/whether to get voting rights Infra please 
continue with the setup of the voting rights for Intel Networking CI. I’ll 
disable -1 voting depending on b).

[1] http://lists.openstack.org/pipermail/openstack-dev/2015-June/068202.html
[2] 
http://git.openstack.org/cgit/openstack/neutron/tree/doc/source/policies/thirdparty-ci.rst


From: Znoinski, Waldemar
Sent: Friday, June 26, 2015 9:58 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: RE: [openstack-dev] [openstack-infra][Infra][Neutron] Nominating 
intel-networking-ci for voting rights

Thanks Kyle.

Yes, I’d wait with further processing of this request till we have a consensus 
on the thread.

From: Kyle Mestery [mailto:mest...@mestery.com]
Sent: Thursday, June 25, 2015 8:11 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra][Infra][Neutron] Nominating 
intel-networking-ci for voting rights

On Wed, Jun 24, 2015 at 12:22 PM, Znoinski, Waldemar 
mailto:waldemar.znoin...@intel.com>> wrote:
Hi Kyle and Neutron Cores,

I would like to nominate Intel-Networking-CI 
(https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-Networking-CI) to have 
voting (non-gating) rights.
It’s been commenting on each proposed patch-set in Neutron since Feb 10 ’15: 
https://review.openstack.org/#/q/reviewer:%22Intel+Networking+CI+%253Copenstack-networking-ci%2540intel.com%253E%22,n,00333e9b0002530a
Any issues with it were resolved within 1-2 working days.

A recent cut from history – although a full one is at 
https://review.openstack.org/#/q/reviewer:%22Intel+Networking+CI+%253Copenstack-networking-ci%2540intel.com%253E%22,n,z
 :

https://review.openstack.org/#/c/194441/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/41/194441/6/
https://review.openstack.org/#/c/173001/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/01/173001/14/
https://review.openstack.org/#/c/195218/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/18/195218/1/
https://review.openstack.org/#/c/194455/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/55/194455/4/
https://review.openstack.org/#/c/195045/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/45/195045/1/

Let me know if there are any other requirements we should be fulfilling and/or 
approve if no questions.



+1 from me. See the recent thread [1] about this topic, however, and decide if 
you really want to vote or not.
Thanks!
Kyle

[1] http://lists.openstack.org/pipermail/openstack-dev/2015-June/067992.html

Waldek


--
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

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-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-infra][Infra][Neutron] Nominating intel-networking-ci for voting rights

[Znoinski, Waldemar]

Thanks Kyle.

Yes, I’d wait with further processing of this request till we have a consensus 
on the thread.

From: Kyle Mestery [mailto:mest...@mestery.com]
Sent: Thursday, June 25, 2015 8:11 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra][Infra][Neutron] Nominating 
intel-networking-ci for voting rights

On Wed, Jun 24, 2015 at 12:22 PM, Znoinski, Waldemar 
mailto:waldemar.znoin...@intel.com>> wrote:
Hi Kyle and Neutron Cores,

I would like to nominate Intel-Networking-CI 
(https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-Networking-CI) to have 
voting (non-gating) rights.
It’s been commenting on each proposed patch-set in Neutron since Feb 10 ’15: 
https://review.openstack.org/#/q/reviewer:%22Intel+Networking+CI+%253Copenstack-networking-ci%2540intel.com%253E%22,n,00333e9b0002530a
Any issues with it were resolved within 1-2 working days.

A recent cut from history – although a full one is at 
https://review.openstack.org/#/q/reviewer:%22Intel+Networking+CI+%253Copenstack-networking-ci%2540intel.com%253E%22,n,z
 :

https://review.openstack.org/#/c/194441/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/41/194441/6/
https://review.openstack.org/#/c/173001/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/01/173001/14/
https://review.openstack.org/#/c/195218/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/18/195218/1/
https://review.openstack.org/#/c/194455/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/55/194455/4/
https://review.openstack.org/#/c/195045/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/45/195045/1/

Let me know if there are any other requirements we should be fulfilling and/or 
approve if no questions.



+1 from me. See the recent thread [1] about this topic, however, and decide if 
you really want to vote or not.
Thanks!
Kyle

[1] http://lists.openstack.org/pipermail/openstack-dev/2015-June/067992.html

Waldek


--
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

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-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [openstack-infra][Infra][Neutron] Nominating intel-networking-ci for voting rights

[Znoinski, Waldemar]

Hi Kyle and Neutron Cores,

I would like to nominate Intel-Networking-CI 
(https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-Networking-CI) to have 
voting (non-gating) rights.
It's been commenting on each proposed patch-set in Neutron since Feb 10 '15: 
https://review.openstack.org/#/q/reviewer:%22Intel+Networking+CI+%253Copenstack-networking-ci%2540intel.com%253E%22,n,00333e9b0002530a
Any issues with it were resolved within 1-2 working days.

A recent cut from history - although a full one is at 
https://review.openstack.org/#/q/reviewer:%22Intel+Networking+CI+%253Copenstack-networking-ci%2540intel.com%253E%22,n,z
 :

https://review.openstack.org/#/c/194441/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/41/194441/6/
https://review.openstack.org/#/c/173001/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/01/173001/14/
https://review.openstack.org/#/c/195218/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/18/195218/1/
https://review.openstack.org/#/c/194455/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/55/194455/4/
https://review.openstack.org/#/c/195045/ - 
http://intel-openstack-ci-logs.ovh/networking-ci/refs/changes/45/195045/1/

Let me know if there are any other requirements we should be fulfilling and/or 
approve if no questions.


Waldek

--
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev