1. tsc@lists.fd.io
  2. Messages
   Date   
FDIO Gerrit Maintenance - 2020-10-04 at 1700 UTC to 1900 UTC

Vanessa Valderrama
 

What:  Gerrit maintenance to resize the instance

When:   2020-10-04 at 1700 UTC to 1900 UTC

Impact:  Gerrit and Jenkins will be unavailable at this time. Jenkins will be placed in shutdown mode at 1700 UTC. At 1800 UTC jobs will be aborted

Why:  This increase is being done at the request of the FD.io community

Thank you,
Vanessa

Ray Kinsella to chair this weeks FD.io TSC meeting

Edward Warnicke
 

Ray Kinsella has graciously agreed to chair the FD.io TSC meeting this week.

Ed
Ole Troan to be my proxy at this weeks FD.io TSC

Edward Warnicke
 

Ole Troan has graciously agreed to be my proxy at this week's FD.io TSC meeting.

Ed
Re: Please approve Vladimir Lavor as a new GoVPP project committer

Ray Kinsella
 

Thanks Rastislav,

 

We will pick this up at the next TSC meeting.

 

Regards,

 

Ray K

 

From: tsc@... <tsc@...> On Behalf Of Rastislav Szabo -X (raszabo - PANTHEON TECH SRO at Cisco) via lists.fd.io
Sent: Thursday 22 October 2020 20:59
To: tsc@...
Cc: govpp-dev@...
Subject: [tsc] Please approve Vladimir Lavor as a new GoVPP project committer

 

Dear FD.io TSC,

 

I would like to ask for approving Vladimir Lavor as a new GoVPP project committer.

 

The supermajority of GoVPP committers already voted +1:

 

https://lists.fd.io/g/govpp-dev/topic/new_govpp_committer/77726308?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,77726308

 

Vladimir has been contributing to GoVPP since 2018 and has been recently one of the top code contributors into GoVPP:

 

https://gerrit.fd.io/r/gitweb?p=govpp.git;a=search;s=Vladimir+Lavor;st=author

 

Thanks,

Rastislav
Please approve Vladimir Lavor as a new GoVPP project committer

Rastislav Szabo -X (raszabo - PANTHEON TECH SRO at Cisco) <raszabo@...>
 

Dear FD.io TSC,

 

I would like to ask for approving Vladimir Lavor as a new GoVPP project committer.

 

The supermajority of GoVPP committers already voted +1:

 

https://lists.fd.io/g/govpp-dev/topic/new_govpp_committer/77726308?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,77726308

 

Vladimir has been contributing to GoVPP since 2018 and has been recently one of the top code contributors into GoVPP:

 

https://gerrit.fd.io/r/gitweb?p=govpp.git;a=search;s=Vladimir+Lavor;st=author

 

Thanks,

Rastislav
GoVPP PTL resignation

Rastislav Szabo -X (raszabo - PANTHEON TECH SRO at Cisco) <raszabo@...>
 

Dear GoVPP community,

 

since I have accepted a new career challenge, I’ve decided to resign from my GoVPP project tech lead position.

 

Although I would still like to retain my GoVPP committer status, I cannot commit to PTL role anymore.

 

According to the FD.io governance document,

https://fd.io/docs/tsc/FD.IO-Technical-Community-Document-12-12-2017.pdf: 

 

3.2.3.1 Project Technical Leader Candidates

Candidates for the project’s PTL will be derived from the Committers of the Project. Candidates must self-nominate.

 

I'd like to invite any interested GoVPP committer to self-nominate for the PTL role. Please email your self-nomination to the govpp-dev mailing list.

 

Let's close the self-nomination period by Tuesday 27th October 20:00 UTC.

 

Thanks,

Rasto
Re: FD.io Jenkins

Vanessa Valderrama
 

Jenkins service has been restored. The UI instability was a result of a
Jenkins OOM issue. We increased the heap size, increased the
KeepAliveTimeout, upgraded the Jenkins version and restarted the service.

We'll continue to monitor Jenkins for performance issues. If you
experience any issue, please open a ticket at support.linuxfoundation.org.

Thank you,
Vanessa

On 10/19/20 7:52 AM, Vanessa Valderrama wrote:
We are currently seeing intermittent slowness on jenkins.fd.io. We're
placing Jenkins in shutdown mode while we troubleshoot the issue and in
preparation for a possible restart.

Thank you,

Vanessa
FD.io Jenkins

Vanessa Valderrama
 

We are currently seeing intermittent slowness on jenkins.fd.io. We're
placing Jenkins in shutdown mode while we troubleshoot the issue and in
preparation for a possible restart.

Thank you,

Vanessa
Re: ENEA and HCL contributions to CSIT

Kinsella, Ray <mdr@...>
 

+1 legend

On 16/10/2020 14:07, Maciek Konstantynowicz (mkonstan) wrote:
Thanks Vratko, you’re a Star! M.

On 16 Oct 2020, at 13:38, Vratko Polak -X (vrpolak - PANTHEON TECH SRO at Cisco) <vrpolak@...> wrote:

Lucian's contribution is about 10-20 LoC, probably about 1hr or 2hr to rework by a volunteer.
Any volunteers ... ?
As I have looked at the contribution already,
I figured the hypothetical volunteer would spend
more time working on that that I would.
So [2] is now merged.

Hopefully, device tests will not start failing occasionally because of that. :)

Vratko.

[2] https://gerrit.fd.io/r/c/csit/+/29478

-----Original Message-----
From: tsc@... <tsc@...> On Behalf Of Kinsella, Ray
Sent: Monday, 2020-October-05 21:32
To: tsc@...; Florin Coras (fcoras) <fcoras@...>; Maciek Konstantynowicz (mkonstan) <mkonstan@...>
Subject: [tsc] ENEA and HCL contributions to CSIT

Folks,

I had a look at the ENEA and HCL contributions contributions to CSIT.
You can find them here:

* Lucian Banu (ENEA): https://git.fd.io/csit/commit/?id=4bafd0aa54fa78c4c3a6a32281cfa551e61bcafc

Lucian's contribution is about 10-20 LoC, probably about 1hr or 2hr to rework by a volunteer.
Any volunteers ... ?

* Nidhy (HCL): https://git.fd.io/csit/commit/?id=aafa2efa63b891e85ff13255691aae4909bc503c

Nidhy's contribution is substantial, adding the following test case.

LISP_IP4o4
LISPGPE_IP4o4
LISPGPE_IP6o4
LISPGPE_IP6o4.
LISPGEP_IP4o6
LISPGPE_IP6o6

CC'ing Florin (LISP maintainer) to understand, what is the impact if we need to excise these Test Cases without rework.

Thanks,

Ray K
Re: ENEA and HCL contributions to CSIT

Maciek Konstantynowicz (mkonstan)
 

Thanks Vratko, you’re a Star! M.

On 16 Oct 2020, at 13:38, Vratko Polak -X (vrpolak - PANTHEON TECH SRO at Cisco) <vrpolak@...> wrote:

Lucian's contribution is about 10-20 LoC, probably about 1hr or 2hr to rework by a volunteer.
Any volunteers ... ?
As I have looked at the contribution already,
I figured the hypothetical volunteer would spend
more time working on that that I would.
So [2] is now merged.

Hopefully, device tests will not start failing occasionally because of that. :)

Vratko.

[2] https://gerrit.fd.io/r/c/csit/+/29478

-----Original Message-----
From: tsc@... <tsc@...> On Behalf Of Kinsella, Ray
Sent: Monday, 2020-October-05 21:32
To: tsc@...; Florin Coras (fcoras) <fcoras@...>; Maciek Konstantynowicz (mkonstan) <mkonstan@...>
Subject: [tsc] ENEA and HCL contributions to CSIT

Folks,

I had a look at the ENEA and HCL contributions contributions to CSIT.
You can find them here:

* Lucian Banu (ENEA): https://git.fd.io/csit/commit/?id=4bafd0aa54fa78c4c3a6a32281cfa551e61bcafc

Lucian's contribution is about 10-20 LoC, probably about 1hr or 2hr to rework by a volunteer.
Any volunteers ... ?

* Nidhy (HCL): https://git.fd.io/csit/commit/?id=aafa2efa63b891e85ff13255691aae4909bc503c

Nidhy's contribution is substantial, adding the following test case.

LISP_IP4o4
LISPGPE_IP4o4
LISPGPE_IP6o4
LISPGPE_IP6o4.
LISPGEP_IP4o6
LISPGPE_IP6o6

CC'ing Florin (LISP maintainer) to understand, what is the impact if we need to excise these Test Cases without rework.

Thanks,

Ray K
Re: ENEA and HCL contributions to CSIT

Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
 

Lucian's contribution is about 10-20 LoC, probably about 1hr or 2hr to rework by a volunteer.
Any volunteers ... ?
As I have looked at the contribution already,
I figured the hypothetical volunteer would spend
more time working on that that I would.
So [2] is now merged.

Hopefully, device tests will not start failing occasionally because of that. :)

Vratko.

[2] https://gerrit.fd.io/r/c/csit/+/29478

-----Original Message-----
From: tsc@... <tsc@...> On Behalf Of Kinsella, Ray
Sent: Monday, 2020-October-05 21:32
To: tsc@...; Florin Coras (fcoras) <fcoras@...>; Maciek Konstantynowicz (mkonstan) <mkonstan@...>
Subject: [tsc] ENEA and HCL contributions to CSIT

Folks,

I had a look at the ENEA and HCL contributions contributions to CSIT.
You can find them here:

* Lucian Banu (ENEA): https://git.fd.io/csit/commit/?id=4bafd0aa54fa78c4c3a6a32281cfa551e61bcafc

Lucian's contribution is about 10-20 LoC, probably about 1hr or 2hr to rework by a volunteer.
Any volunteers ... ?

* Nidhy (HCL): https://git.fd.io/csit/commit/?id=aafa2efa63b891e85ff13255691aae4909bc503c

Nidhy's contribution is substantial, adding the following test case.

LISP_IP4o4
LISPGPE_IP4o4
LISPGPE_IP6o4
LISPGPE_IP6o4.
LISPGEP_IP4o6
LISPGPE_IP6o6

CC'ing Florin (LISP maintainer) to understand, what is the impact if we need to excise these Test Cases without rework.

Thanks,

Ray K
Re: Emergency upgrade of Nexus system

Andrew Grimberg
 

This work has been completed.

-Andy-

On 2020-10-15 12:04, Andrew Grimberg via lists.fd.io wrote:
We just received word that both Nexus 2 and Nexus 3 are vulnerable to a
security issue that was just announced with possible attacks already in
the wild.

Given the nature of the security issue we will be performing emergency
upgrades on the single Nexus system that FD.io has in play. I have
already placed both Jenkins systems into shutdown mode to stop new jobs
from starting.

Given the length of the jobs already running and their ETA for
completion. We will be running the upgrade in while the jobs are in
progress. If you see a failure in your job due to this forced upgrade we
apologize but due to the nature of this we must get this update rolled out.

-Andy-




--
Andrew J Grimberg
Manager Release Engineering
The Linux Foundation

?
signature.asc

Emergency upgrade of Nexus system

Andrew Grimberg
 

We just received word that both Nexus 2 and Nexus 3 are vulnerable to a
security issue that was just announced with possible attacks already in
the wild.

Given the nature of the security issue we will be performing emergency
upgrades on the single Nexus system that FD.io has in play. I have
already placed both Jenkins systems into shutdown mode to stop new jobs
from starting.

Given the length of the jobs already running and their ETA for
completion. We will be running the upgrade in while the jobs are in
progress. If you see a failure in your job due to this forced upgrade we
apologize but due to the nature of this we must get this update rolled out.

-Andy-
--
Andrew J Grimberg
Manager Release Engineering
The Linux Foundation

?
signature.asc

Published: FD.io CSIT-2009 Release Report

Maciek Konstantynowicz (mkonstan)
 

Hi All,

FD.io CSIT-2009 report is available on FD.io docs site:

https://docs.fd.io/csit/rls2009/report/

Great thanks to all contributors in CSIT and VPP communities!

Below summary and pointers to specific sections in the report.
Welcome all comments, best by email to csit-dev@....

Cheers,
-Maciek


CSIT-2009 Release Summary
-------------------------

NEW TESTS

- A new category of tests using TRex ASTF stateful APIs and traffic
profiles with up to 16M UDP and TCP/IP sessions. Initial stateful
tests include VPP NAT44 Endpoint Dependent (NAT44ed)
connections-per-second and packets-per-second throughput (with
controlled packet size). (Note: report test runs are still to be
executed in their fullness, expect them to appear in maintenance
report versions next week and week after next. Maintenance reports are
published on a weekly basis if there are changes.)

- Refactored existing NAT44 Deterministic (NAT44det) throughput tests
and added higher session scale, up to 16M UDP sessions. Continue to
use TRex STL stateless APIs and traffic profiles.

- Added NAT44ed uni-directional UDP throughput tests using TRex STL
stateless APIs and traffic profiles, as a way to verify stateful tests
performance.

- IPsec async mode VPP performance tests, with HW crypto only for now,
meaning Xeon Haswell testbeds only.

- Full suite of tests now running on Mellanox ConnectX5-2p100GE NICs in
2n-clx (Intel Xeon Cascadelake) testbeds using VPP native rdma driver.
For the first time one case see linear multi-core speedup into 72 Mpps
region (L2 on 2 cores, IPv4 on 4 cores), in some cases NIC is the
limit again (like it was to date in CSIT labs with FVL 2p25GE NICs).

BENCHMARKING

- AMD 2n-zn2 testbed onboarded with EPYC 7532 32-Core Processor. Full
set of CSIT-2009 results to be included in one of the upcoming
maintenance reports, following completion of calibrating dry runs that
are currently ongoing.

- Optimization and calibration of TRex STL and ASTF multi-core
configurations, a small impact on test results as captured in current
vs. previous release performance comparisons.


Pointers to CSIT-2009 Report sections
-------------------------------------

1. FD.io CSIT test methodology [1]
2. VPP release notes [2]
3. VPP 64B/IMIX throughput graphs [3]
4. VPP throughput speedup multi-core [4]
5. VPP latency under load [5]
6. VPP comparisons v20.09 vs. v20.05 [6]
7. VPP performance all pkt sizes & NICs [7]
8. DPDK 20.08 apps release notes [8]
9. DPDK 64B throughput graphs [9]
10. DPDK latency under load [10]
11. DPDK comparisons 20.08 vs. 20.02 [11]

Functional device tests (VPP_Device) are also included in the report.

[1] https://docs.fd.io/csit/rls2009/report/introduction/methodology.html
[2] https://docs.fd.io/csit/rls2009/report/vpp_performance_tests/csit_release_notes.html
[3] https://docs.fd.io/csit/rls2009/report/vpp_performance_tests/packet_throughput_graphs/index.html
[4] https://docs.fd.io/csit/rls2009/report/vpp_performance_tests/throughput_speedup_multi_core/index.html
[5] https://docs.fd.io/csit/rls2009/report/vpp_performance_tests/packet_latency/index.html
[6] https://docs.fd.io/csit/rls2009/report/vpp_performance_tests/comparisons/current_vs_previous_release.html
[7] https://docs.fd.io/csit/rls2009/report/detailed_test_results/vpp_performance_results/index.html
[8] https://docs.fd.io/csit/rls2009/report/dpdk_performance_tests/csit_release_notes.html
[9] https://docs.fd.io/csit/rls2009/report/dpdk_performance_tests/packet_throughput_graphs/index.html
[10] https://docs.fd.io/csit/rls2009/report/dpdk_performance_tests/packet_latency/index.html
[11] https://docs.fd.io/csit/rls2009/report/dpdk_performance_tests/comparisons/current_vs_previous_release.html
Re: FD.io Jenkins Maintenance: 2020-10-19 1700 UTC to 2200 UTC

Vanessa Valderrama
 

Maintenance has been completed successfully. All service are available.

As part of maintenance we downgraded the Gerrit Trigger plugin in Jenkins to avoid a re-occurrence of the incident we had today. It appears there is a defect in the latest version of the plugin that causes Gerrit triggers to stop triggering builds in Jenkins causing the queue to grow out of control and affect the stability of the Jenkins system. The root cause is unknown at this time. The workaround is to restart Jenkins.

If you experience any issues, please open a ticket at support.linuxfoundation.org.

Thank you,
Anton & Vanessa


On 10/7/20 9:36 AM, Vanessa Valderrama wrote:

Due to the unexpected Jenkins outage, we are going to perform this maintenance now. This maintenance has been approved by the VPP and CSIT teams.

Thank you,
Vanessa

On 10/5/20 12:11 PM, Vanessa Valderrama wrote:

What:
  • Ingress
    • Increase the size of the instance
    • OS and security updates
  • Jenkins
    • OS and security updates
    • Upgrade to 2.249.1
    • Plugin updates
  • Nexus
    • OS updates
    • Upgrade to 2.14.19-01
  • Jira
    • OS updates
    • Upgrade to 8.12.2
  • Gerrit
    • OS updates
When:  2020-10-19 1700 UTC to 2200 UTC

Impact:

All systems will be unavailable during the maintenance window. Jenkins will be placed in shutdown mode at 1600 UTC. We will abort all jobs at 1700 UTC.
Re: FD.io Jenkins Maintenance: 2020-10-19 1700 UTC to 2200 UTC

Vanessa Valderrama
 

Due to the unexpected Jenkins outage, we are going to perform this maintenance now. This maintenance has been approved by the VPP and CSIT teams.

Thank you,
Vanessa

On 10/5/20 12:11 PM, Vanessa Valderrama wrote:

What:
  • Ingress
    • Increase the size of the instance
    • OS and security updates
  • Jenkins
    • OS and security updates
    • Upgrade to 2.249.1
    • Plugin updates
  • Nexus
    • OS updates
    • Upgrade to 2.14.19-01
  • Jira
    • OS updates
    • Upgrade to 8.12.2
  • Gerrit
    • OS updates
When:  2020-10-19 1700 UTC to 2200 UTC

Impact:

All systems will be unavailable during the maintenance window. Jenkins will be placed in shutdown mode at 1600 UTC. We will abort all jobs at 1700 UTC.
FD.io Jenkins Unavailable

Vanessa Valderrama
 

We are currently experiencing issues with Jenkins production. We are
investigating this issue and working on resolving it as quickly as possible.

Thank you,
Vanessa
Re: ENEA and HCL contributions to CSIT

Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
 

The tests are still being used (even part of voting VPP verify job):
https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-csit-verify-device-master-1n-skx/9274/archives/log.html.gz#s1-s1-s1-s5-s3
https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-csit-verify-device-master-1n-skx/9274/archives/log.html.gz#s1-s1-s1-s7-s1

Including their to-be-GPLed traffic scripts:
https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-csit-verify-device-master-1n-skx/9274/archives/log.html.gz#s1-s1-s1-s5-s3-s1-t1-k2-k10-k4
https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-csit-verify-device-master-1n-skx/9274/archives/log.html.gz#s1-s1-s1-s7-s1-s1-t1-k2-k11-k4

Vratko.

-----Original Message-----
From: tsc@... <tsc@...> On Behalf Of Florin Coras (fcoras) via lists.fd.io
Sent: Monday, 2020-October-05 21:47
To: Kinsella, Ray <mdr@...>; tsc@...; Maciek Konstantynowicz (mkonstan) <mkonstan@...>
Subject: Re: [tsc] ENEA and HCL contributions to CSIT

I'll let Maciek clarify that, but I think we're no longer running them. I'm okay with removing them, if they're disabled.

Regards,
Florin

On 10/5/20, 12:36 PM, "Kinsella, Ray" <mdr@...> wrote:


So we aren't even running them at the moment then?
I presume if we aren't running them, we can safely remove them to solve our GPL issue?

Would you object?

Ray K

On 05/10/2020 20:34, Florin Coras (fcoras) wrote:
> Hi Ray,
>
> Would love to try to restart running those test cases, if we have enough resources.
>
> Hard to say if they'll work out of the box.
>
> Regards,
> Florin
>
>
> On 10/5/20, 12:32 PM, "Kinsella, Ray" <mdr@...> wrote:
>
> Folks,
>
> I had a look at the ENEA and HCL contributions contributions to CSIT.
> You can find them here:
>
> * Lucian Banu (ENEA): https://git.fd.io/csit/commit/?id=4bafd0aa54fa78c4c3a6a32281cfa551e61bcafc
>
> Lucian's contribution is about 10-20 LoC, probably about 1hr or 2hr to rework by a volunteer.
> Any volunteers ... ?
>
> * Nidhy (HCL): https://git.fd.io/csit/commit/?id=aafa2efa63b891e85ff13255691aae4909bc503c
>
> Nidhy's contribution is substantial, adding the following test case.
>
> LISP_IP4o4
> LISPGPE_IP4o4
> LISPGPE_IP6o4
> LISPGPE_IP6o4.
> LISPGEP_IP4o6
> LISPGPE_IP6o6
>
> CC'ing Florin (LISP maintainer) to understand, what is the impact if we need to excise these Test Cases without rework.
>
> Thanks,
>
> Ray K
>
Re: ENEA and HCL contributions to CSIT

Florin Coras (fcoras) <fcoras@...>
 

I'll let Maciek clarify that, but I think we're no longer running them. I'm okay with removing them, if they're disabled.

Regards,
Florin

On 10/5/20, 12:36 PM, "Kinsella, Ray" <mdr@...> wrote:


So we aren't even running them at the moment then?
I presume if we aren't running them, we can safely remove them to solve our GPL issue?

Would you object?

Ray K

On 05/10/2020 20:34, Florin Coras (fcoras) wrote:
> Hi Ray,
>
> Would love to try to restart running those test cases, if we have enough resources.
>
> Hard to say if they'll work out of the box.
>
> Regards,
> Florin
>
>
> On 10/5/20, 12:32 PM, "Kinsella, Ray" <mdr@...> wrote:
>
> Folks,
>
> I had a look at the ENEA and HCL contributions contributions to CSIT.
> You can find them here:
>
> * Lucian Banu (ENEA): https://git.fd.io/csit/commit/?id=4bafd0aa54fa78c4c3a6a32281cfa551e61bcafc
>
> Lucian's contribution is about 10-20 LoC, probably about 1hr or 2hr to rework by a volunteer.
> Any volunteers ... ?
>
> * Nidhy (HCL): https://git.fd.io/csit/commit/?id=aafa2efa63b891e85ff13255691aae4909bc503c
>
> Nidhy's contribution is substantial, adding the following test case.
>
> LISP_IP4o4
> LISPGPE_IP4o4
> LISPGPE_IP6o4
> LISPGPE_IP6o4.
> LISPGEP_IP4o6
> LISPGPE_IP6o6
>
> CC'ing Florin (LISP maintainer) to understand, what is the impact if we need to excise these Test Cases without rework.
>
> Thanks,
>
> Ray K
>
Re: ENEA and HCL contributions to CSIT

Kinsella, Ray <mdr@...>
 

So we aren't even running them at the moment then?
I presume if we aren't running them, we can safely remove them to solve our GPL issue?

Would you object?

Ray K

On 05/10/2020 20:34, Florin Coras (fcoras) wrote:
Hi Ray,

Would love to try to restart running those test cases, if we have enough resources.

Hard to say if they'll work out of the box.

Regards,
Florin


On 10/5/20, 12:32 PM, "Kinsella, Ray" <mdr@...> wrote:

Folks,

I had a look at the ENEA and HCL contributions contributions to CSIT.
You can find them here:

* Lucian Banu (ENEA): https://git.fd.io/csit/commit/?id=4bafd0aa54fa78c4c3a6a32281cfa551e61bcafc

Lucian's contribution is about 10-20 LoC, probably about 1hr or 2hr to rework by a volunteer.
Any volunteers ... ?

* Nidhy (HCL): https://git.fd.io/csit/commit/?id=aafa2efa63b891e85ff13255691aae4909bc503c

Nidhy's contribution is substantial, adding the following test case.

LISP_IP4o4
LISPGPE_IP4o4
LISPGPE_IP6o4
LISPGPE_IP6o4.
LISPGEP_IP4o6
LISPGPE_IP6o6

CC'ing Florin (LISP maintainer) to understand, what is the impact if we need to excise these Test Cases without rework.

Thanks,

Ray K
301 - 320 of 1740