Re: [vpp-dev] failure while building VPP v23.02 in centos 7 VM

[Dave Wallace]

Hi Sandeep,

The VPP community no longer supports building on CentOS-7.  The build 
infrastructure for centos/redhat/rocky OS distros was left in place 
after support ended, but there are no active maintainers for this build 
infra nor are there any CI jobs to ensure that it still works.


You may get lucky and a community member may chime in, but for the most 
part you are on your own wrt. getting currently supported VPP releases 
to build on CentOS-7.


Thanks,
-daw-

On 3/9/2023 11:56 AM, SANDEEP KUMAR wrote:

Hi All,

I am trying to build VPP v23.02 but getting an issue while performing 
the *make install-ext-deps* step in centos 7 VM, so please look at the 
following issue and help me to resolve it.


*Prerequisites:*
sudo yum groupinstall "Development Tools"
sudo yum install -y numactl-devel libarchive-devel bzip2-devel  
libpcap-devel libhugetlbfs-utils pciutils pkgconfig libtool ethtool

sudo yum -y install libibverbs
sudo yum -y groupinstall "Infiniband Support"
sudo yum install -y numactl-devel librdmacm-devel libmnl-devel libatomic

#Download and install nasm
wget https://www.nasm.us/pub/nasm/releasebuilds/2.15/nasm-2.15.tar.gz
tar -xzvf nasm-2.15.tar.gz
cd nasm-2.15/
sh autogen.sh
sh configure --prefix=/usr/local/
make
sudo make install
sudo ldconfig

#Download and install the latest libpcap
git clone https://github.com/the-tcpdump-group/libpcap.git
cd libpcap
git checkout libpcap-1.10.0
./autogen.sh
./configure
make
make install
sudo ldconfig

#Download and build clang with 10.x version
git clone -b llvmorg-10.0.1  --depth 1 
https://github.com/llvm/llvm-project.git

cd llvm-project
mkdir build && cd build
cmake -G "Unix Makefiles" 
-DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra" 
-DCMAKE_INSTALL_PREFIX=/usr/local -DCMAKE_BUILD_TYPE=Release ../llvm

make -j 8
sudo make install
sudo ldconfig

To download the pre-compiled cmake v3.23
wget 
https://github.com/Kitware/CMake/releases/download/v3.23.0-rc4/cmake-3.23.0-rc4-linux-x86_64.tar.gz 


tar -xzvf cmake-3.23.0-rc4-linux-x86_64.tar.gz
cd cmake-3.23.0-rc4-linux-x86_64
cp -v ./bin/cmake /usr/local/bin
cp -r ./share/cmake-3.23 /usr/local/share
sudo ldconfig

*Using gcc version 9.3.x while build VPP v23.02*
sudo yum install -y centos-release-scl
sudo yum install -y devtoolset-9
scl enable devtoolset-9 bash
[root@localhost vpp]# gcc --version
gcc (GCC) 9.3.1 20200408 (Red Hat 9.3.1-2)
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
PURPOSE.


*Using centos 7 and kernel used*
[root@localhost vpp]#*cat /etc/os-release*
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/";
BUG_REPORT_URL="https://bugs.centos.org/";

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

[root@localhost vpp]# *uname -r*
3.10.0-1160.71.1.el7.x86_64


*Git clone VPP and build VPP v23.02*
git clone https://gerrit.fd.io/r/vpp
cd vpp
git tag
git checkout v23.02
make install-deps

Following issue coming while performing make install-ext-deps step
*make install-ext-deps*
*...*
*...*
*..*
Installing 
/home/centos/download_vpp/vpp/build/external/rpm/tmp/build-dpdk/meson-private/libdpdk.pc 
to 
/home/centos/download_vpp/vpp/build/external/rpm/BUILDROOT/vpp-ext-deps-23.02-8.

x86_64/opt/vpp/external/x86_64/lib/pkgconfig
Running custom install script '/bin/sh 
/home/centos/download_vpp/vpp/build/external/rpm/tmp/src-dpdk/config/../buildtools/symlink-drivers-solibs.sh 
lib dpdk/pmds-22.2'
--- installing quicly 0.1.4-vpp - log: 
/home/centos/download_vpp/vpp/build/external/rpm/tmp/quicly.install.log

mkdir -p downloads
Downloading 
https://github.com/xdp-project/xdp-tools/releases/download/v1.2.9/xdp-tools-1.2.9.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time 
 Current
                                 Dload  Upload   Total   Spent    Left 
 Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- 
--:--:--     0
100 1177k  100 1177k    0     0   271k      0  0:00:04  0:00:04 
--:--:--  468k

--- validating xdp-tools 1.2.9 checksum
--- extracting xdp-tools 1.2.9
--- patching xdp-tools 1.2.9
Applying patch: 0001-libxdp-add-fPIC-with-static-lib-build.patch
patching file lib/libxdp/Makefile
Applying patch: 0002-libxdp-fix-asm-types.h-file-not-found-issue.patch
patching file lib/defines.mk 
Applying patch: 0003-libxdp-fix-maybe-uninitialized-compiler-warning.patch
patching file lib/common.mk 
--- configuring xdp-tools 1.2.9 - log: 
/home/centos/download_vpp/vpp/build/external/rpm/tmp/xdp-tools.config.log
--- building xdp-tools 1.2.9 - log: 
/home/centos/download_vpp/vpp/build/external/rpm/tmp/xdp-tools.bu

[vpp-dev] RFC: VPP Build Artifact Retention Policy

[Dave Wallace]

Folks,

As discussed in the last 2 VPP Community meetings, I have created a 
draft build artifact policy for the VPP project [0].


Please review and provide comments to this email thread.

Thanks,
-daw-

[0] https://wiki.fd.io/view/VPP/BuildArtifactRetentionPolicy

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22669): https://lists.fd.io/g/vpp-dev/message/22669
Mute This Topic: https://lists.fd.io/mt/97437987/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] docker pkg-deb?

[Dave Wallace]

Hemant,

VPP build infrastructure does not currently support building docker 
images containing the VPP pkg-deb.  You'll have to create your own 
Dockerfile to do so.


Thanks,
-daw-

On 2/28/2023 3:09 PM, hemant via lists.fd.io wrote:


Folks,

I use “sudo make pkg-deb” to build.

How to I build a docker image for pkg-deb?

Hemant





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22638): https://lists.fd.io/g/vpp-dev/message/22638
Mute This Topic: https://lists.fd.io/mt/97298934/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [vpp-build] VPP build error on Ubuntu 22.04

[Dave Wallace]

Thanks for letting us know.
-daw-

On 2/26/2023 8:49 AM, Jens Rösiger via lists.fd.io wrote:

Hi Dave,

i have apply the patch and the build process has no more errors. All 
.deb packages are created.

Thank you very much.

--
Jens




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22628): https://lists.fd.io/g/vpp-dev/message/22628
Mute This Topic: https://lists.fd.io/mt/97192445/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [vpp-build] VPP build error on Ubuntu 22.04

[Dave Wallace]

Jens,

Forwarding to vpp-dev@lists.fd.io where VPP contributors answer these 
types of questions.


The srtp plugin is not built in the CI [0] and ubuntu-22.04 includes 
version 2.4.2 of libsrtp2 [1].  The ekt field was deprecated in 2.4.0 
since it was never fully implemented and the draft changed [2].


I pinged Florin Coras who maintains the srtp_plugin which is 
experimental and verified that it has been intentionally left out of the 
CI.  I have pushed a fix for the build failure [3], but Florin will need 
to test it before it can be merged.


Please apply the patch and let us know if you run into any more issues.

Thanks,
-daw-

[0] 
https://s3-logs.fd.io/vex-yul-rot-jenkins-1/vpp-verify-master-ubuntu2204-x86_64/1178/console-timestamp.log.gz
    (search for libsrtp2.a -> "17:54:54  -- -- libsrtp2.a library not 
found - srtp plugin disabled"

[1] https://pkgs.org/search/?q=libsrtp2
[2] https://github.com/cisco/libsrtp/releases/tag/v2.4.0
[3] https://gerrit.fd.io/r/c/vpp/+/38345

 Forwarded Message 
Subject:[vpp-build] VPP build error on Ubuntu 22.04
Date:   Thu, 23 Feb 2023 03:26:25 -0800
From:   Jens Rösiger via lists.fd.io 
Reply-To:   vpp-bu...@lists.fd.io
To: vpp-bu...@lists.fd.io



Dear VPP Build Team,

i have a problem to build VPP on Ubuntu 22.04(LTS).

 * no errror on "make install-deps"
 * no errors on "make install-ext-deps"
 * but "make build-release"  give this error:

make[1]: Entering directory '/opt/buildpackage/src/vpp/vpp/build-root'
 Arch for platform 'vpp' is native 
 Finding source for external 
 Makefile fragment found in 
/opt/buildpackage/src/vpp/vpp/build-data/packages/external.mk 

 Source found in /opt/buildpackage/src/vpp/vpp/build 
 Arch for platform 'vpp' is native 
 Finding source for vpp 
 Makefile fragment found in 
/opt/buildpackage/src/vpp/vpp/build-data/packages/vpp.mk 

 Source found in /opt/buildpackage/src/vpp/vpp/src 
 Configuring external in 
/opt/buildpackage/src/vpp/vpp/build-root/build-vpp-native/external 
 Building external in 
/opt/buildpackage/src/vpp/vpp/build-root/build-vpp-native/external 

 Installing external 
make[2]: Entering directory '/opt/buildpackage/src/vpp/vpp/build/external'
make check-deb
make[3]: Entering directory '/opt/buildpackage/src/vpp/vpp/build/external'
make[3]: Nothing to be done for 'check-deb'.
make[3]: Leaving directory '/opt/buildpackage/src/vpp/vpp/build/external'
make[2]: Nothing to be done for 'ebuild-install'.
make[2]: Leaving directory '/opt/buildpackage/src/vpp/vpp/build/external'
 Configuring vpp in 
/opt/buildpackage/src/vpp/vpp/build-root/build-vpp-native/vpp 

-- The C compiler identification is Clang 14.0.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/lib/ccache/clang - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Performing Test compiler_flag_march_haswell
-- Performing Test compiler_flag_march_haswell - Success
-- Performing Test compiler_flag_mtune_haswell
-- Performing Test compiler_flag_mtune_haswell - Success
-- Performing Test compiler_flag_march_tremont
-- Performing Test compiler_flag_march_tremont - Success
-- Performing Test compiler_flag_mtune_tremont
-- Performing Test compiler_flag_mtune_tremont - Success
-- Performing Test compiler_flag_march_skylake_avx512
-- Performing Test compiler_flag_march_skylake_avx512 - Success
-- Performing Test compiler_flag_mtune_skylake_avx512
-- Performing Test compiler_flag_mtune_skylake_avx512 - Success
-- Performing Test compiler_flag_mprefer_vector_width_256
-- Performing Test compiler_flag_mprefer_vector_width_256 - Success
-- Performing Test compiler_flag_march_icelake_client
-- Performing Test compiler_flag_march_icelake_client - Success
-- Performing Test compiler_flag_mtune_icelake_client
-- Performing Test compiler_flag_mtune_icelake_client - Success
-- Performing Test compiler_flag_mprefer_vector_width_512
-- Performing Test compiler_flag_mprefer_vector_width_512 - Success
-- Looking for ccache
-- Looking for ccache - found
-- Performing Test compiler_flag_no_address_of_packed_member
-- Performing Test compiler_flag_no_address_of_packed_member - Success
-- Performing Test compiler_flag_no_stringop_overflow
-- Performing Test compiler_flag_no_stringop_overflow - Failed
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Performing Test HAVE_FCNTL64
-- Performing Test HAVE_FCNTL64 - Success
-- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version 
"3.0.2")

-- The ASM compiler identification is Clang with GNU-like command-line
-- Found assembler: /usr/lib/ccache/clang
-- Looking for libuuid
-- Found uuid in /usr/include
-- Found subunit in /usr/include and /usr/lib/x86_64-linux-gnu/libsubunit.s

Re: [vpp-dev] [csit-dev] VPP 23.02 release is complete!

[Dave Wallace]

Congratulations to everyone in the FD.io community who continuing the 
excellence in delivering VPP features, fixes, and improvements on a rock 
solid cadence.


A special thanks to Andrew for his effort to automate & execute the 
release process.


-daw-
FD.io TSC Chairperson

On 2/22/23 11:46 AM, Andrew Yourtchenko wrote:

Hi all,

VPP release 23.02 is complete ! Artifacts are at their usual place athttps://packagecloud.io/fdio/release  


Many thanks to all the contributors for their work that went into the release, 
and thanks to Dave Wallace and Vanessa Valderrama for the help in the process !

Onwards to 23.06! :-)

--a /* your friendly 23.02 release manager */




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22618): https://lists.fd.io/g/vpp-dev/message/22618
Mute This Topic: https://lists.fd.io/mt/97184849/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] FD.io Projects Retention Policy on Packagecloud.io

[Dave Wallace]

Folks,

In light of the recent VPP Security Vulnerability, the FD.io TSC 
discussed and would like to recommend that each project adopt and 
publish a retention policy for packages uploaded to 
https:packagecloud.io/fdio.


The Security Response Team is recommending that any package which was 
built from source that contains a public vulnerability in the form of a 
published CVE record be removed from packagecloud.io/fdio as soon as 
practicable after publication.


Additional factors to consider for a retention policy, is the 
availability of CI infrastructure to generate build artifacts.  CI jobs 
for releases which are no longer supported are removed shortly after the 
release has passed the End-Of-Life date.  In the TSC discussion, it was 
agreed that it made sense to remove the associated release and stable 
branch artifacts at the time the CI infrastructure was removed.  For the 
most part, artifacts uploaded to packagecloud.io are either consumed by 
the CI (e.g. CSIT performance tests), or are made available for 
newcomers to evaluate FD.io software without having to build it from 
scratch. It would be best to encourage all consumers to use supported 
software by retaining only those artifacts in packagecloud.io that are 
based on supported releases.


As it currently stands, packagecloud.io/fdio has artifacts that date 
back to early FD.io VPP releases (circa VPP 17.01).  FD.io projects are 
encouraged to be kind to packagecloud.io who is generously donating 
storage for Open Source project artifacts for free by removing 
antiquated build artifacts.


For VPP artifacts, let's discuss this at tomorrow's VPP Community Meeting.

Thanks,
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22588): https://lists.fd.io/g/vpp-dev/message/22588
Mute This Topic: https://lists.fd.io/mt/96954107/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] CVE-2022-46397: FD.io VPP (Vector Packet Processor) IPSec generates a predictable IV with AES-CBC mode

[Dave Wallace]

Folks,

A vulnerability in the VPP IPSec plugin was identified by Benoit Ganne 
who has also provided a fix that has been committed to master and 
cherry-picked to all affected VPP Release branches.



Here is the Security Advisory report for CVE-2022-46397 [0]:

Description:
FP.io VPP (Vector Packet Processor) 22.10, 22.06, 22.02, 21.10, 21.06, 
21.01, 20.09, 20.05, 20.01, 19.08, and 19.04 Generates a Predictable IV 
with CBC Mode.


Vulnerability Type Other:
CWE-329: Generation of Predictable IV with CBC Mode

Severity:
Moderate

Vendor of Product:
https://fd.io

Affected Product Code Base:
vpp - v22.10, v22.06, v22.02, v21.10, v21.06, v21.01, v20.09, v20.05, 
v20.01, v19.08, v19.04


Credit:
This issue was reported by Benoit Ganne of Cisco Systems, Inc per the 
FD.io Security Policy [1].


Resolution:
The fix for the vulnerability was committed to the VPP repository's main 
development branch and cherry-picked to all affected release branches on 
2023-02-07. See FD.io VPP Jira ticket VPP-2037 [2] for details.


Maintenance releases were performed on 2023-02-10 for the currently 
supported releases (VPP 22.06, VPP 22.10) and release artifacts for VPP 
22.06.1 and VPP 22.10.1 uploaded to the FD.io packagecloud.io release 
repository [3].  All release branches prior to 2206 are UNSUPPORTED and 
will NOT undergo maintenance releases.  Packages for each VPP release 
version prior to VPP-22.06.1 SHOULD NOT BE INSTALLED from 
https://packagecloud.io/fdio/release, but should be built from the 
latest source code in the release branch.


Reference:
[0] https://www.cve.org/CVERecord?id=CVE-2022-46397
[1] https://wiki.fd.io/view/TSC:Vulnerability_Management
[2] https://jira.fd.io/browse/VPP-2037
[3] https://packagecloud.io/fdio/release


Thanks,
FD.io Security Response Team

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22587): https://lists.fd.io/g/vpp-dev/message/22587
Mute This Topic: https://lists.fd.io/mt/96953693/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Compilation errors seen in VPP v23.02-rc1 on Centos 8

[Dave Wallace]

Burcu,

Unfortunately, no one in the community has stepped up to maintain the 
Centos build infrastructure after Red Hat left the community a few years 
back.
VPP 20.09 was the last supported release of CentOS-7 and VPP 21.10 was 
the last supported release of CentOS-8 by the FD.io CI jobs.


The build infra for CentOS was left in place and some folks continue to 
update it for Red Hat variants, so hopefully one of those will fix your 
issue.


Patches are always welcome :)

Thanks,
-daw-

On 2/13/23 7:36 AM, Burcu YUKSEL wrote:

Hello,
We have exactly the same errors when we try to compile VPP v23.02 on 
Centos 7. Is there anyone who can solve this problem?


Regards,
Burcu




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22586): https://lists.fd.io/g/vpp-dev/message/22586
Mute This Topic: https://lists.fd.io/mt/96486179/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] February LFN Virtual Developer & Testing Forum

[Dave Wallace]

Folks,

Please register to join the virtual LFN Developer & Test Forum next week!

Thanks,
-daw-


 Forwarded Message 
Subject:[tsc] February LFN Virtual Developer & Testing Forum
Date:   Fri, 10 Feb 2023 08:12:55 -0800
From:   Casey Cain 
To: 	TAC , ODIM TSC 
, ONAP TSC , Anuket TSC 
, XGVela TSC , 
FD.io TSC , ODL TSC , EMCO 
TSC , TF TSC , 
L3AF TSC , Nephio TSC 




Dear LFN Communities,

We are looking forward to seeing you next week for the LFN Developer & 
Testing Forum *on February 13-16, 2023*. *Please remember to register 
 for 
the event; it's free! *


The schedule 
 is now 
available.  You can find further details about the sessions and speakers 
on the event wiki  page.


Please note: Zoom account authentication will be required for this 
event. If you do not already have a Zoom account, you can obtain a free 
account by going to https://www.zoom.us. We know that authentication may 
present challenges for LFN community members in regions where the use of 
free accounts may be disallowed. If such geographic limitations impact 
you, please send an email to eve...@lfnetworking.org 
 in advance of the event for assistance.


The LFN Developer & Testing Forum will begin at 13:00 UTC each day, I've 
included the current schedule here 
- the 
schedule will be updated in real-time as session details are provided.


Join the LFN Tech Slack 
. 
Slack will be used for side discussions, hallway track, and 
track-related discussions.


Additional information regarding the event can be found on the LFN Wiki 
.


We are excited to see you soon.

Best,
Casey Cain
Senior Technical Community Architect
Linux Foundation
_
WeChat: okaru6
WhatsApp: +1.503.779.4519
Book a Meeting w/ Casey 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1736): https://lists.fd.io/g/tsc/message/1736
Mute This Topic: https://lists.fd.io/mt/96879261/675079
Group Owner: tsc+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/tsc/leave/7245241/675079/598713070/xyzzy 
[dwallac...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22577): https://lists.fd.io/g/vpp-dev/message/22577
Mute This Topic: https://lists.fd.io/mt/96891372/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] additional email

[Dave Wallace]

Hi Stanislav,

Please open a case with LF-IT and let me know what the case number is.

https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/37

I will follow up with LF-IT folks to make sure that it is picked up 
promptly.


Thanks,
-daw-

On 2/2/23 4:22 AM, Stanislav Zaikin wrote:

Hello folks,

I have a stupid question. I want to add an additional email (my 
employer asked me to sign commits with my working email). I've added 
new email at linuxfoundation.org , but 
gerrit keeps showing me the error:


Error 405 (Method Not Allowed): realm does not allow adding emails 
Endpoint: /account/self/emails/*


What can I do about it?

I also tried to push with no luck:
remote: ERROR: commit e1d7fd7: email address 
stanislav.zai...@46labs.com is not registered in your account, and you 
lack 'forge committer' permission.

remote: The following addresses are currently registered:
remote: zsta...@gmail.com

--
Best regards
Stanislav Zaikin




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22539): https://lists.fd.io/g/vpp-dev/message/22539
Mute This Topic: https://lists.fd.io/mt/96696880/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] is VPP Gerrit server "No space left on device"

[Dave Wallace]

After gerrit was restarted, git review is working for me: 
https://gerrit.fd.io/r/c/vpp/+/38076 <https://gerrit.fd.io/r/c/vpp/+/38076>


Thanks,
-daw-

On 1/30/23 11:05 AM, Dave Wallace via lists.fd.io wrote:

Folks,

This issue is being actively worked on and is being tracked via the 
following ticket:


https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-25113

Gerrit is being restarted now.

Thanks,
Dave
ps. Support requests for gerrit issues at 
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/37


On 1/29/23 9:28 PM, Xu, Ting wrote:


Hi,

+1, Meet the same issue

*From:* vpp-dev@lists.fd.io  *On Behalf Of *Pei, 
Yulong

*Sent:* Monday, January 30, 2023 10:12 AM
*To:* vpp-dev@lists.fd.io
*Subject:* Re: [vpp-dev] is VPP Gerrit server "No space left on device"
*Importance:* High

When open patch link of gerrit, it pops up below message with web 
browser, and can not find patch contents any more,


*From:* vpp-dev@lists.fd.io  *On Behalf Of *Pei, 
Yulong

*Sent:* Saturday, January 28, 2023 10:30 PM
*To:* vpp-dev 
*Subject:* [vpp-dev] is VPP Gerrit server "No space left on device"

Hello vpp-dev,

Failed to run `git review`,  is VPP Gerrit server "No space left on 
device" ?


# git review

error: remote unpack failed: error No space left on device

fatal: Unpack error, check server log

To ssh://gerrit.fd.io:29418/vpp








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22521): https://lists.fd.io/g/vpp-dev/message/22521
Mute This Topic: https://lists.fd.io/mt/96587880/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] is VPP Gerrit server "No space left on device"

[Dave Wallace]

Folks,

This issue is being actively worked on and is being tracked via the 
following ticket:


https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-25113

Gerrit is being restarted now.

Thanks,
Dave
ps. Support requests for gerrit issues at 
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/37


On 1/29/23 9:28 PM, Xu, Ting wrote:


Hi,

+1, Meet the same issue

*From:* vpp-dev@lists.fd.io  *On Behalf Of *Pei, 
Yulong

*Sent:* Monday, January 30, 2023 10:12 AM
*To:* vpp-dev@lists.fd.io
*Subject:* Re: [vpp-dev] is VPP Gerrit server "No space left on device"
*Importance:* High

When open patch link of gerrit, it pops up below message with web 
browser, and can not find patch contents any more,


*From:* vpp-dev@lists.fd.io  *On Behalf Of *Pei, 
Yulong

*Sent:* Saturday, January 28, 2023 10:30 PM
*To:* vpp-dev 
*Subject:* [vpp-dev] is VPP Gerrit server "No space left on device"

Hello vpp-dev,

Failed to run `git review`,  is VPP Gerrit server "No space left on 
device" ?


# git review

error: remote unpack failed: error No space left on device

fatal: Unpack error, check server log

To ssh://gerrit.fd.io:29418/vpp





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22520): https://lists.fd.io/g/vpp-dev/message/22520
Mute This Topic: https://lists.fd.io/mt/96587880/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Topic for VPP Community Meeting (Jan 24) - DPDK Version for VPP 23.06 Release

[Dave Wallace]

Folks,

Let's discuss the status of the dpdk version for VPP 23.06 Release (dpdk 
22.11 or dpdk 23.03).


In addition to the resolution of the internal API access, NVidia has 
donated ConnectX-7 NICs to the CSIT performance lab which requires the 
latest dpdk version to enable hardware features of the NIC.


Thanks,
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22479): https://lists.fd.io/g/vpp-dev/message/22479
Mute This Topic: https://lists.fd.io/mt/96356937/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [lfn-TAC] Call for Mentors - 2023 Mentorship Program is live

[Dave Wallace]

Folks,

One of the 2023 goals for the FD.io community is to foster growth of 
open source software by mentoring those interested in learning how to 
contribute.


Please consider submitting a mentorship project proposal for your area 
of expertise as described in Casey's email [0].


Thanks,
-daw-  "FD.io TSC Chair"

[0] https://lists.fd.io/g/tsc/message/1732  (use this link to access 
embedded url's)


 Forwarded Message 
Subject:[lfn-TAC] Call for Mentors - 2023 Mentorship Program is live
Date:   Thu, 12 Jan 2023 12:35:58 -0800
From:   Casey Cain 
Reply-To:   lfn-...@lists.lfnetworking.org
To: 	TAC , ODIM TSC 
, onap-tsc , 
anuket-...@lists.anuket.io, XGVela TSC , 
FD.io TSC , TSC , 
emco-...@lists.project-emco.io, TF TSC , L3AF TSC 





Today, we’re excited to open the call for mentors and project proposals 
for the 2023 LF Networking Mentorship Program 
. The 
Program is intended to provide a formal structure to connect mentors and 
student developers from around the globe to contribute their enthusiasm, 
time, and experience toward building sustainable LFN communities.


*Why should you consider mentoring for LF Networking Mentorship Program?*

 * You believe in the value of mentorship in helping new developers to
   navigate open source development, the culture, the tooling, and the
   infrastructure to be productive members of the community.
 * You are passionate about teaching and guiding student developers,
   many of whom may be first time open-source contributors,
 * You are eager to bring new perspectives, ideas, and talent into your
   community and projects.
 * You have a narrowly scoped mentorship project with clear learning
   objectives/outcomes, and a mentee's work and potential contributions
   could add value to the project or community of which you're an
   active developer or maintainer.

*I am interested in mentoring but how do I get started? *

 * Please submit a project proposal
    for consideration by the
   TSC no later than *Friday, March 3rd*.
 * Please reference 2023 program schedule
   as you plan out your project
   and commitment.
 * Please review the project proposal guidelines
    before your submit your
   proposal

*What are the elements the LFN Mentorship Program will implement to 
maximize mentor/mentee collaboration success?*


 * Mentor and mentee onboarding will be conducted at the start of the
   Program
 * Project planning that includes deliverables, milestones, and tasks
   will be completed collaboratively between the mentors and mentees
   during the first two weeks of the program and posted on the wiki to
   increase transparency and accountability.
 * Mentee presentations will be required to sharpen both presentation
   skills and to cultivate the ability to provide constructive feedback
   and critique that’s the norm in the open source community for
   developing technologies collaboratively and openly.
 * Mentee evaluation will be conducted on a regular cadence tied to
   milestone deliverable schedules to help mentors and LFN staff
   formalize and respond to progress.

If you have any questions, please contact mentors...@lfnetworking.org 



We look forward to your submission of a mentorship project and thank you 
in advance for volunteering your time to contribute to training the new 
talent pool in the LF Networking communities.


Best,
Casey Cain
Senior Technical Community Architect
Linux Foundation
_
WeChat: okaru6
WhatsApp: +1.503.779.4519
Book a Meeting w/ Casey 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22461): https://lists.fd.io/g/vpp-dev/message/22461
Mute This Topic: https://lists.fd.io/mt/96233648/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [csit-dev] Bumping dpdk to 22.11 in vpp 23.02 ?

[Dave Wallace]

It is on the VPP meeting wiki page: https://wiki.fd.io/view/VPP/Meeting

Thanks,
-daw-

On 1/12/2023 10:14 AM, Zhang, Fan wrote:


Then I was an hour late :-( Thanks Dave!

Where can I find the new time calendar?

On 1/12/2023 3:12 PM, Dave Wallace wrote:
There was a VPP Community meeting this Tuesday at the new time (5am 
PST) that was lightly attended.





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22459): https://lists.fd.io/g/vpp-dev/message/22459
Mute This Topic: https://lists.fd.io/mt/96211041/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [csit-dev] Bumping dpdk to 22.11 in vpp 23.02 ?

[Dave Wallace]

Hi Fan,

There was a VPP Community meeting this Tuesday at the new time (5am PST) 
that was lightly attended.


Thanks,
-daw-

On 1/12/2023 4:42 AM, Zhang, Fan wrote:

I agree.

It is worth discussing in VPP community call if VPP should access the 
DPDK internal APIs - it surely leaves us more flexibility with the 
price of possible more maintenance effort.


- BTW was there a meeting on this Tuesday? I joined 4 minutes late but 
nobody was there.


Apart from that I believe the patch is in relatively good shape, 
surely lacked testing though.



As of continuous build/sanity between VPP and DPDK main branch - the 
way DPDK function/perf testing the patches now are RC-based, there are 
build tests carried out per-patch based, and there is a crypto unit 
test running nightly with only SW crypto PMDs (@Kai is it still 
running?).


If VPP does the sanity check against DPDK main branch - I personally 
believe VPP may catch some potential DPDK bugs earlier than DPDK 
validation team.


Hence I believe it is a very good idea as a cooperation between two 
projects. This in my opinion also means we need DPDK tech board 
members attending regular meeting with us in case some problems have 
been catched early.



Regards,

Fan

On 1/11/2023 10:29 PM, Andrew Yourtchenko wrote:
My naive impression looking at the change, seems like it’s still work 
in progress with several comments open. Especially with the autumn 
DPDK release IIRC being the “API-breaking” one, looks a bit risky to 
me… I think haste may get us into places we don’t wanna be in. I 
would vote to merge this into master post-RC1 milestone, thus giving 
it more time to soak, and not to put undue strain on anyone.


At the same time I would like to (again?) bring up the idea of doing 
some sort of continuous build/sanity between VPP and DPDK master 
branches -  Fan, I think we discussed this once ? We could then have 
a change ready “just in time” in the future, potentially ? As I am 
not well versed with DPDK - does this idea even make sense ?


--a

On 11 Jan 2023, at 16:53, Maciek Konstantynowicz (mkonstan) via 
lists.fd.io  wrote:


Hi,

On CSIT call just now Kai made us aware of issues with above 
(cryptodev, sat), as captured in this patch:


    37840: dpdk: make impact to VPP for changes in API for DPDK 
22.11 | https://gerrit.fd.io/r/c/vpp/+/37840


23.02 RC1 is next week and in CSIT we start testing at RC1 
milestone, so it’s very last minute …


Also, in the past we got burned by DPDK bump requiring bumping 
firmware versions on FVL and CVL NICs, which for our performance 
testbed fleet is a bit of an operation (e.g. on Arm we have to 
remove the NICs and put them into Xeon machines to do firmware 
upgrade, unless things improved recently).


Asking for views if we could delay dpdk ver bumping to avoid rushing 
it in, especially that there are open issues?


Thoughts?

Cheers,
-Maciek










-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22457): https://lists.fd.io/g/vpp-dev/message/22457
Mute This Topic: https://lists.fd.io/mt/96211041/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Error message on starting vpp

[Dave Wallace]

Merged :)

Thanks,
-daw-

On 1/11/23 9:31 AM, Ahmed Abdelsalam (ahabdels) via lists.fd.io wrote:


I just discussed this with Nathan. Should be merged soon. Cheers!

*From: *Pim van Pelt 
*Date: *Wednesday, 11 January 2023 at 13:37
*To: *vpp-dev@lists.fd.io 
*Cc: *jul...@klaiber.me , Pablo Camarillo 
(pcamaril) , Ahmed Abdelsalam (ahabdels) 


*Subject: *Re: [vpp-dev] Error message on starting vpp

Hoi,

Nathan's fix is still pending and starting VPP at HEAD still emits the 
warning:


pim@hippo:~/src/vpp$ make run
WARNING: STARTUP_CONF not defined or file doesn't exist.
         Running with minimal startup config:  unix { interactive 
cli-listen /run/vpp/cli.sock gid 1000 } dpdk { no-pci } \n
vnet_feature_arc_init:272: feature node 'ip6-lookup' not found (before 
'pt', arc 'ip6-output')


I see the other fixes from this thread were merged (thanks!) but what 
about the OP? Would be prudent to address before Jan 18th :)


groet,

Pim

On Mon, Dec 19, 2022 at 9:49 AM Nathan Skrzypczak 
 wrote:


Hi Xiaodong,

It seems like a '.runs_after' was introduced on a node that does
not belong to the arc in question. [0] should solve this.

(CCingJulian as he is the author of the original patch & sr plugin
maintainers)

Cheers

-Nathan

[0] https://gerrit.fd.io/r/c/vpp/+/37837

Le sam. 3 déc. 2022 à 19:29, Xiaodong Xu  a
écrit :

Hi VPP experts,

I got the following error message when starting vpp recently:

0: vnet_feature_arc_init:272: feature node 'ip6-lookup' not
found (before 'pt', arc 'ip6-output')

I'm using master branch from VPP git repo. By checking the
source code, it seems it might have something to do with the
comment

https://github.com/FDio/vpp/commit/b79d09bbfa93f0f752f7249ad27a08eae0863a6b
and

https://github.com/FDio/vpp/commit/39d6deca5f71ee4fe772c10d76ed5b65d1ebec44


So I remove the two commits from my local repo and the issue
is gone.

The message seems to be harmless, but if anyone who is
familiar with the commits can take a look, I'd appreciate it.

Regards,

Xiaodong





--

Pim van Pelt 
PBVP1-RIPE - http://www.ipng.nl/





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22447): https://lists.fd.io/g/vpp-dev/message/22447
Mute This Topic: https://lists.fd.io/mt/95432703/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Error message on starting vpp

[Dave Wallace]

Merged :)

Thanks,
-daw-

On 1/10/2023 4:24 PM, Ahmed Abdelsalam (ahabdels) via lists.fd.io wrote:


Hi Xiaodong,

The warning has been fixed here https://gerrit.fd.io/r/c/vpp/+/37874

Cheers,

Ahmed

*From: *Xiaodong Xu 
*Date: *Thursday, 29 December 2022 at 01:55
*To: *vpp-dev@lists.fd.io 
*Cc: *jul...@klaiber.me , Pablo Camarillo 
(pcamaril) , Ahmed Abdelsalam (ahabdels) 


*Subject: *Re: [vpp-dev] Error message on starting vpp

Hi Nathan,

The issue is gone after your patch is applied. Thanks for the fix. In 
the meantime, there is actually a compile warning which can be fixed 
by the following change:


@@ -124,6 +124,7 @@
   n_left_to_next -= 1;
   timestamp_64_t t64;

+  unix_time_now_nsec_fraction (&t64.sec, &t64.nsec);
   b0 = vlib_get_buffer (vm, bi0);
   iface = vnet_buffer (b0)->sw_if_index[VLIB_TX];
   ls = sr_pt_find_iface (iface);
@@ -131,7 +132,6 @@
     {
       en0 = vlib_buffer_get_current (b0);
       ip0 = (void *) (en0 + 1);
-      unix_time_now_nsec_fraction (&t64.sec, &t64.nsec);
       pt_midpoint_processing (vm, node, b0, ip0, ls, t64);
       pt_behavior = PT_BEHAVIOR_MID;
     }

Not sure if it makes sense for you to incorporate the change into your 
patch.


Regards,

Xiaodong

On Mon, Dec 19, 2022 at 12:49 AM Nathan Skrzypczak 
 wrote:


Hi Xiaodong,

It seems like a '.runs_after' was introduced on a node that does
not belong to the arc in question. [0] should solve this.

(CCingJulian as he is the author of the original patch & sr plugin
maintainers)

Cheers

-Nathan

[0] https://gerrit.fd.io/r/c/vpp/+/37837

Le sam. 3 déc. 2022 à 19:29, Xiaodong Xu  a
écrit :

Hi VPP experts,

I got the following error message when starting vpp recently:

0: vnet_feature_arc_init:272: feature node 'ip6-lookup' not
found (before 'pt', arc 'ip6-output')

I'm using master branch from VPP git repo. By checking the
source code, it seems it might have something to do with the
comment

https://github.com/FDio/vpp/commit/b79d09bbfa93f0f752f7249ad27a08eae0863a6b
and

https://github.com/FDio/vpp/commit/39d6deca5f71ee4fe772c10d76ed5b65d1ebec44


So I remove the two commits from my local repo and the issue
is gone.

The message seems to be harmless, but if anyone who is
familiar with the commits can take a look, I'd appreciate it.

Regards,

Xiaodong








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22441): https://lists.fd.io/g/vpp-dev/message/22441
Mute This Topic: https://lists.fd.io/mt/95432703/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP AF_PACKET (aka host-interface) driver is now a plugin

[Dave Wallace]

Folks,

As part of the ongoing effort to move features from vpp/src/vnet to 
plugins (tracked Jira VPP-2040 [0]), the gerrit change [1] moving the 
VPP AF_PACKET (aka host-interface) driver to a plugin has just been 
merged into master.


If you use the VPP AF_PACKET driverand have the stanza 'plugin default 
{disable}' in your startup.conf (if not, you probably should consider 
it) then you'll have to add 'plugin af_packet_plugin.so {enable}' to the 
plugins stanza in your startup.conf for the AF_PACKET plugin to be 
loaded from now on.


Thanks,
-daw-

[0] https://jira.fd.io/browse/VPP-2040
[1] https://gerrit.fd.io/r/c/vpp/+/37830

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22355): https://lists.fd.io/g/vpp-dev/message/22355
Mute This Topic: https://lists.fd.io/mt/95813067/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP & HICN docs verify jobs now upload generated docs to a 7-day retention S3 bucket

[Dave Wallace]

Folks,

The VPP and HICN docs verify jobs now upload the generated docs for each 
patch to a 7-day retention bucket in Amazon S3 storage. The upload URL 
for the docs is the same as the log URL for the docs job except that the 
domain name is 's3-docs-7day.fd.io' instead of 's3-logs.fd.io'.


For example, the following VPP docs job:

https://s3-logs.fd.io/vex-yul-rot-jenkins-1/vpp-docs-verify-master-ubuntu2204-x86_64/742/

uploaded the VPP documentation generated for the associated patch to:

https://s3-docs-7day.fd.io/vex-yul-rot-jenkins-1/vpp-docs-verify-master-ubuntu2204-x86_64/742/


Similarly, the HICN docs job:

https://s3-logs.fd.io/vex-yul-rot-jenkins-1/hicn-docs-verify-master-ubuntu2004-x86_64/433/

uploaded the HICN documentation generated for the associated patch to:

https://s3-docs-7day.fd.io/vex-yul-rot-jenkins-1/hicn-docs-verify-master-ubuntu2004-x86_64/433/


If you attempt to access a URL for a docs verify job that is more than 7 
days old, then you will get a 404 error:


https://s3-docs-7day.fd.io/vex-yul-rot-jenkins-1/vpp-docs-verify-master-ubuntu2204-x86_64/658

 %< 
404 Not Found

    Code: NoSuchKey
    Message: The specified key does not exist.
    Key: vex-yul-rot-jenkins-1/vpp-docs-verify-master-ubuntu2204-x86_64/658
    RequestId: VZSP8G8QK91WF3AB
    HostId: 
X6+NkeAuRXpVGgDCq27Yqg7vbg6VdlyqS1utS+nPrJjCjIjDdQ+p6INLPuPfjHdMIWUW40ANht4=


An Error Occurred While Attempting to Retrieve a Custom Error Document

    Code: NoSuchKey
    Message: The specified key does not exist.
    Key: error.html
 %< 

Thanks,
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22321): https://lists.fd.io/g/vpp-dev/message/22321
Mute This Topic: https://lists.fd.io/mt/95627241/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [csit-dev] Core isolation on kernel command line deprecated

[Dave Wallace]

Hi Juraj,

+ vpp-dev@lists.fd.io

For those curious to learn more, here is the cpusets kernel 
documentation [0] and cpuset manpage [1].


Thanks for the heads up!
-daw-

[0] 
https://www.kernel.org/doc/Documentation/admin-guide/cgroup-v1/cpusets.rst

[1] https://manpages.ubuntu.com/manpages/jammy/man7/cpuset.7.html

On 12/5/2022 5:44 AM, Juraj Linkeš wrote:


Hello CSIT devs,

While looking for possible causes for the 3n-tsh VM testcase timeouts, 
Tianyu from arm found out that the isolcpus kernel command line 
parameter has been deprecated. It seems that no cores are actually 
being isolated:


# altra SUT

jlinkes@jlinkes:~/workspace$ alt1-perf cat /proc/self/status | grep 
Cpus_allowed_list


Cpus_allowed_list:  0-159

# icelake SUT

jlinkes@jlinkes:~/workspace$ ssh testuser@10.30.51.75 cat 
/proc/self/status | grep Cpus_allowed_list


Cpus_allowed_list:  0-127

# snowridge SUT

jlinkes@jlinkes:~/workspace$ ssh testuser@10.30.51.93 cat 
/proc/self/status | grep Cpus_allowed_list


Cpus_allowed_list:  0-23

# cascadelake SUT

jlinkes@jlinkes:~/workspace$ ssh testuser@10.32.8.18 cat 
/proc/self/status | grep Cpus_allowed_list


Cpus_allowed_list:  0-95

The kernel docs [0] themselves mention that the parameter has been 
deprecated and we should use cpusets instead.


Looks like the deprecation could have broader implications in CSIT.

Regards,

Juraj

[0] 
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22320): https://lists.fd.io/g/vpp-dev/message/22320
Mute This Topic: https://lists.fd.io/mt/95625755/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] PSA: host stack active opens from first worker

[Dave Wallace]

Florin,

Most Excellent -- very nice work on improving the VPP Hoststack! :D

Thanks,
-daw-

On 12/1/22 18:17, Florin Coras wrote:

Hi folks,

It’s been many months and patches at this point but once [1] is 
merged, session layer will accept connects from both main, with worker 
barrier, and first worker. Preference is now for the latter, 
especially if CPS performance is critical.


There should be no need to change existing apps. In particular, vcl 
applications will transparently leverage this improvement while 
builtin applications should still work even if they rely on main 
thread for the connects.


The reason why this is a PSA is because in spite of all testing, 
there’s still a chance some corner case are not supported, some 
transports might be buggy now or just plain old bugs might’ve slipped 
in. Should you hit any issues, or have any additional comments, feel 
free to reach out via this thread or directly.


Benefits of this improvement are:
- no more main thread polling under heavy connect load. Under certain 
circumstances, main can still be used to perform the connects but this 
should be the exception not the norm.

- higher CPS performance.

And to be precise, regarding the CPS performance, on my skylake 
testbed using 40Gbps nics:
o) prior to [2], albeit note that several other changes that might’ve 
affected performance have already gone in:

- 1 worker vpp, pre-warmup: 80k post warmup: 105k
- 4 worker vpp, pre-warmup: 135k post-warmup: 230k
o) after change:
- 1 worker vpp, pre-warmup: 110k, post warmup: 165k
- 4 worker vpp, pre-warmup: 150k, post warmup: 360k

You can try to reproduce these results using this [2].

Regards,
Florin

[1] https://gerrit.fd.io/r/c/vpp/+/35713/
[2] 
https://wiki.fd.io/view/VPP/HostStack/EchoClientServer#TCP_CPS_measurement








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22271): https://lists.fd.io/g/vpp-dev/message/22271
Mute This Topic: https://lists.fd.io/mt/95395667/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] vpp-gerrit-report with auto-abandonment

[Dave Wallace]

Folks,

As discussed at this week's VPP Community Meeting, I have completed 
development of gerrit change auto-abandonment and incorporated the 
reporting of auto-abandoned gerrit changes in the daily 
vpp-gerrit-report [0] generation scripts.


The gerrit instance is being stressed with the large number of open 
changes and leaving hundreds of open gerrit changes reduces the 
signal-to-noise ration for reviewers. Abandoned changes are not deleted 
from gerrit, so they can always be restored.  If you want them to remain 
visible, then restore the change and mark them either as 
work-in-progress (publicly visible) or private (visible to reviewers + 
author). This will remove them from regular CI processing that gerrit 
does and help improve gerrit performance.


Alternatively, gerrit changes that are to be merged can simply be 
rebased (which they should be prior to merging to ensure testing with 
the latest codebase prior to merge).


I have also written a shellscript to search the repo for gerrit changes 
that were auto-abandoned by the daily scripts to make it easy to find 
and restore auto-abandoned changes.  Here's how to use it:


1. git clone https://github.com/vpp-dev/vpp-gerrit-report && cd 
vpp-gerrit-report

2. ./scripts/find_abandoned_changes.sh 

Here is a sample output of the shellscript:

/scratch/dwallacelf/github.com/vpp-dev/vpp-gerrit-report$ 
./scripts/find_abandoned_changes.sh dwallac...@gmail.com


**Dave Wallace** :

Found in 
https://github.com/vpp-dev/vpp-gerrit-report/blob/6d844808a029747406e2e2ca39b3c6d62e56e09a/VPP-GERRIT-REPORT.rst
  | `33727 <https:gerrit.fd.io/r/c/vpp/+/33727>`_ [A 0]: tests: 
relicense
  | `33707 <https:gerrit.fd.io/r/c/vpp/+/33707>`_ [A 0]: papi: 
relicense


Found in 
https://github.com/vpp-dev/vpp-gerrit-report/blob/33cdcd6ef678873c9b5feacb81296ac6243dc352/VPP-GERRIT-REPORT.rst
  | `37088 <https:gerrit.fd.io/r/c/vpp/+/37088>`_ [A 0]: misc: 
patch to test CI infra changes


Found in 
https://github.com/vpp-dev/vpp-gerrit-report/blob/4f1f0aeed38480d39c188a2dc0d338de356a9818/VPP-GERRIT-REPORT.rst
  | `37088 <https:gerrit.fd.io/r/c/vpp/+/37088>`_ [A 0]: misc: 
patch to test CI infra changes


Found in 
https://github.com/vpp-dev/vpp-gerrit-report/blob/88e5d41324dec032db40eba4639573f2f6d37cca/VPP-GERRIT-REPORT.rst
  | `37088 <https:gerrit.fd.io/r/c/vpp/+/37088>`_ [A 0]: misc: 
patch to test CI infra changes



Thanks,
-daw-

[0] https://github.com/vpp-dev/vpp-gerrit-report

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22235): https://lists.fd.io/g/vpp-dev/message/22235
Mute This Topic: https://lists.fd.io/mt/95224721/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] RFC: move the “1”st instance of the community meeting 3 hours earlier to reduce impact for earlier time zone

[Dave Wallace]

+1

On 11/22/22 11:28 AM, Andrew Yourtchenko wrote:

Hi all,

It came up that the current time of the community meeting is extremely 
unfriendly for our community members on China timezone - it makes it midnight 
their time.

So, as per discussion on the call today, I would like to propose to move every 
other of the meetings (the one in the second Tuesday of the month) three hours 
earlier.

I would also suggest that this proposal take effect starting with the upcoming 
meeting on December 13th.

Thoughts ?

--a




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#2): https://lists.fd.io/g/vpp-dev/message/2
Mute This Topic: https://lists.fd.io/mt/9526/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Gerrit Review Id 37642

[Dave Wallace]

Merged.

Thanks for your contribution.
-daw-

On 11/11/2022 1:51 AM, lihuawei wrote:

Hi community maintainers,
I have added a fix as gerrit review id 37642.

*gerrit link: https://gerrit.fd.io/r/c/vpp/+/37642*

*short description: *fix lib install dir and add vat2 lib install when 
build rpm.


Please have a look and review.

Best regards,
Huawei LI




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22174): https://lists.fd.io/g/vpp-dev/message/22174
Mute This Topic: https://lists.fd.io/mt/94953939/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Volunteers to join the FD.io Security Response Team

[Dave Wallace]

Folks,

The TSC is looking for volunteers from the community to join the 
Security Response Team [0].


If you have any experience with open source Vulnerability Reporting 
Processes and would like to help the FD.io community by joining the 
Security Response Team, then please respond to me directly via email.


Thanks,
-daw-, TSC Chairperson

[0] https://wiki.fd.io/view/Security

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22160): https://lists.fd.io/g/vpp-dev/message/22160
Mute This Topic: https://lists.fd.io/mt/94938558/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP Gerrit Report Enhancement

[Dave Wallace]

Hi Andrew,

Hmmm, the fix was to get_changes.py to not download changes with -2 
(before classification / report generation), so it would appear to be a 
bug in the gerrit api.  What change was it?


It worked for two of my changes which are set to -2 (33707 & 33727).

BTW, if you prefer to retain -2 changes in author's section, then I will 
need to refactor my fix to elide the -2 changes during report generation.


Thanks,
-daw-

On 11/5/2022 5:34 AM, Andrew Yourtchenko wrote:

Hi Dave,

Very cool! I assume this change reflects only for the changes showing 
in component maintainers’ lists, and not the authors ? (I saw one -2 
change in my list in this report, which is the “correct” behavior imo, 
so just making sure it is a feature and not a bug :)


--a


On 4 Nov 2022, at 16:13, Dave Wallace  wrote:

 Folks,

I have enhanced the VPP Gerrit Report to not include gerrit changes 
which are marked 'Code-review -2'.  Today's report [0] reflects that 
improvement.


Please let me know if you have any feedback on this report.

Thanks,
-daw-

[0] https://github.com/vpp-dev/vpp-gerrit-report








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22135): https://lists.fd.io/g/vpp-dev/message/22135
Mute This Topic: https://lists.fd.io/mt/94807675/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP Gerrit Report Enhancement

[Dave Wallace]

Folks,

I have enhanced the VPP Gerrit Report to not include gerrit changes 
which are marked 'Code-review -2'.  Today's report [0] reflects that 
improvement.


Please let me know if you have any feedback on this report.

Thanks,
-daw-

[0] https://github.com/vpp-dev/vpp-gerrit-report

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22124): https://lists.fd.io/g/vpp-dev/message/22124
Mute This Topic: https://lists.fd.io/mt/94807675/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP release 22.10 is complete !

[Dave Wallace]

Most Excellent!

Congratulations to the VPP Community for another high quality, on time, 
release.


Thanks to Andrew for his work driving the release process to a 
successful conclusion.

-daw-

On 10/26/22 14:04, Andrew Yourtchenko wrote:

Hi all,

VPP release 22.10 is complete !

You can have a look at the release notes at
https://docs.fd.io/vpp/22.10/aboutvpp/releasenotes/v22.10.html

The artifacts are available at the https://packagecloud.io/fdio/release

Thanks to Dave Wallace and Vanessa Valderrama for the assistance in 
preparing the release, and to all of the VPP contributors for their 
valuable work!


--a /* your friendly 22.10 release manager */






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22078): https://lists.fd.io/g/vpp-dev/message/22078
Mute This Topic: https://lists.fd.io/mt/94587728/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] FD.io VPP (master branch) Gerrit Change Report is now being generated daily

[Dave Wallace]

Folks,

I have completed automating the generation of the VPP Gerrit Change 
Report which will now be updated daily.


The source code and latest report can be found in the repo:
https://github.com/vpp-dev/vpp-gerrit-report

The daily report can be found in the file, VPP-GERRIT-REPORT.rst and its 
contents are also included in the README.rst as a convenience.


Please let me know if this report is useful and any suggestions to make 
it more better.


Thanks,
-daw-

[0] : 
https://github.com/vpp-dev/vpp-gerrit-report/blob/main/VPP-GERRIT-REPORT.rst


On 10/12/22 10:57, Dave Wallace via lists.fd.io wrote:
New report generated today 
https://gist.github.com/dwallacelf/90f2c3b1a2a59b5bc186d89650826f6b


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-

On 9/27/22 10:09 AM, Dave Wallace via lists.fd.io wrote:
New report generated today: 
https://gist.github.com/dwallacelf/4147e4d26ca154698ea3c881426160c3


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-


On 9/14/22 3:55 PM, Dave Wallace via lists.fd.io wrote:
New report generated today: 
https://gist.github.com/dwallacelf/c60164b8affb65fdef690d7500d8de1a


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-

On 9/1/22 4:04 PM, Dave Wallace via lists.fd.io wrote:

Folks,

I have updated a gerrit change report generator authored by Ole 
Troan [0] to produce a report that categorizes the state of the 
Gerrit review queue.  Each gerrit change is labeled with the 
following status:


== ===
Status Complete    Needs To Be Addressed
== ===
V - verified   v - not verified
E - not expired    e - expired
C - no unresolved comments c - comments not resolved
R - reviewed/approved  r - review incomplete
# - days since update  # - days since update > 30
== ===

Example: [VECr 23]
    - Verified
    - Not Expired
    - No unresolved comments
    - Review incomplete (Code-Review < +1)
    - 23 days since last update

The report generator sorts the gerrit changes into three categories 
based on the state and the person or group required to perform the 
next action:


- Committers:
  Status [VECR xx]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & approved by a maintainer.
  Action: A committer should do a final review and submit the 
change or provide comment(s).


- Maintainers:
  Status [VECr]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & not reviewed

  Action: The Maintainer should do a code review

- Authors:
  Status : Gerrit Changes that are either not verified, 
expired, or comments not resolved
  Action: Author should rebase the change, fix verification errors, 
and/or resolve comments to move the status to [VECr]


Here is a gist of the report generated today: 
https://gist.github.com/dwallacelf/8f6e7c0ea7ae07cae1460cf49b631e6f


In the near future, I will add this to a github action to generate 
an updated report daily.


Please review the report and look for gerrit changes which require 
your attention.

All feedback welcome.

Thanks,
-daw-

[0] https://github.com/dwallacelf/gerrit-review













-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22068): https://lists.fd.io/g/vpp-dev/message/22068
Mute This Topic: https://lists.fd.io/mt/94549931/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Move VNET features to plugins

[Dave Wallace]

Hi Neale,

Comments inline...

On 10/17/22 10:46 PM, Neale Ranns wrote:


Hi Dave,

I fully support pluginification 😊

Is it fair though to say that if the remaining functions of vnet have 
a dependency on one of the modules below then that module is not a 
good candidate to move to a plugin?



[daw] Agreed.

If any function in the subtask list lands into this category I would 
recommend the following:

    1. Document the dependency in a comment of the subtask
    2. Mark the sub-task as 'Will Not Do'.

That way we have a list of dependencies that could potentially be 
refactored at a later time to allow the feature(s) to be moved to a plugin.


I thinking about the dependency between IPIP and TEIB. Some of the 
IPIP functionality (i.e. p2p tunnels) can be provided without TEIB but 
some cannot (i.e. p2mp tunnels).


  * Any thoughts on infrastructure to ease plugin on plugin
dependencies. For example I seem to recall a system that used a
‘registry’ that the producer would populate and the consumer would
invoke and that invocation would be sane in the absence of a producer.

[daw] Ole brought this up during our internal discussion with the 
reference to the same mechanism. I forgot to mention that I also added a 
Jira issue [2] to address this requirement.  Any features requiring 
cross-plugin dependency management should be marked as blocked by [2].  
Let's use [2] to capture the requirements and assign a volunteer to lead 
the implementation.



 *


  * How do we [unit] test the various combinations of loaded plugins?
Perhaps the default is not to load any plugins and the test-case
specifies which set to load.



[daw] I agree that it would be best to default to not loading any 
plugins and have testcase specifications load the appropriate plugins as 
required.



Thanks,
-daw-

[2] https://jira.fd.io/browse/VPP-2060


/neale

*From: *vpp-dev@lists.fd.io  on behalf of Dave 
Wallace via lists.fd.io 

*Date: *Tuesday, 18 October 2022 at 08:57
*To: *vpp-dev 
*Subject: *[vpp-dev] Move VNET features to plugins

Folks,

There has been a long standing chore to move VNET features to plugins
for which I've created a Jira ticket [0] to coordinate getting this work
done for VPP 23.02 release.

Can the maintainers of the VNET features [1] please sign up for the
associated subtask in [0] and complete the work before the 23.02 RC1
milestone (01/18/2023).  It would be great to get this done before the
end of 2022 to avoid a large influx of changes in early January.

Thanks in advance for your help!
-daw-

[0] 
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjira.fd.io%2Fbrowse%2FVPP-2040&data=05%7C01%7Cneale%40graphiant.com%7C888ed5dcf8744e783a0708dab08a892d%7C162101cdceb34e62ab2e3abc7aeede47%7C0%7C0%7C638016406459814597%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qtN1mKiFVnGYzcW3lAsg7%2FSFLd5%2Bl8NICwMuqrG0m1M%3D&reserved=0 
<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjira.fd.io%2Fbrowse%2FVPP-2040&data=05%7C01%7Cneale%40graphiant.com%7C888ed5dcf8744e783a0708dab08a892d%7C162101cdceb34e62ab2e3abc7aeede47%7C0%7C0%7C638016406459814597%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qtN1mKiFVnGYzcW3lAsg7%2FSFLd5%2Bl8NICwMuqrG0m1M%3D&reserved=0>


[1] Current set of VNET features to be moved:
 BFD
 BIER
 CRYPTO
 GRE
 IPFIX-EXPORT
 IPIP
 IPSEC
 LAWFUL-INTERCEPT
 MPLS
 OSI
 POLICER
 PPP
 QOS
 SRMPLS
 SRV6
 TEIB
 TLS
 VXLAN
 VXLAN-GPE
 DEVICES:
     AF_PACKET
     PIPE
     TAP
     VIRTIO





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22048): https://lists.fd.io/g/vpp-dev/message/22048
Mute This Topic: https://lists.fd.io/mt/94396253/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Move VNET features to plugins

[Dave Wallace]

Folks,

There has been a long standing chore to move VNET features to plugins 
for which I've created a Jira ticket [0] to coordinate getting this work 
done for VPP 23.02 release.


Can the maintainers of the VNET features [1] please sign up for the 
associated subtask in [0] and complete the work before the 23.02 RC1 
milestone (01/18/2023).  It would be great to get this done before the 
end of 2022 to avoid a large influx of changes in early January.


Thanks in advance for your help!
-daw-

[0] https://jira.fd.io/browse/VPP-2040

[1] Current set of VNET features to be moved:
    BFD
    BIER
    CRYPTO
    GRE
    IPFIX-EXPORT
    IPIP
    IPSEC
    LAWFUL-INTERCEPT
    MPLS
    OSI
    POLICER
    PPP
    QOS
    SRMPLS
    SRV6
    TEIB
    TLS
    VXLAN
    VXLAN-GPE
    DEVICES:
        AF_PACKET
        PIPE
        TAP
        VIRTIO



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22042): https://lists.fd.io/g/vpp-dev/message/22042
Mute This Topic: https://lists.fd.io/mt/94396253/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Build VPP with clean Jenkins workspace

[Dave Wallace]

Marcel,

The build failure was caused by the fact that your gerrit change was not 
based on top of master and because there was another gerrit change 
merged [0] which changed the PKG_SUFFIX in build/external/Makefile [0].  
Thus build was not updating vpp-ext-deps in the CI docker container 
because the vpp-ext-dep version (22.03-3) was the same as that which was 
already installed by the CI pre-build scripts.


I rebased 37358 which resolves the cmake failure.

Thanks,
-daw-

[0] https://github.com/FDio/vpp/blob/master/build/external/Makefile#L23

On 10/11/22 17:43, Cornu, Marcel D wrote:


Hi all,

I submitted a patch toadd support for a new version of the ipsecmb 
library, used by the crypto_ipsecmb plugin.


https://gerrit.fd.io/r/c/vpp/+/37358 



A previous build downloaded and built the new version of the library 
and the build passed, great!


Subsequentbuilds are now failing stating thatsymbols from the new 
library version can’t be found.


It seems like an old library version is being picked up by the build.

I am wondering if workspaces are isolated? Or is it possible that a 
previously installed (old) version of the library could be installed 
and accessible in the workspace?


Is there any way to wipe the Jenkins workspace and start from a clean 
state?


Thanks,

Marcel





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22016): https://lists.fd.io/g/vpp-dev/message/22016
Mute This Topic: https://lists.fd.io/mt/94269242/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] 2022-10-12 FD.io VPP (master branch) Gerrit Change Report

[Dave Wallace]

New report generated today 
https://gist.github.com/dwallacelf/90f2c3b1a2a59b5bc186d89650826f6b


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-

On 9/27/22 10:09 AM, Dave Wallace via lists.fd.io wrote:
New report generated today: 
https://gist.github.com/dwallacelf/4147e4d26ca154698ea3c881426160c3


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-


On 9/14/22 3:55 PM, Dave Wallace via lists.fd.io wrote:
New report generated today: 
https://gist.github.com/dwallacelf/c60164b8affb65fdef690d7500d8de1a


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-

On 9/1/22 4:04 PM, Dave Wallace via lists.fd.io wrote:

Folks,

I have updated a gerrit change report generator authored by Ole 
Troan [0] to produce a report that categorizes the state of the 
Gerrit review queue.  Each gerrit change is labeled with the 
following status:


== ===
Status Complete    Needs To Be Addressed
== ===
V - verified   v - not verified
E - not expired    e - expired
C - no unresolved comments c - comments not resolved
R - reviewed/approved  r - review incomplete
# - days since update  # - days since update > 30
== ===

Example: [VECr 23]
    - Verified
    - Not Expired
    - No unresolved comments
    - Review incomplete (Code-Review < +1)
    - 23 days since last update

The report generator sorts the gerrit changes into three categories 
based on the state and the person or group required to perform the 
next action:


- Committers:
  Status [VECR xx]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & approved by a maintainer.
  Action: A committer should do a final review and submit the change 
or provide comment(s).


- Maintainers:
  Status [VECr]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & not reviewed

  Action: The Maintainer should do a code review

- Authors:
  Status : Gerrit Changes that are either not verified, 
expired, or comments not resolved
  Action: Author should rebase the change, fix verification errors, 
and/or resolve comments to move the status to [VECr]


Here is a gist of the report generated today: 
https://gist.github.com/dwallacelf/8f6e7c0ea7ae07cae1460cf49b631e6f


In the near future, I will add this to a github action to generate 
an updated report daily.


Please review the report and look for gerrit changes which require 
your attention.

All feedback welcome.

Thanks,
-daw-

[0] https://github.com/dwallacelf/gerrit-review










-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22008): https://lists.fd.io/g/vpp-dev/message/22008
Mute This Topic: https://lists.fd.io/mt/94282673/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] vpp-debug-verify job enabled per-patch non-voting

[Dave Wallace]

Folks,

After removing the most egregious make test testcases which fail on the 
vpp_debug image, I have re-instated the vpp-debug-verify job as 
non-voting per-patch [0].  I will continue to work on fixing or removing 
testcases which are failing on non-related patches.


Please look for failures reported like this:
https://jenkins.fd.io/job/vpp-debug-verify-master-ubuntu2204-x86_64/1021/ 
: FAILURE (skipped)


Thanks,
-daw-

[0] https://jenkins.fd.io/job/vpp-debug-verify-master-ubuntu2204-x86_64 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22007): https://lists.fd.io/g/vpp-dev/message/22007
Mute This Topic: https://lists.fd.io/mt/94281766/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] 2022-09-27 FD.io VPP (master branch) Gerrit Change Report

[Dave Wallace]

New report generated today: 
https://gist.github.com/dwallacelf/4147e4d26ca154698ea3c881426160c3


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-


On 9/14/22 3:55 PM, Dave Wallace via lists.fd.io wrote:
New report generated today: 
https://gist.github.com/dwallacelf/c60164b8affb65fdef690d7500d8de1a


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-

On 9/1/22 4:04 PM, Dave Wallace via lists.fd.io wrote:

Folks,

I have updated a gerrit change report generator authored by Ole Troan 
[0] to produce a report that categorizes the state of the Gerrit 
review queue.  Each gerrit change is labeled with the following status:


== ===
Status Complete    Needs To Be Addressed
== ===
V - verified   v - not verified
E - not expired    e - expired
C - no unresolved comments c - comments not resolved
R - reviewed/approved  r - review incomplete
# - days since update  # - days since update > 30
== ===

Example: [VECr 23]
    - Verified
    - Not Expired
    - No unresolved comments
    - Review incomplete (Code-Review < +1)
    - 23 days since last update

The report generator sorts the gerrit changes into three categories 
based on the state and the person or group required to perform the 
next action:


- Committers:
  Status [VECR xx]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & approved by a maintainer.
  Action: A committer should do a final review and submit the change 
or provide comment(s).


- Maintainers:
  Status [VECr]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & not reviewed

  Action: The Maintainer should do a code review

- Authors:
  Status : Gerrit Changes that are either not verified, 
expired, or comments not resolved
  Action: Author should rebase the change, fix verification errors, 
and/or resolve comments to move the status to [VECr]


Here is a gist of the report generated today: 
https://gist.github.com/dwallacelf/8f6e7c0ea7ae07cae1460cf49b631e6f


In the near future, I will add this to a github action to generate an 
updated report daily.


Please review the report and look for gerrit changes which require 
your attention.

All feedback welcome.

Thanks,
-daw-

[0] https://github.com/dwallacelf/gerrit-review







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21935): https://lists.fd.io/g/vpp-dev/message/21935
Mute This Topic: https://lists.fd.io/mt/93950487/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] 'make test' failures on ubuntu2204 & debian11

[Dave Wallace]

Folks,

Due to the upgrade to ubuntu-22.04 and re-enabling multi-worker tests on 
debian-11 CI jobs, there have been a number of regressions in 'make 
test' (some intermittent failures, other hard failures).


I have disabled the offending tests [0] and rebased all of the 
outstanding gerrit changes which had failed due to these 'make test' 
failures.  See below list of jobs skipped on debian-11 [1] and 
ubuntu-22.04 [2]


I will be reaching out to maintainers to help troubleshoot, fix, and 
re-enable all of these tests and will plan to discuss this effort at 
tomorrow's VPP Community Meeting


Thanks,
-daw-

[0] https://gerrit.fd.io/r/c/vpp/+/37198
https://gerrit.fd.io/r/c/vpp/+/37144

[1] Tests Disabled on Debian-11:
- %< -
fixme-on-debian11-console-timestamp.log:01:40:53  FIXME on Debian-11: 
Wireguard Test Case [2 worker threads]
fixme-on-debian11-console-timestamp.log:01:40:53  FIXME on Debian-11: 
Wireguard Tests in multi worker setup [2 worker threads]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: test ikev2 responder - rekey [main thread only]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: test ikev2 responder - rekey repeat [main thread 
only]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: test ikev2 responder - pre shared key auth [main 
thread only]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: test ikev2 responder - rekey with key exchange 
[main thread only]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: Dead peer detection test [main thread only]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: test ikev2 responder - rekey repeat with key 
exchange [main thread only]
fixme-on-debian11-console-timestamp.log:02:04:28  FIXME on Debian-11: 
FIXME with VPP workers: test ikev2 responder - non-default table id 
[main thread only]
fixme-on-debian11-console-timestamp.log:02:08:18  FIXME on Debian-11: 
NAT44EI Test Cases [2 worker threads]
fixme-on-debian11-console-timestamp.log:02:08:44  FIXME on Debian-11: 
SOLO RUN: Memif Test Case [2 worker threads]
fixme-on-debian11-console-timestamp.log:02:09:54  FIXME on Debian-11: 
SOLO RUN: Bidirectional Forwarding Detection (BFD) [2 worker threads]
fixme-on-debian11-console-timestamp.log:02:13:19  FIXME on Debian-11: 
FIXME with VPP workers: SOLO RUN: Template verification, timer tests 
[main thread only]

- %< -

[2] Tests Disabled on Ubuntu-22.04:
- %< -
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: ipsecmb ESNon ARon AES-CBC-256/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNoff ARon AES-CBC-128/MD5-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARon AES-CBC-192/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARon AES-CBC-128/MD5-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNoff ARoff AES-CBC-192/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: ipsecmb ESNon ARon AES-CBC-192/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARon AES-CBC-256/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNoff ARon 3DES-CBC/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNoff ARoff AES-CBC-128/MD5-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARoff AES-CBC-128/MD5-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNoff ARoff 3DES-CBC/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNoff ARoff AES-CBC-256/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: ipsecmb ESNon ARon AES-CBC-128/MD5-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARoff AES-CBC-256/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARoff AES-CBC-192/SHA1-96 IPSec test [main 
thread only]
fixme-on-ubuntu2204-console-timestamp.log:01:38:53  FIXME on 
Ubuntu-22.04: native ESNon ARon 3DES-CBC/SHA1-96 IPSec test [main thread 
only]
fixme-on-ubuntu2204

[vpp-dev] Input on VPP 'make test' use cases

[Dave Wallace]

Folks,

In preparation for refactoring 'make test', I'd like to get feedback on 
the which features in test/Makefile are being used and the context for 
them (e.g. FD.io CI, downstream CI, local testing, test development).


I've created a wiki page [0] to capture the feedback.  Please edit the 
wiki page and increment any of the cases in the matrix which you use.


If you have any additional use cases that you would like to be covered, 
please add a comment at the bottom of the page.


I will plan to discuss the results of this at the next VPP community 
meeting.


Thanks,
-daw-

[0] https://wiki.fd.io/view/VPP/2022_Make_Test_Use_Case_Poll

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21899): https://lists.fd.io/g/vpp-dev/message/21899
Mute This Topic: https://lists.fd.io/mt/93729368/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] 2022-09-14 FD.io VPP (master branch) Gerrit Change Report

[Dave Wallace]

New report generated today: 
https://gist.github.com/dwallacelf/c60164b8affb65fdef690d7500d8de1a


Please review the report and update/review/merge changes as appropriate.

Thanks,
-daw-

On 9/1/22 4:04 PM, Dave Wallace via lists.fd.io wrote:

Folks,

I have updated a gerrit change report generator authored by Ole Troan 
[0] to produce a report that categorizes the state of the Gerrit 
review queue.  Each gerrit change is labeled with the following status:


== ===
Status Complete    Needs To Be Addressed
== ===
V - verified   v - not verified
E - not expired    e - expired
C - no unresolved comments c - comments not resolved
R - reviewed/approved  r - review incomplete
# - days since update  # - days since update > 30
== ===

Example: [VECr 23]
    - Verified
    - Not Expired
    - No unresolved comments
    - Review incomplete (Code-Review < +1)
    - 23 days since last update

The report generator sorts the gerrit changes into three categories 
based on the state and the person or group required to perform the 
next action:


- Committers:
  Status [VECR xx]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & approved by a maintainer.
  Action: A committer should do a final review and submit the change 
or provide comment(s).


- Maintainers:
  Status [VECr]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & not reviewed

  Action: The Maintainer should do a code review

- Authors:
  Status : Gerrit Changes that are either not verified, 
expired, or comments not resolved
  Action: Author should rebase the change, fix verification errors, 
and/or resolve comments to move the status to [VECr]


Here is a gist of the report generated today: 
https://gist.github.com/dwallacelf/8f6e7c0ea7ae07cae1460cf49b631e6f


In the near future, I will add this to a github action to generate an 
updated report daily.


Please review the report and look for gerrit changes which require 
your attention.

All feedback welcome.

Thanks,
-daw-

[0] https://github.com/dwallacelf/gerrit-review




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21880): https://lists.fd.io/g/vpp-dev/message/21880
Mute This Topic: https://lists.fd.io/mt/93686025/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] One proposal for community meeting

[Dave Wallace]

Hi Xu,

Presenting your patch is a fine idea.
I will also spend a few minutes discussing the upgrade of the CI infra 
from ubuntu-20.04 to ubuntu-22.04.


You have the correct link to join the meeting.

Thanks,
-daw-

On 9/5/22 11:18 PM, Xu, Ting wrote:


Hi,

As I see in Dave’s message, our Community Meeting will be held next 
Tuesday (9.13).


I am wondering if I can have some time to present my patch – 
packetforge (5 minutes). It’s been a long time since it was last 
reviewed, and I think perhaps it is not clear to understand.


The patch link is: https://gerrit.fd.io/r/c/vpp/+/36149

BTW, should I follow the step here https://wiki.fd.io/view/VPP/Meeting 
to join the meeting?


Thanks!

Best Regards,

Xu Ting





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21853): https://lists.fd.io/g/vpp-dev/message/21853
Mute This Topic: https://lists.fd.io/mt/93494249/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Fix for vpp-csit-verify-device-master-ubuntu2204-x86_64-1n-skx job failures

[Dave Wallace]

Folks,

We're in the process of upgrading our CI infrastructure to use 
Ubuntu-22.04 LTS.  An issue was discovered that causes the vpp-device 
jobs (vpp-csit-verify-device-master-ubuntu2204-x86_64-1n-*) to fail due 
to memory exhaustion.


Damjan helped identify the root cause & correct fix [1], but gerrit 
changes which do not include this patch may still encounter the job failure:


    Java Connection Closed Exception
    Caused when the TCP connection is closed between Jenkins and the 
build executor.


I've been seeing gerrit changes which do not include this fix fail 
vpp-device tests and will be rebasing them.  If you encounter this error 
signature please rebase your gerrit change on the top of master.


Thanks,
-daw-

[0] 
https://jenkins.fd.io/job/vpp-csit-verify-device-master-ubuntu2204-x86_64-1n-skx/58/

[1] https://gerrit.fd.io/r/c/vpp/+/37036

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21846): https://lists.fd.io/g/vpp-dev/message/21846
Mute This Topic: https://lists.fd.io/mt/93427378/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] 2022-09-01 FD.io VPP (master branch) Gerrit Change Report

[Dave Wallace]

Folks,

I have updated a gerrit change report generator authored by Ole Troan 
[0] to produce a report that categorizes the state of the Gerrit review 
queue.  Each gerrit change is labeled with the following status:


== ===
Status Complete    Needs To Be Addressed
== ===
V - verified   v - not verified
E - not expired    e - expired
C - no unresolved comments c - comments not resolved
R - reviewed/approved  r - review incomplete
# - days since update  # - days since update > 30
== ===

Example: [VECr 23]
    - Verified
    - Not Expired
    - No unresolved comments
    - Review incomplete (Code-Review < +1)
    - 23 days since last update

The report generator sorts the gerrit changes into three categories 
based on the state and the person or group required to perform the next 
action:


- Committers:
  Status [VECR xx]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & approved by a maintainer.
  Action: A committer should do a final review and submit the change or 
provide comment(s).


- Maintainers:
  Status [VECr]: Gerrit Changes that have been verified, are not 
expired, no unresolved comments, & not reviewed

  Action: The Maintainer should do a code review

- Authors:
  Status : Gerrit Changes that are either not verified, expired, 
or comments not resolved
  Action: Author should rebase the change, fix verification errors, 
and/or resolve comments to move the status to [VECr]


Here is a gist of the report generated today: 
https://gist.github.com/dwallacelf/8f6e7c0ea7ae07cae1460cf49b631e6f


In the near future, I will add this to a github action to generate an 
updated report daily.


Please review the report and look for gerrit changes which require your 
attention.

All feedback welcome.

Thanks,
-daw-

[0] https://github.com/dwallacelf/gerrit-review

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21843): https://lists.fd.io/g/vpp-dev/message/21843
Mute This Topic: https://lists.fd.io/mt/93404542/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] make install-dep fails

[Dave Wallace]

Hi Hemant,

I would recommend using a more recent Ubuntu LTS release as support for 
Ubuntu 18.04 was deprecated a many releases ago.


All of our CI/CD & CSIT infrastructure are migrating to Ubuntu 22.04 for 
the upcoming VPP 22.10 release.  I anticipate that support for Ubuntu 
20.04 will be deprecated around VPP 23.06 timeframe.


You can always look back in the git history of .../vpp/Makefile for when 
Ubuntu 18.04 was deprecated from the 'install-deps' target but there is 
no guarantee that it will still work.


Thanks,
-daw-

On 8/23/2022 11:35 AM, hemant via lists.fd.io wrote:

I am using Ubuntu 18.04. I cloned the vpp repo today. I see a failure to get
enchant-2 and libffi7. I installed libffi-dev and enchant but still see the
failure.

git clonehttps://gerrit.fd.io/r/vpp

$ sudo make install-deps
Hit:2http://us.archive.ubuntu.com/ubuntu  bionic InRelease
Hit:3http://us.archive.ubuntu.com/ubuntu  bionic-updates InRelease
Get:4http://us.archive.ubuntu.com/ubuntu  bionic-backports InRelease [74.6 kB]
Hit:1https://apt.llvm.org/bionic  llvm-toolchain-bionic-11 InRelease
Hit:5http://us.archive.ubuntu.com/ubuntu  bionic-security InRelease
Hit:6http://ppa.launchpad.net/x2go/stable/ubuntu  bionic InRelease
Fetched 74.6 kB in 1s (81.3 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package enchant-2
E: Unable to locate package libffi7
Makefile:319: recipe for target 'install-dep' failed
make: *** [install-dep] Error 100

Hemant






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21815): https://lists.fd.io/g/vpp-dev/message/21815
Mute This Topic: https://lists.fd.io/mt/93206813/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Aug 2022 VPP Community Meetings are cancelled

[Dave Wallace]

Folks,

Per agreement at the last VPP Community meeting, the August 2022 VPP 
Community meetings are cancelled due to the summer holiday season.


The next VPP Community meeting is scheduled for Tuesday September 13, 
2022 at 8am PDT.


Enjoy the rest of the summer!
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21735): https://lists.fd.io/g/vpp-dev/message/21735
Mute This Topic: https://lists.fd.io/mt/92651804/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [csit-dev] FD.io CSIT-2206 Release Report is published

[Dave Wallace]

Congratulations to the CSIT Community and all FD.io community members 
who contributed to the VPP 22.06 release and CSIT 22.06 Report!


Well done!
-daw-

On 7/13/22 11:20 AM, Andrew Yourtchenko wrote:

FYI - in case you are not on csit-dev mail list.

--a

Begin forwarded message:


*From:* "Tibor Frank via lists.fd.io" 
*Date:* 13 July 2022 at 16:46:07 CEST
*To:* csit-...@lists.fd.io
*Subject:* *[csit-dev] FD.io CSIT-2206 Release Report is published*
*Reply-To:* tifr...@cisco.com



Hi All,

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

https://s3-docs.fd.io/csit/rls2206/report/

Another successful release! Many thanks to all contributors in CSIT and

VPP communities for making it happen.

See below for CSIT-2206 release summary and pointers to specific

sections in the report.

Welcome all comments, best by email to csit-...@lists.fd.io.

Tibor

CSIT-2206 Release Summary

-

BENCHMARK TESTS

- Regressions with DPDK drivers: Change from DPDK v21.08 to DPDK v21.11

introduced regression across all tests using dpdk drivers (with 
dpdk_plugin


loaded). Compared to previous VPP release performance drop varies in the

range of -15% to -6%, depending on test. It is related to updated MTU 
checks


within DPDK code and associated VPP code changes.

- Number of CSIT 9000B frame tests failing: tests with higher 
encapsulation


overhead are failing due to exceeding default Ethernet Maximum Frame Size

value that has been reduced by MTU related VPP code changes.

- Intel Xeon Ice Lake: Performance test data for these platforms is now

provided by testbeds newly installed in FD.io CSIT labs.

- Arm Ampere Altra: Performance test data for these platforms is now 
provided


by testbeds newly installed in FD.io CSIT labs.

- Reduction of tests: Removed certain test variations executed 
iteratively for


the report (as well as in daily and weekly trending) due to physical 
testbeds


overload.

TEST FRAMEWORK

- CSIT test environment version has been updated to ver. 10.

- CSIT PAPI support: Due to issues with PAPI performance, and 
deprecation of


VAT, VPP CLI is used in CSIT for many VPP scale tests.

- General Code Housekeeping: Ongoing code optimizations and bug fixes.

Pointers to CSIT-2206 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 v22.06 vs. v22.02[6]

7. VPP performance all pkt sizes & NICs [7]

8. DPDK 22.03 apps release notes[8]

9. DPDK 64B throughput graphs[9]

10. DPDK latency under load[10]

11. DPDK comparisons 22.03 vs. 21.11[11]

12. TRex 2.97 release notes[12]

13. TRex loopback 64B throughput graphs [13]

14. TRex latency under load[14]

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

[1] 
https://s3-docs.fd.io/csit/rls2206/report/introduction/methodology.html


[2] 
https://s3-docs.fd.io/csit/rls2206/report/vpp_performance_tests/csit_release_notes.html


[3] 
https://s3-docs.fd.io/csit/rls2206/report/vpp_performance_tests/packet_throughput_graphs/index.html


[4] 
https://s3-docs.fd.io/csit/rls2206/report/vpp_performance_tests/throughput_speedup_multi_core/index.html


[5] 
https://s3-docs.fd.io/csit/rls2206/report/vpp_performance_tests/packet_latency/index.html


[6] 
https://s3-docs.fd.io/csit/rls2206/report/vpp_performance_tests/comparisons/current_vs_previous_release.html


[7] 
https://s3-docs.fd.io/csit/rls2206/report/detailed_test_results/vpp_performance_results/index.html


[8] 
https://s3-docs.fd.io/csit/rls2206/report/dpdk_performance_tests/csit_release_notes.html


[9] 
https://s3-docs.fd.io/csit/rls2206/report/dpdk_performance_tests/packet_throughput_graphs/index.html


[10] 
https://s3-docs.fd.io/csit/rls2206/report/dpdk_performance_tests/packet_latency/index.html


[11] 
https://s3-docs.fd.io/csit/rls2206/report/dpdk_performance_tests/comparisons/current_vs_previous_release.html


[12] 
https://s3-docs.fd.io/csit/rls2206/report/trex_performance_tests/csit_release_notes.html


[13] 
https://s3-docs.fd.io/csit/rls2206/report/trex_performance_tests/packet_throughput_graphs/index.html


[14] 
https://s3-docs.fd.io/csit/rls2206/report/trex_performance_tests/packet_latency/index.html










-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21653): https://lists.fd.io/g/vpp-dev/message/21653
Mute This Topic: https://lists.fd.io/mt/92359742/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Reg Failure in make pkg-rpm with stable/2206 branch

[Dave Wallace]

Hi Archana,

Unfortunately the RPM package builds have been unsupported for several 
years and CentOS CI jobs removed a few releases ago.


Thus you are essentially on your own unless someone else who have been 
building rpm packages locally has any pointers.


Thanks,
-daw-

On 7/1/22 6:32 AM, Archana Sampath wrote:


Hi Team,

I am compiling vpp on centos 7 machine . Gcc version is 9.3.1.
I am facing the below issue when I  issue "make pkg-rpm" .
Kindly advise what needs to be done.

+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/redhat/brp-compress
+ /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1
Bytecompiling .py files below 
/data/archana/vpp_code/vpp/build-root/rpmbuild/BUILDROOT/vpp-22.06-release.x86_64/usr/lib/python3.6 
using /usr/bin/python3.6
Compiling 
/data/archana/vpp_code/vpp/build-root/rpmbuild/BUILDROOT/vpp-22.06-release.x86_64/usr/share/vpp/vppapigen_c.py 
...

  File "/usr/share/vpp/vppapigen_c.py", line 1298
    output += f"      return sizeof(*a)"
                                       ^
SyntaxError: invalid syntax

error: Bad exit status from /var/tmp/rpm-tmp.8XvMf6 (%install)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.8XvMf6 (%install)
make[1]: *** [Makefile:54: RPM] Error 1
make[1]: Leaving directory '/data/archana/vpp_code/vpp/extras/rpm'
make: *** [Makefile:619: pkg-rpm] Error 2


Thanks & Regards,
Archana




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21639): https://lists.fd.io/g/vpp-dev/message/21639
Mute This Topic: https://lists.fd.io/mt/92105557/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP release 22.06 is complete !

[Dave Wallace]

Congratulations to the entire FD.io Community and all who contributed to 
yet another on time, quality VPP release!


Special thanks to Andrew for his work as Release Manager.

Thanks,
-daw-

On 6/29/22 12:13 PM, Andrew Yourtchenko wrote:

Hello all,

VPP 22.06 release is complete and the artifacts are available in 
packagecloud release repository at https://packagecloud.io/fdio/release


Thanks a lot to all of you for the hard work which made this release 
possible!


Thanks to Vanessa Valderrama for the help with publishing the release 
artifacts!


Cheers! And onwards to 22.10! :-)

--a /* your friendly 22.06 release manager */




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21597): https://lists.fd.io/g/vpp-dev/message/21597
Mute This Topic: https://lists.fd.io/mt/92068364/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Latest News on FD.io

[Dave Wallace]

Folks,

FD.io TSC member Ray Kinsella has been blogging recently on FD.io VPP.  
His blog posts are now included on the FD.io web site under 'The 
Latest'->'Latest News' [0].


I highly recommend that you check them out.

Many thanks to Ray for his contributions to the FD.io Community!
-daw-

[0] https://fd.io/latest/news/

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21579): https://lists.fd.io/g/vpp-dev/message/21579
Mute This Topic: https://lists.fd.io/mt/91946428/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] unable to install vpp plugin dpdk

[Dave Wallace]

Ubuntu 22.04 (Jammy Jellyfish) packages are scheduled to be produced in 
VPP 22.10 release.


Thanks,
-daw-

On 6/21/22 4:29 AM, Lokesh Chakka wrote:

$ cat /etc/apt/sources.list.d/fdio_release.list
# this file was generated by packagecloud.io  for
# the repository at https://packagecloud.io/fdio/release

deb [signed-by=/etc/apt/keyrings/fdio_release-archive-keyring.gpg] 
https://packagecloud.io/fdio/release/ubuntu/ focal main
deb-src [signed-by=/etc/apt/keyrings/fdio_release-archive-keyring.gpg] 
https://packagecloud.io/fdio/release/ubuntu/ focal main


tried jammy. not working. kept focal. able to install the vpp

Thanks & Regards
--
Lokesh Chakka.


On Tue, Jun 21, 2022 at 1:52 PM Benoit Ganne (bganne) via lists.fd.io 
  wrote:


Are you sure you're downloading the right packages for your distro?
Check the content of /etc/apt/sources.list.d/fdio_release.list and
/etc/os-release.

ben

> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of
Lokesh Chakka
> Sent: Tuesday, June 21, 2022 9:36
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] unable to install vpp plugin dpdk
>
> Hello,
>
> =
>
> $ sudo apt-get install vpp-plugin-dpdk
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  vpp-plugin-dpdk : Depends: libssl1.1 (>= 1.1.0) but it is not
installable
> E: Unable to correct problems, you have held broken packages.
>
> =
>
>
> libssl is already the latest one. I have already installed dpdk. Can
> someone please help me fixing the issue
>
>
>
> Thanks & Regards
> --
> Lokesh Chakka.








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21573): https://lists.fd.io/g/vpp-dev/message/21573
Mute This Topic: https://lists.fd.io/mt/91895180/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Configuring linux kernel bond interface in VPP

[Dave Wallace]

Folks,

Unfortunately when performing an internet search for VPP's 
documentation, the first link found is commonly a very old copy on 
Read-The-Docs and often times a cloned RTD project.  Equally sad is the 
fact that the early doc sets did not include release labels, so it is 
not easy to discover the documentation is dated.


Here is a link to the VPP 22.06 documentation which is the equivalent 
circa VPP 18.07 doc section that Pim references below: 
https://s3-docs.fd.io/vpp/22.06/configuration/config_getting_started.html#configuration-file-startup-conf


Thanks,
-daw-

On 6/18/22 1:36 PM, Pim van Pelt wrote:

Hoi,


On Fri, Jun 17, 2022 at 8:41 AM Chinmaya Aggarwal 
 wrote:


Hi,

We configure linux kernel physical interface on VPP using below
steps:-

1. Whitelisting the physical interface in /etc/vpp/startup.conf.
2. Bringing the kernel interface down.
3. Restarting vpp service.

Is there a similar way by which we can configure linux bond
interface in VPP? I don't see pci address for bond interface in linux.

No, you cannot create a bond in Linux and make use of that in VPP. 
Bonding is a kernel driver that makes use of physical network card 
(and their driver), so you will not see a PCI address for a bonded 
ethernet device in Linux.


However, you can do it the other way around -- create the bond in VPP 
and then expose it in Linux using the Linux Control Plane.

See an example of this in https://ipng.ch/s/articles/2021/08/25/vpp-4.html

There's another way of creating the bond in startup.conf -- search for 
the string eth_bond0 in the documentation here:

https://my-vpp-docs.readthedocs.io/en/latest/gettingstarted/users/configuring/startup.html


groet,
Pim
--
Pim van Pelt 
PBVP1-RIPE - http://www.ipng.nl/




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21572): https://lists.fd.io/g/vpp-dev/message/21572
Mute This Topic: https://lists.fd.io/mt/91816581/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] FD.io CI Outage

[Dave Wallace]

Folks,

Jenkins was restarted last night which resolved the outage.  RCA is 
still being investigated.


Thanks,
-daw-

On 6/20/22 4:36 PM, Dave Wallace via lists.fd.io wrote:

Folks,

Jenkins.fd.io was inadvertently put into maintenance mode on 
Saturday.  It was taken out of maintenance mode about 5 hours ago, but 
VPP & CSIT jobs are still stuck in the Jenkins Build Queue (currently 
18 jobs in the queue).


LF-IT tickets [0] have been opened and resolution of the issue is ongoing.

Thank you for your patience as today is a US Holiday and the regular 
LF-IT support team is short staffed.

-daw-

[0] 
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-24179

https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-24181




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21562): https://lists.fd.io/g/vpp-dev/message/21562
Mute This Topic: https://lists.fd.io/mt/91886472/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] FD.io CI Outage

[Dave Wallace]

Folks,

Jenkins.fd.io was inadvertently put into maintenance mode on Saturday.  
It was taken out of maintenance mode about 5 hours ago, but VPP & CSIT 
jobs are still stuck in the Jenkins Build Queue (currently 18 jobs in 
the queue).


LF-IT tickets [0] have been opened and resolution of the issue is ongoing.

Thank you for your patience as today is a US Holiday and the regular 
LF-IT support team is short staffed.

-daw-

[0] https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-24179
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-24181

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21557): https://lists.fd.io/g/vpp-dev/message/21557
Mute This Topic: https://lists.fd.io/mt/91886472/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Jenkins Job failures do to TCP connectivity issues

[Dave Wallace]

Folks,

I found and fixed the root cause of the CI job failures.

Two of the four Nomad Server nodes were in a disconnected state wrt the 
Nomad Server Election pool (i.e. they both thought that there was no 
leader in the server pool and failed to initiate a new election).  The 
other two Nomad Servers were blissfully ignorant of the state as they 
both agreed upon the existing leader and apparently the leader was able 
to verify that all Nomad Server nodes were alive.


This issue was resolved by doing the following on each of the bogged up 
Nomad nodes sequentially:


1. Stop Nomad (sudo systemctl stop nomad)
2. Wait for the node to be set as 'left' (i.e. offline) in the leader's
   Nomad Server pool status
3. Start Nomad (sudo systemctl start nomad)

After both of the errant nodes had Nomad restarted, a new Nomad server 
pool leader was elected and the CI returned to normal.
Unfortunately the current monitoring tools were insufficient to directly 
identify the disconnected state of the two bad nodes.  I will work with 
Peter Mikus who helps maintain the servers to put a monitor in place to 
detect this state send an alert to reduce the downtime should this 
happen again.


It is not yet clear what triggered the disconnected state in the two 
Nomad server nodes and/or whether one or both of them had been in that 
state for a long time.


After resolving the issue, I have issued a 'recheck' on all VPP gerrit 
changes which failed due to TCP timeouts.  So far I have not seen any 
new job failures due to TCP connection resets.


Thanks for your patience during this outage.
-daw-

On 6/1/22 2:22 PM, Dave Wallace via lists.fd.io wrote:

Folks,

The FD.io CI is currently experiencing an rash of CI job failures do 
to TCP connection failures between Jenkins and the docker executor 
images.  I am currently working with LF-IT and the lab hosting vendor 
to diagnose and fix the issues.


Thank you in advance for your patience while this issue is being resolved.
-daw-




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21494): https://lists.fd.io/g/vpp-dev/message/21494
Mute This Topic: https://lists.fd.io/mt/91483014/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Jenkins Job failures do to TCP connectivity issues

[Dave Wallace]

Folks,

The FD.io CI is currently experiencing an rash of CI job failures do to 
TCP connection failures between Jenkins and the docker executor images.  
I am currently working with LF-IT and the lab hosting vendor to diagnose 
and fix the issues.


Thank you in advance for your patience while this issue is being resolved.
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21490): https://lists.fd.io/g/vpp-dev/message/21490
Mute This Topic: https://lists.fd.io/mt/91483014/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] GoVPP Community Meetings (even weeks @ 6:30am Pacific Time)

[Dave Wallace]

Folks,

The GoVPP project is starting to hold GoVPP Community meetings every 
other week on even weeks @ 6:30am Pacific Time beginning this Thursday 
June 2, 2022.


A recent increase in downstream consumers has prompted holding regular 
meetings to address critical fixes / improve review/merge times, discuss 
downstream consumer requirements, proposed moving of the project from 
gerrit.fd.io to github, and improving automated CI test coverage.


Detailed meeting information and agenda can be found on the GoVPP wiki page:
https://wiki.fd.io/view/GoVPP/Meeting

Everyone interested in the GoVPP project is welcome to attend and 
encouraged to participate.


Thanks,
-daw-


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21488): https://lists.fd.io/g/vpp-dev/message/21488
Mute This Topic: https://lists.fd.io/mt/91467384/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Topics for tomorrow's VPP Community Meeting

[Dave Wallace]

Folks,

I have a couple topics to discuss at tomorrow's VPP Community meeting:

1. Feedback on https://gerrit.fd.io/r/c/vpp/+/36043 tests: replace 
pycodestyle with black


2. Presentation on Refactoring VPP Make Test Framework (20 minutes + 
discussion)


Thanks,
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21392): https://lists.fd.io/g/vpp-dev/message/21392
Mute This Topic: https://lists.fd.io/mt/91003928/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Issue with VPP build

[Dave Wallace]

Rajisha,

The scripts in that directory are woefully out of date.

Plesae see the vpp 18.10+ directions in 
https://wiki.fd.io/view/VPP/Pulling,_Building,_Running,_Hacking_and_Pushing_VPP_Code#Building_without_virtualization


Thanks,
-daw-


On 5/5/22 4:12 AM, Rajisha Payyanur wrote:


Hi Team,

We are trying to build VPP on ubuntu 20.04 with kernel version:5.4.x.

We cloned the gerrit code:https://gerrit.fd.io/r/vpp

When we try to build with : /build-root/vagrant/build.sh, we see below 
issues:


ubuntu@vpp:~/vpp/build-root$ cat 
/home/ubuntu/vpp/build-root/build-vpp-native/vpp/CMakeFiles/CMakeError.log


Performing C SOURCE FILE Test compiler_flag_no_stringop_overflow 
failed with the following output:


Change Dir: 
/home/ubuntu/vpp/build-root/build-vpp-native/vpp/CMakeFiles/CMakeTmp


Run Build Command(s):/usr/bin/ninja cmTC_155e3 && [1/2] Building C 
object CMakeFiles/cmTC_155e3.dir/src.c.o


warning: unknown warning option '-Wno-stringop-overflow'; did you mean 
'-Wno-shift-overflow'? [-Wunknown-warning-option]


1 warning generated.

[2/2] Linking C executable cmTC_155e3

Source file was:

int main(void) { return 0; }

Performing C SOURCE FILE Test CMAKE_HAVE_LIBC_PTHREAD failed with the 
following output:


Change Dir: 
/home/ubuntu/vpp/build-root/build-vpp-native/vpp/CMakeFiles/CMakeTmp


*Run Build Command(s):/usr/bin/ninja cmTC_ff9c6 && [1/2] Building C 
object CMakeFiles/cmTC_ff9c6.dir/src.c.o*


*[2/2] Linking C executable cmTC_ff9c6*

*FAILED: cmTC_ff9c6 *

*: && /usr/lib/ccache/clang --target=x86_64-linux-gnu 
CMakeFiles/cmTC_ff9c6.dir/src.c.o -o cmTC_ff9c6 && :*


*/usr/bin/x86_64-linux-gnu-ld: CMakeFiles/cmTC_ff9c6.dir/src.c.o: in 
function `main':*


*src.c:(.text+0x25): undefined reference to `pthread_create'*

*/usr/bin/x86_64-linux-gnu-ld: src.c:(.text+0x31): undefined reference 
to `pthread_detach'*


*/usr/bin/x86_64-linux-gnu-ld: src.c:(.text+0x3d): undefined reference 
to `pthread_cancel'*


*/usr/bin/x86_64-linux-gnu-ld: src.c:(.text+0x4f): undefined reference 
to `pthread_join'*


*clang: error: linker command failed with exit code 1 (use -v to see 
invocation)*


*ninja: build stopped: subcommand failed.*

Source file was:

#include 

static void* test_func(void* data)

{

  return data;

}

int main(void)

{

  pthread_t thread;

pthread_create(&thread, NULL, test_func, NULL);

pthread_detach(thread);

pthread_cancel(thread);

pthread_join(thread, NULL);

pthread_atfork(NULL, NULL, NULL);

pthread_exit(NULL);

  return 0;

}

Checking whether the ASM compiler is GNU using "--version" did not 
match "(GNU assembler)|(GCC)|(Free Software Foundation)":


clang version 10.0.0-4ubuntu1

Target: x86_64-pc-linux-gnu

Thread model: posix

InstalledDir: /usr/bin

Determining if the function SSL_set_async_callback exists failed with 
the following output:


Change Dir: 
/home/ubuntu/vpp/build-root/build-vpp-native/vpp/CMakeFiles/CMakeTmp


*Run Build Command(s):/usr/bin/ninja cmTC_ed864 && [1/2] Building C 
object CMakeFiles/cmTC_ed864.dir/CheckFunctionExists.c.o*


*[2/2] Linking C executable cmTC_ed864*

*FAILED: cmTC_ed864 *

*: && /usr/lib/ccache/clang --target=x86_64-linux-gnu 
-DCHECK_FUNCTION_EXISTS=SSL_set_async_callback 
CMakeFiles/cmTC_ed864.dir/CheckFunctionExists.c.o -o cmTC_ed864  
/usr/lib/x86_64-linux-gnu/libssl.so 
/usr/lib/x86_64-linux-gnu/libcrypto.so && :*


*/usr/bin/x86_64-linux-gnu-ld: 
CMakeFiles/cmTC_ed864.dir/CheckFunctionExists.c.o: in function `main':*


*CheckFunctionExists.c:(.text+0x17): undefined reference to 
`SSL_set_async_callback'*


clang: error: linker command failed with exit code 1 (use -v to see 
invocation)


ninja: build stopped: subcommand failed.

We have seen posts on similar issue(vpp-dev@lists.fd.io | Arm build 
failures on Qualcomm, ThunderX2, Mellanox Bluefield 
),but 
couldn’t find a proper answer.


We tried with a stable version also, but seeing same issue.

Is there any prerequisites to build VPP on ubuntu 20.

Can anyone please share your points on this.

Regards,

Rajisha

*L&T Technology Services Ltd*

www.LTTS.com

L&T Technology Services Limited (LTTS) is committed to safeguard your 
data privacy. For more information to view our commitment towards data 
privacy under GDPR, please visit the privacy policy on our website 
www.Ltts.com. This Email may contain confidential or privileged 
information for the intended recipient (s). If you are not the 
intended recipient, please do not use or disseminate the information, 
notify the sender and delete it from your system.






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21376): https://lists.fd.io/g/vpp-dev/message/21376
Mute This Topic: https://lists.fd.io/mt/90906807/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Replacing pycodestyle with black

[Dave Wallace]

+1

On 5/3/2022 3:10 AM, Benoit Ganne (bganne) via lists.fd.io wrote:

I am all for a consistent formatter for make test, the current situation is 
painfull .
Regarding defaults, I think just using the defaults from the tools is fine as 
long it is not completely crazy.
I'll just use make fixstyle before pushing anyway.

ben


-Original Message-
From:vpp-dev@lists.fd.ioOn Behalf Of Klement
Sekera
Sent: Tuesday, May 3, 2022 8:58
To: vpp-dev
Subject: Re: [vpp-dev] Replacing pycodestyle with black

Also an item to ponder - line length. PEP8 says line length should be <=
79 IIRC.

Black advocates line length of 88, saying it produces least lines of code
by experience and it’s the default.

https://black.readthedocs.io/en/stable/the_black_code_style/current_style.
html#line-length




On 2 May 2022, at 23:31, Dave Wallace mailto:dwallac...@gmail.com>  > wrote:

I'll work on expanding Klement's patch to include all python files
in the repo.

I'm thinking it makes more sense to have a single target 'make
checkstyle-python' (and corresponding 'fixstyle-python') that runs black
against all of the '*.py' files in the repo and deprecate the 'test-
checkstyle' target.  Any objections?

Thanks,
-daw-


On 5/2/22 4:08 PM, Ole Troan wrote:


I’d be happy to have formatting consistency across the
project.

Cheers
Ole


On 2 May 2022, at 19:17, Klement Sekera
  <mailto:klem...@graphiant.com>   wrote:



 +Real Ole.



On 2 May 2022, at 19:15, Klement Sekera via
lists.fd.io<http://lists.fd.io/>   mailto:klement=graphiant@lists.fd.io>  > wrote:

Hi Dave,

good catch about requirements.txt. Should be
fixed now.

I’m not sure how to proceed with rest of code,
seems to be mostly Ole’s domain. Thoughts, Ole?

Thanks,
    Klement



On 2 May 2022, at 18:50, Dave Wallace
mailto:dwallac...@gmail.com>  > wrote:

Hi Klement,

I agree that black is a much better PEP8
compliance/formatter for python code.  I've been using it on my personal
python projects for a while now.

I left a minor comment on your gerrit
change wrt. installation of pinned version as part of the rest of the
python virtualenv.  Otherwise it looks good to me.

What about the rest of the python code 
in
the repo?

Thanks,
-daw-


On 5/2/22 6:56 AM, Klement Sekera wrote:


Hey vpp-dev,

looking at our current code style and 
its
PEP8 compliance I see a couple of issues

1.) it’s not really PEP8 compliant
2.) we have no test-fixstyle

I decided to make it more PEP8 compliant
and found out that to just fix W503 to W504 (per
https://peps.python.org/pep-0008/#should-a-line-break-before-or-after-a-
binary-operator), we would need to do a lot of manual code style changes.
Looking at a tool to do that I stumbled upon black
(https://github.com/psf/black) which aims to be a consistent  code style
fixer/validator producing minimum diffs. It’s already used by many small
and large projects and similarly small and large organisations. It’s also
much faster to validate/format than pycodestyle/autopep8 - its runtime on
all our files is in seconds.

My proposal is to bite the bullet and
accept a change in style in exchange for a consistent, auto-formatted,
(almost entirely) pep8 compliant style.

Here’s the diff:

https://gerrit.fd.io/r/c/vpp/+/36043

Thoughts?

Thanks,
Klement




















-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21346): https://lists.fd.io/g/vpp-dev/message/21346
Mute This Topic: https://lists.fd.io/mt/90832348/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Replacing pycodestyle with black

[Dave Wallace]

I'll work on expanding Klement's patch to include all python files in 
the repo.


I'm thinking it makes more sense to have a single target 'make 
checkstyle-python' (and corresponding 'fixstyle-python') that runs black 
against all of the '*.py' files in the repo and deprecate the 
'test-checkstyle' target.  Any objections?


Thanks,
-daw-

On 5/2/22 4:08 PM, Ole Troan wrote:

I’d be happy to have formatting consistency across the project.

Cheers
Ole


On 2 May 2022, at 19:17, Klement Sekera  wrote:

 +Real Ole.

On 2 May 2022, at 19:15, Klement Sekera via lists.fd.io 
<http://lists.fd.io>  wrote:


Hi Dave,

good catch about requirements.txt. Should be fixed now.

I’m not sure how to proceed with rest of code, seems to be mostly 
Ole’s domain. Thoughts, Ole?


Thanks,
Klement


On 2 May 2022, at 18:50, Dave Wallace  wrote:

Hi Klement,

I agree that black is a much better PEP8 compliance/formatter for 
python code.  I've been using it on my personal python projects for 
a while now.


I left a minor comment on your gerrit change wrt. installation of 
pinned version as part of the rest of the python virtualenv. 
Otherwise it looks good to me.


What about the rest of the python code in the repo?

Thanks,
-daw-

On 5/2/22 6:56 AM, Klement Sekera wrote:

Hey vpp-dev,

looking at our current code style and its PEP8 compliance I see a 
couple of issues


1.) it’s not really PEP8 compliant
2.) we have no test-fixstyle

I decided to make it more PEP8 compliant and found out that to 
just fix W503 to W504 (per 
https://peps.python.org/pep-0008/#should-a-line-break-before-or-after-a-binary-operator), 
we would need to do a lot of manual code style changes. Looking at 
a tool to do that I stumbled upon black 
(https://github.com/psf/black) which aims to be a consistentcode 
style fixer/validator producing minimum diffs. It’s already used 
by many small and large projects and similarly small and large 
organisations. It’s also much faster to validate/format than 
pycodestyle/autopep8 - its runtime on all our files is in seconds.


My proposal is to bite the bullet and accept a change in style in 
exchange for a consistent, auto-formatted, (almost entirely) pep8 
compliant style.


Here’s the diff:

https://gerrit.fd.io/r/c/vpp/+/36043

Thoughts?

Thanks,
Klement












-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21329): https://lists.fd.io/g/vpp-dev/message/21329
Mute This Topic: https://lists.fd.io/mt/90832348/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Replacing pycodestyle with black

[Dave Wallace]

Hi Klement,

I agree that black is a much better PEP8 compliance/formatter for python 
code.  I've been using it on my personal python projects for a while now.


I left a minor comment on your gerrit change wrt. installation of pinned 
version as part of the rest of the python virtualenv. Otherwise it looks 
good to me.


What about the rest of the python code in the repo?

Thanks,
-daw-

On 5/2/22 6:56 AM, Klement Sekera wrote:

Hey vpp-dev,

looking at our current code style and its PEP8 compliance I see a 
couple of issues


1.) it’s not really PEP8 compliant
2.) we have no test-fixstyle

I decided to make it more PEP8 compliant and found out that to just 
fix W503 to W504 (per 
https://peps.python.org/pep-0008/#should-a-line-break-before-or-after-a-binary-operator), 
we would need to do a lot of manual code style changes. Looking at a 
tool to do that I stumbled upon black (https://github.com/psf/black) 
which aims to be a consistent code style fixer/validator producing 
minimum diffs. It’s already used by many small and large projects and 
similarly small and large organisations. It’s also much faster to 
validate/format than pycodestyle/autopep8 - its runtime on all our 
files is in seconds.


My proposal is to bite the bullet and accept a change in style in 
exchange for a consistent, auto-formatted, (almost entirely) pep8 
compliant style.


Here’s the diff:

https://gerrit.fd.io/r/c/vpp/+/36043

Thoughts?

Thanks,
Klement




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21321): https://lists.fd.io/g/vpp-dev/message/21321
Mute This Topic: https://lists.fd.io/mt/90832348/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Query on VPP in Aure

[Dave Wallace]

Thanks Matt!

-daw-

On 4/29/2022 2:40 PM, Matthew Smith via lists.fd.io wrote:

Hi Ben,

Sure, I'll work on an update to the doc.

-Matt


On Fri, Apr 29, 2022 at 3:48 AM Benoit Ganne (bganne) 
 wrote:


Hi Matt, John,

This is a great summary!

>> The only reference I could find for VPP in Azure was in this link
>> but it is very outdated:
>> https://fd.io/docs/vpp/v2101/usecases/vppinazure.html

> Yes, that doc is way outdated. I advise against following the
instructions
> in it.

Matt or John, would you mind proposing a patch for that? Even a
quick & dirty "here are the steps you need to follow" would be great.

Best
ben





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21304): https://lists.fd.io/g/vpp-dev/message/21304
Mute This Topic: https://lists.fd.io/mt/90759128/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Feedback on a tool: vppcfg

[Dave Wallace]

Hi Pim,

This is most excellent!  Thank you for sharing your work.

I also have only taken a quick pass through the information you posted, 
but have been thinking about tackling a YAML or JSON based configuration 
format to help simplify the unit testing environment and make use case 
test automation more accessible.


From a FD.io community perspective, your work could readily be set up 
as a sub-project which would be extremely beneficial were it to be 
adopted as a tool to be utilized in the test pipeline in addition to 
other downstream VPP consumers.


I will give a test drive this week and provide some feedback to you. I'm 
very interested in helping out with this effort.


In case you are not aware, Ole introduced JSON formatted API output and 
vat2 which translates JSON api files into VPP api calls.  I have used 
this feature to capture 'make test' testcase configurations and replay 
them to VPP using vat2.  This experiment is part of the 'make test' 
framework refactoring that I am engaged in to separate Scapy packet 
stream processing (pcap input file generation and pcap output file 
verification) from the 'make test' python framework.  I haven't looked 
at your implementation closely at this point, so you may in fact already 
be using this.  If so, please excuse my ignorance. :)


There is also a gap in VPP control plane interfaces between the Debug 
CLI and VPP-API. As you mention in your write-up, the debug CLI is NOT 
intended to be used as the primary control plane interface.


The original control plane design patter by Dave Barach was to split 
feature configuration into parallel CLI/API parsing/message validation 
stages, each of which would call the same feature config function. This 
allowed Dave to rapidly prototype the configuration interface using the 
debug CLI and subsequently add the VPP-API with minimal effort.


Unfortunately this architecture has not been utilized universally as VPP 
features have been added. This has led to inconsistency between debug 
CLI commands and the VPP-API.  While it is understandable that there are 
debug configuration attributes that are not appropriate for the 
production API, I think that it would be great to make a pass through 
the feature set to align them more closely and to promote the sharing of 
common configuration code in VPP features between the Debug CLI and VPP-API.


In any case, enough of my ranting -- thanks again for your contributions 
to VPP & the FD.io community!

-daw-


On 4/2/2022 2:21 PM, Florin Coras wrote:

Hi Pim,

Definitely cool! Haven’t had a chance to go through all of it but the 
fact that some binary api calls crash vpp is something we should fix.


It feels like vppcfg could also be used for extensive vpp api/cli/cfg 
testing.


My quick 0.02$

Regards,
Florin


On Apr 2, 2022, at 8:17 AM, Pim van Pelt  wrote:

Hoi colleagues,

I know there exist several smaller and larger scale VPP configuration 
harnesses out there, some more complex and feature complete than 
others. I wanted to share my work on an approach based on a YAML 
configuration with strict syntax and semantic validation, and a path 
planner that brings the dataplane from any configuration state safely 
to any other configuration state, as defined by these YAML files.


A bit of a storyline on the validator: 
https://ipng.ch/s/articles/2022/03/27/vppcfg-1.html
A bit of background on the DAG path planner: 
https://ipng.ch/s/articles/2022/04/02/vppcfg-2.html

Code with tests on https://github.com/pimvanpelt/vppcfg

The config and planner supports interfaces, bondethernets, vxlan 
tunnels, l2xc, bridgedomains and, quelle surprise, linux-cp 
configurations of all sorts. If anybody feels like giving it a spin, 
I'd certainly appreciate feedback and if you can manage to create two 
configuration states that the planner cannot reconcile, I'd love to 
hear about those too.


For now, the path planner works by reading the API configuration 
state exactly once (at startup), and then it figures out the CLI 
calls to print without needing to consult VPP again. This is super 
useful as it’s a non-intrusive way to inspect the changes before 
applying them, and it’s a property I’d like to carry forward. 
However, I don’t necessarily think that emitting the CLI statements 
is the best user experience, it’s more for the purposes of analysis 
that they can be useful. What I really want to do is emit API calls 
after the plan is created and reviewed/approved, directly 
reprogramming the VPP dataplane. However, the VPP API set needed to 
do this is not 100% baked yet. For example, I observed crashes when 
tinkering with BVIs and Loopbacks (see my thread from last week, 
thanks for the response Neale), and fixed a few obvious errors in the 
Linux CP API (gerrit) but there are still a few more issues to work 
through before I can set the next step with vppcfg.


If this tool proves to be useful to others, I'm happy to upstream it 
to extras/ somewhere.


--
Pim van Pelt 
PB

Re: [vpp-dev] In regards of the memif library from the vpp Git repository

[Dave Wallace]

Funny you should mention 30573 -- yesterday I noticed this was in limbo 
& broken.  I am in the process of fixing the bugs in this documentation 
so that it can be merged.


While I'm at it, I will be be updating the CI verify job to upload the 
doc verify results to an AWS S3 bucket with a 7 day retention policy to 
enhance the documentation review process.


Thanks,
-daw-

On 3/22/22 5:21 AM, Benoit Ganne (bganne) via lists.fd.io wrote:

Hi Catalin,

CC'ed vpp-dev, but examples and doc can be found 
herehttps://gerrit.fd.io/r/c/vpp/+/30573
It would be good to have this patch merged I guess but it looks like there are 
some issues to fix in the doc.

Best
Ben


From: Catalin Iordache
Date: Mar 20, 2022 15:36
Subject: In regards of the memif library from the vpp Git repository
To:benoit.ga...@gmail.com
Cc:



Hello,

I noticed that the latest version of the memif library is lacking
documentation and the things that are in there seem a bit outdated.

I am mostly interested in the multi threaded support in memif,
which in older versions seemed to be offered by the library but now
they’ve been removed.

Do you have some documentation and code examples on how memif
should be handled by multiple threads concurrently?

Best regards,
Catalin






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21094): https://lists.fd.io/g/vpp-dev/message/21094
Mute This Topic: https://lists.fd.io/mt/89948379/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [csit-dev] FD.io CSIT-2202 Release Report is published

[Dave Wallace]

Most Excellent!

Congratulations to all members of the FD.io community that contributed 
to the VPP 22.02 Release and CSIT 22.02 Release Report.


Thanks,
-daw-

On 3/9/22 10:30, Tibor Frank via lists.fd.io wrote:


Hi All,

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

https://s3-docs.fd.io/csit/rls2202/report/

Another successful release! Many thanks to all contributors in CSIT and

VPP communities for making it happen.

See below for CSIT-2202 release summary and pointers to specific

sections in the report.

Welcome all comments, best by email to csit-...@lists.fd.io.

Tibor

CSIT-2202 Release Summary

-

BENCHMARK TESTS

- Regressions with DPDK drivers: Change from DPDK v21.08 to DPDK v21.11

introduced regression across all tests using dpdk drivers (with 
dpdk_plugin


loaded). Compared to previous VPP release performance drop varies in the

range of -15% to -6%, depending on test. It is related to updated MTU 
checks


within DPDK code and associated VPP code changes.

- Number of CSIT 9000B frame tests failing: tests with higher 
encapsulation


overhead are failing due to exceeding default Ethernet Maximum Frame Size

value that has been reduced by MTU related VPP code changes.

- Intel Xeon Ice Lake: Performance test data for these platforms is now

provided by testbeds newly installed in FD.io CSIT labs.

- Reduction of tests: Removed certain test variations executed 
iteratively for


the report (as well as in daily and weekly trending) due to physical 
testbeds


overload.

TEST FRAMEWORK

- CSIT test environment version has been updated to ver. 9.

- CSIT PAPI support: Due to issues with PAPI performance, and 
deprecation of


VAT, VPP CLI is used in CSIT for many VPP scale tests.

- General Code Housekeeping: Ongoing code optimizations and bug fixes.

Pointers to CSIT-2202 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 v22.02 vs. v21.10[6]

7. VPP performance all pkt sizes & NICs [7]

8. DPDK 21.11 apps release notes[8]

9. DPDK 64B throughput graphs[9]

10. DPDK latency under load[10]

11. DPDK comparisons 21.11 vs. 21.08[11]

12. TRex 2.88 release notes[12]

13. TRex loopback 64B throughput graphs [13]

14. TRex latency under load[14]

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

[1] 
https://s3-docs.fd.io/csit/rls2202/report/introduction/methodology.html


[2] 
https://s3-docs.fd.io/csit/rls2202/report/vpp_performance_tests/csit_release_notes.html


[3] 
https://s3-docs.fd.io/csit/rls2202/report/vpp_performance_tests/packet_throughput_graphs/index.html


[4] 
https://s3-docs.fd.io/csit/rls2202/report/vpp_performance_tests/throughput_speedup_multi_core/index.html


[5] 
https://s3-docs.fd.io/csit/rls2202/report/vpp_performance_tests/packet_latency/index.html


[6] 
https://s3-docs.fd.io/csit/rls2202/report/vpp_performance_tests/comparisons/current_vs_previous_release.html


[7] 
https://s3-docs.fd.io/csit/rls2202/report/detailed_test_results/vpp_performance_results/index.html


[8] 
https://s3-docs.fd.io/csit/rls2202/report/dpdk_performance_tests/csit_release_notes.html


[9] 
https://s3-docs.fd.io/csit/rls2202/report/dpdk_performance_tests/packet_throughput_graphs/index.html


[10] 
https://s3-docs.fd.io/csit/rls2202/report/dpdk_performance_tests/packet_latency/index.html


[11] 
https://s3-docs.fd.io/csit/rls2202/report/dpdk_performance_tests/comparisons/current_vs_previous_release.html


[12] 
https://s3-docs.fd.io/csit/rls2202/report/trex_performance_tests/csit_release_notes.html


[13] 
https://s3-docs.fd.io/csit/rls2202/report/trex_performance_tests/packet_throughput_graphs/index.html


[14] 
https://s3-docs.fd.io/csit/rls2202/report/trex_performance_tests/packet_latency/index.html






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20994): https://lists.fd.io/g/vpp-dev/message/20994
Mute This Topic: https://lists.fd.io/mt/89667940/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] vpp-dev@lists.fd.io is operational once more.

[Dave Wallace]

Folks,

The vpp-dev@lists.fd.io mailing list is working again.  This issue was 
inadvertently caused when the web interface was being updated to 
restrict it to view only.


There have been a few issues of very old threads being replied to via 
the web interface which was causing some communication challenges and it 
was deemed to be best to disallow replying to email threads via the web 
interface.


Thank you for your patience during this outage.
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20949): https://lists.fd.io/g/vpp-dev/message/20949
Mute This Topic: https://lists.fd.io/mt/89554874/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] vpp-dev mailing list is inoperative

[Dave Wallace]

Testing vpp-dev@lists.fd.io

Thanks,
-daw-

 Forwarded Message 
Subject:vpp-dev mailing list is inoperative
Date:   Fri, 4 Mar 2022 08:47:03 -0500
From:   Dave Wallace 
To: 	csit-...@lists.fd.io , t...@lists.fd.io 





FYI,

The vpp-dev@lists.fd.io is currently inoperative.  Benoit opened an 
LF-IT ticket [0] to have this resolved.


Thanks,
-daw-

[0] https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23697

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20948): https://lists.fd.io/g/vpp-dev/message/20948
Mute This Topic: https://lists.fd.io/mt/89554616/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] gerrit.fd.io not responding

[Dave Wallace]

Thanks Pim.  I agree about Jira :)

Have a great weekend!
-daw-

On 2/25/22 7:42 PM, Pim van Pelt wrote:

Hoi,

Confirmed gerrit is up on its website. And to answer your question -- 
Yes, I'm logged in to the linuxfoundation SSO (and currently see 
gerrit in read/write view). Don't worry about it, Dave. I would've 
fired Jira too :)


groet,
Pim

On Sat, Feb 26, 2022 at 1:28 AM Dave Wallace  wrote:

Pim thanks for the status report.  It now appears to be back in
service.

FYI, gerrit.fd.io <http://gerrit.fd.io> is hosted in amazon AWS,
so it may have been a glitch routing to us-east-1.

As for access to LF-IT help desk, I'm not sure what the
restrictions are wrt. viewing tickets.  We you able to login?

Thanks,
-daw-

On 2/25/22 7:11 PM, Pim van Pelt wrote:

Hoi,

Thanks Dave. From me in Zurich, SSH (and git) are up, but perhaps
it's only the website that is down?
By the way, in case others see this too, I do not have permission
to view that ticket in Jira.

groet,
Pim

On Sat, Feb 26, 2022 at 1:06 AM Dave Wallace
 wrote:

Folks,

I have opened a ticket [0] with LF-IT due to gerrit.fd.io
<http://gerrit.fd.io> not responding.

Will provide an update when the issue is resolved or more
information is available.

Thanks,
-daw-
[0]
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23671






-- 
Pim van Pelt 

PBVP1-RIPE - http://www.ipng.nl/




--
Pim van Pelt 
PBVP1-RIPE - http://www.ipng.nl/

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20926): https://lists.fd.io/g/vpp-dev/message/20926
Mute This Topic: https://lists.fd.io/mt/89401616/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Resolved: [vpp-dev] gerrit.fd.io not responding

[Dave Wallace]

gerrit.fd.io is now responding again (without any known intervention).  
I have closed the ticket.


Thanks,
-daw-

On 2/25/22 7:06 PM, Dave Wallace via lists.fd.io wrote:

Folks,

I have opened a ticket [0] with LF-IT due to gerrit.fd.io not responding.

Will provide an update when the issue is resolved or more information 
is available.


Thanks,
-daw-
[0] 
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23671





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20924): https://lists.fd.io/g/vpp-dev/message/20924
Mute This Topic: https://lists.fd.io/mt/89401986/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] gerrit.fd.io not responding

[Dave Wallace]

Pim thanks for the status report.  It now appears to be back in service.

FYI, gerrit.fd.io is hosted in amazon AWS, so it may have been a glitch 
routing to us-east-1.


As for access to LF-IT help desk, I'm not sure what the restrictions are 
wrt. viewing tickets.  We you able to login?


Thanks,
-daw-

On 2/25/22 7:11 PM, Pim van Pelt wrote:

Hoi,

Thanks Dave. From me in Zurich, SSH (and git) are up, but perhaps it's 
only the website that is down?
By the way, in case others see this too, I do not have permission to 
view that ticket in Jira.


groet,
Pim

On Sat, Feb 26, 2022 at 1:06 AM Dave Wallace  wrote:

Folks,

I have opened a ticket [0] with LF-IT due to gerrit.fd.io
<http://gerrit.fd.io> not responding.

Will provide an update when the issue is resolved or more
information is available.

Thanks,
-daw-
[0]
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23671






--
Pim van Pelt 
PBVP1-RIPE - http://www.ipng.nl/

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20923): https://lists.fd.io/g/vpp-dev/message/20923
Mute This Topic: https://lists.fd.io/mt/89401616/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] gerrit.fd.io not responding

[Dave Wallace]

Folks,

I have opened a ticket [0] with LF-IT due to gerrit.fd.io not responding.

Will provide an update when the issue is resolved or more information is 
available.


Thanks,
-daw-
[0] https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23671

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20921): https://lists.fd.io/g/vpp-dev/message/20921
Mute This Topic: https://lists.fd.io/mt/89401616/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP release 22.02 release is complete!

[Dave Wallace]

Most excellent!

Thank you to all of the FD.io community who contributed/supported the 
successful, on-time release of VPP 22.02.


Special thanks to Andrew for his work as VPP 22.02 Release Manager!

-daw-

On 2/23/22 12:17 PM, Andrew Yourtchenko wrote:

Hi all,

the artifacts for the VPP 22.02 release are available at the usual 
place, https://packagecloud.io/fdio/release 
<https://packagecloud.io/fdio/release>


Many thanks to Vanessa Valderrama, Maciek Konstantynowicz, Dave 
Wallace, Fan Zhang for the help with this release!


--a // your friendly 22.02 release manager






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20896): https://lists.fd.io/g/vpp-dev/message/20896
Mute This Topic: https://lists.fd.io/mt/89345752/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev]: Unable to run make test

[Dave Wallace]

Rajith,

What OS are you building on and what VPP branch are you trying to build?

Ubuntu-20.04/master:HEAD works for me.

Thanks,
-daw-

On 2/4/22 10:29 AM, Rajith PR via lists.fd.io wrote:

Hi Ole/Klement,

I changed the command to make test-debug TEST=ip4. But still the same 
issue. Under install-vpp_debug-native/vpp/bin *vpp* is not getting 
built for some reason. I can see all the shared libs getting built though.


supervisor@rajith_upstream>srv3.nbg1.rtbrick.net:~/libvpp $ make 
test-debug TEST=ip4 V=1
make -C /home/supervisor/libvpp/build-root PLATFORM=vpp TAG=vpp_debug 
vpp-install

make[1]: Entering directory '/home/supervisor/libvpp/build-root'
 Arch for platform 'vpp' is native 
 Finding source for external 
 Makefile fragment found in 
/home/supervisor/libvpp/build-data/packages/external.mk 
 

 Source found in /home/supervisor/libvpp/build 
 Arch for platform 'vpp' is native 
 Finding source for vpp 
 Makefile fragment found in 
/home/supervisor/libvpp/build-data/packages/vpp.mk  

 Source found in /home/supervisor/libvpp/src 
find: ‘/home/supervisor/libvpp/build-root/config.site’: No such file 
or directory

 Configuring external: nothing to do 
 Building external: nothing to do 
 Installing external: nothing to do 
find: ‘/home/supervisor/libvpp/build-root/config.site’: No such file 
or directory

 Configuring vpp: nothing to do 
 Building vpp in 
/home/supervisor/libvpp/build-root/build-vpp_debug-native/vpp 

ninja: no work to do.
 Installing vpp: nothing to do 
make[1]: Leaving directory '/home/supervisor/libvpp/build-root'
make -C test 
VPP_BUILD_DIR=/home/supervisor/libvpp/build-root/build-vpp_debug-native 
VPP_BIN=/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/bin/vpp 
VPP_PLUGIN_PATH=/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins:/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/lib64/vpp_plugins 
VPP_TEST_PLUGIN_PATH=/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/lib/vpp_api_test_plugins:/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/lib64/vpp_api_test_plugins 
VPP_INSTALL_PATH=/home/supervisor/libvpp/build-root/install-vpp_debug-native/ 
LD_LIBRARY_PATH=/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/lib/:/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/lib64/ 
EXTENDED_TESTS= PYTHON= OS_ID=ubuntu RND_SEED=1643988103.7971287 
CACHE_OUTPUT= test

make[1]: Entering directory '/home/supervisor/libvpp/test'
15:21:46,418 Temporary dir is 
/tmp/vpp-unittest-SanityTestCase-x4melzcc, api socket is 
/tmp/vpp-unittest-SanityTestCase-x4melzcc/api.sock
15:21:46,418 vpp_cmdline args: 
['/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/bin/vpp', 
'unix', '{', 'nodaemon', '', 'full-coredump', 'coredump-size 
unlimited', 'runtime-dir', 
'/tmp/vpp-unittest-SanityTestCase-x4melzcc', '}', 'api-trace', '{', 
'on', '}', 'api-segment', '{', 'prefix', 
'vpp-unittest-SanityTestCase-x4melzcc', '}', 'cpu', '{', 'main-core', 
'0', '}', 'physmem', '{', 'max-size', '32m', '}', 'statseg', '{', 
'socket-name', '/tmp/vpp-unittest-SanityTestCase-x4melzcc/stats.sock', 
'', '}', 'socksvr', '{', 'socket-name', 
'/tmp/vpp-unittest-SanityTestCase-x4melzcc/api.sock', '}', 'node { ', 
'', '}', 'api-fuzz {', 'off', '}', 'plugins', '{', 'plugin', 
'dpdk_plugin.so', '{', 'disable', '}', 'plugin', 'rdma_plugin.so', 
'{', 'disable', '}', 'plugin', 'lisp_unittest_plugin.so', '{', 
'enable', '}', 'plugin', 'unittest_plugin.so', '{', 'enable', '}', 
'}', 'plugin_path', 
'/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins:/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/lib64/vpp_plugins', 
'test_plugin_path', 
'/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/lib/vpp_api_test_plugins:/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/lib64/vpp_api_test_plugins']
15:21:46,418 vpp_cmdline: 
/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/bin/vpp 
unix { nodaemon  full-coredump coredump-size unlimited runtime-dir 
/tmp/vpp-unittest-SanityTestCase-x4melzcc } api-trace { on } 
api-segment { prefix vpp-unittest-SanityTestCase-x4melzcc } cpu { 
main-core 0 } physmem { max-size 32m } statseg { socket-name 
/tmp/vpp-unittest-SanityTestCase-x4melzcc/stats.sock  } socksvr { 
socket-name /tmp/vpp-unittest-SanityTestCase-x4melzcc/api.sock } node 
{ } api-fuzz { off } plugins { plugin dpdk_plugin.so { disable } 
plugin rdma_plugin.so { disable } plugin lisp_unittest_plugin.so { 
enable } plugin unittest_plugin.so { enable } } plugin_path 
/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins:/home/supervisor/libvpp/build-root/install-vpp_debug-native/vpp/lib64/vpp_plugins 
test_plugin_path 
/home/supervisor/libvpp/build-root/install-vpp_debug-na

Re: [vpp-dev] Install vpp with router/netlink plugin and FRR #vpp

[Dave Wallace]

Suresh,

Please be aware that VPP 20.04 has not been supported for well over a 
year (since VPP 20.09 was released).


I would highly recommend that you move forward to stable/21.10 or the 
soon to be released stable/22.02 branch.  Based on 20.04, you are 
effectively on your own.


Thanks,
-daw-

On 2/3/22 5:59 AM, Pim van Pelt wrote:

Hoi Suresh,

Do not use this plugin, we really should delete it. Recently, work on 
Linux Control Plane has progressed - please take a look at the 
following resources -- https://ipng.ch/s/articles/
It describes the work that we've been doing to create a feature 
complete BGP/OSPF/ISIS capable plugin for VPP.


If you build VPP at HEAD, you will find a plugin called 'linux-cp' 
which contains the code you need to expose FRR and other higher level 
routing suites. I recommend you read the posts above, and possibly 
take out a KVM image with FRR + Bird2 prebuilt here: 
https://ipng.ch/s/articles/2021/12/23/vpp-playground.html


If you're feeling adventurous, you can take a look at the completed 
plugin in an out-or-tree (and fully unsupported by the community :) 
repository at github.com/pimvanpelt/lcpng 
 but you won't need it anymore, as 
the lion's share of the code has been committed to VPP. I hope to 
finish upstreaming the last bits of code into VPP in time for the next 
release (which will be VPP 22.06).


groet,
Pim

On Thu, Feb 3, 2022 at 1:14 AM  wrote:

Hi all,

   My goal is to install FRR and VPP with all router/network
plugin directly on ubunut 20.04 without any VM.

I am following this link to complete my goal
'https://github.com/FRRouting/frr/wiki/Alternate-forwarding-planes%3A-VPP'.
But here the author explains how to install VPP on vagrant, Can
some one help or point to link where I cna install VPP directly on
ubuntu with all required plugins(netlink/router plugin)

When I try to follow same steps by eliminating Vagrant related
commands I see below error

$ git clone https://gerrit.fd.io/r/vpp

$ git clone https://gerrit.fd.io/r/vpps

$ sudo apt-get install -y python-cffi python-pycparser

$ cd /vpp

$ git checkout v18.10

$ ln -sf /home/vagrant/vppsb/netlink

$ ln -sf /home/vagrant/vppsb/router

$ ln -sf ../../netlink/netlink.mk 
build-data/packages/

$ ln -sf ../../router/router.mk 
build-data/packages/

$ cd build-root/

$ make V=0 PLATFORM=vpp TAG=vpp_debug install-deb netlink-install
router-install


gna@admin:~/vpp/build-root$ make V=0 PLATFORM=vpp TAG=vpp_debug
netlink-install router-install
 Arch for platform 'vpp' is native 
 Finding source for external 
 Makefile fragment found in
/home/gna/vpp/build-data/packages/external.mk 

 Source found in /home/gna/vpp/build 
 Arch for platform 'vpp' is native 
 Finding source for vpp 
 Makefile fragment found in
/home/gna/vpp/build-data/packages/vpp.mk  
 Source found in /home/gna/vpp/src 
 Arch for platform 'vpp' is native 
 Finding source for netlink 
 Makefile fragment found in
/home/gna/vpp/build-data/packages/netlink.mk  
 Source found in /home/gna/vpp/netlink 
 Configuring external: nothing to do 
 Building external: nothing to do 
 Installing external 
make[1]: Entering directory '/home/gna/vpp/build/external'
make install
make[2]: Entering directory '/home/gna/vpp/build/external'
--- installing nasm 2.14.02 - log:
/home/gna/vpp/build-root/build-vpp_debug-native/external/nasm.install.log
*autoreconf: 'configure.ac ' or 'configure.in
' is required*
*make[3]: *** No rule to make target 'configure', needed by
'config.status'.  Stop.*
*make[2]: *** [packages/nasm.mk:22 :
/home/gna/vpp/build-root/build-vpp_debug-native/external/.nasm.install.ok]
Error 2*
make[2]: Leaving directory '/home/gna/vpp/build/external'
make[1]: *** [Makefile:169: ebuild-install] Error 2
make[1]: Leaving directory '/home/gna/vpp/build/external'
make: *** [Makefile:732: external-install] Error 2







--
Pim van Pelt 
PBVP1-RIPE - http://www.ipng.nl/




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20825): https://lists.fd.io/g/vpp-dev/message/20825
Mute This Topic: https://lists.fd.io/mt/88873111/21656
Mute #vpp:https://lists.fd.io/g/vpp-dev/mutehashtag/vpp
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Community call today

[Dave Wallace]

Hi Damjan,

I just noticed that the .ics file has the meeting scheduled for 2nd and 
4th Tuesdays in each month instead of bi-weekly, which means that 
meetings per the .ics are wrong starting in April.


Thanks,
-daw-

On 1/25/22 7:06 AM, Damjan Marion via lists.fd.io wrote:

Just a reminder, today we have community call, as we agreed to move to 
bi-weekly format.

I created .ics file so people can put it in the calendar.

Please let me know if you have any topics to discuss…


—
Damjan






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20804): https://lists.fd.io/g/vpp-dev/message/20804
Mute This Topic: https://lists.fd.io/mt/88669896/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP 22.02 RC1 milestone is complete!

[Dave Wallace]

Excellent!

Thanks for getting the VPP 22.02 release cycle under way :D
-daw-

On 1/19/2022 3:29 PM, Andrew Yourtchenko wrote:

Hi all,

the VPP 22.02 RC1 milestone is complete!

The master branch is open for all commits, the stable/2202 is open for
the bugfixes (other than the exception related to the wireguard that
was discussed in the other thread today).

The artifacts are available at the packagecloud.io/fdio/2202

The RC2 milestone is on the 9th of February 2022.

Thanks a lot!

--a /* your friendly 22.02 release manager */




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20767): https://lists.fd.io/g/vpp-dev/message/20767
Mute This Topic: https://lists.fd.io/mt/88543995/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] FD.io CI operational once again [was: FD.io CI outage]

[Dave Wallace]

CI is operational again after Jenkins was restarted.  I'll be issuing 
'recheck' for those patches submitted that failed to have jobs started.


Thanks,
-daw-

On 12/15/21 1:18 PM, Dave Wallace via lists.fd.io wrote:
[0] 
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23405


On 12/15/21 1:13 PM, Dave Wallace via lists.fd.io wrote:

Folks,

Due to service issues in AWS, gerrit.fd.io (AWS instance) is 
currently not communicating with jenkins.fd.io (Vexxhost instance).


I have opened a ticket with LF-IT [0] and Vanessa has put 
jenkins.fd.io into shutdown mode in anticipation of a reset when the 
communications issue is resolved.


Thanks,
-daw-







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20639): https://lists.fd.io/g/vpp-dev/message/20639
Mute This Topic: https://lists.fd.io/mt/87752629/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] FD.io CI outage

[Dave Wallace]

[0] https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23405

On 12/15/21 1:13 PM, Dave Wallace via lists.fd.io wrote:

Folks,

Due to service issues in AWS, gerrit.fd.io (AWS instance) is currently 
not communicating with jenkins.fd.io (Vexxhost instance).


I have opened a ticket with LF-IT [0] and Vanessa has put 
jenkins.fd.io into shutdown mode in anticipation of a reset when the 
communications issue is resolved.


Thanks,
-daw-




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20638): https://lists.fd.io/g/vpp-dev/message/20638
Mute This Topic: https://lists.fd.io/mt/87749872/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] FD.io CI outage

[Dave Wallace]

Folks,

Due to service issues in AWS, gerrit.fd.io (AWS instance) is currently 
not communicating with jenkins.fd.io (Vexxhost instance).


I have opened a ticket with LF-IT [0] and Vanessa has put jenkins.fd.io 
into shutdown mode in anticipation of a reset when the communications 
issue is resolved.


Thanks,
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20637): https://lists.fd.io/g/vpp-dev/message/20637
Mute This Topic: https://lists.fd.io/mt/87749872/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Security Contact

[Dave Wallace]

Hi Raj,

Please send an email to secur...@lists.fd.io describing this potential 
issue you would like to report.


Thanks,
-daw-

On 12/10/21 4:41 AM, S Rajkumar wrote:

Hello,

Just checking if there is a security contact to notify a potential 
security vulnerability in VPP


raj








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20622): https://lists.fd.io/g/vpp-dev/message/20622
Mute This Topic: https://lists.fd.io/mt/87632666/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP release 21.10.1 artifacts are available on packagecloud.io

[Dave Wallace]

Most excellent!

Kudos to Andrew for making this happen.
-daw-

On 11/17/21 3:09 PM, Andrew Yourtchenko wrote:

Hi all,

VPP release 21.10.1 artifacts are available at packagecloud.io/fdio/release.

Thanks a lot to Dave Wallace and Vanessa Valderrama for the help!

--a






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20513): https://lists.fd.io/g/vpp-dev/message/20513
Mute This Topic: https://lists.fd.io/mt/87128508/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP 21.10.1 Maintenance Release

[Dave Wallace]

Hi Petr,

I have cherry-picked this into stable/2110 and Andrew will merge it once 
it has verified so that it will be included in the VPP 21.10.1 
Maintenance Release.


Thanks,
-daw-

On 11/15/21 12:54 PM, Petr Boltík wrote:

Hello,

please consider including https://gerrit.fd.io/r/c/vpp/+/34040 
<https://gerrit.fd.io/r/c/vpp/+/34040>


Thanks
Petr

po 15. 11. 2021 v 16:24 odesílatel Dave Wallace <mailto:dwallac...@gmail.com>> napsal:


Folks,

As discussed in last Tuesday's VPP Community Meeting, there are
some missing header files in the 21.10 VPP release which the HICN
project requires. Therefore the VPP 21.10.1 Maintenance release is
scheduled for this Wed. Nov 17, 2021 which will include the
cherry-pick [0] that resolves this issue.

Please let us know if there are any additional cherry-picks that
should be included in this maintenance release.

Thanks,
-daw-

[0] https://gerrit.fd.io/r/c/vpp/+/34339
<https://gerrit.fd.io/r/c/vpp/+/34339>






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20497): https://lists.fd.io/g/vpp-dev/message/20497
Mute This Topic: https://lists.fd.io/mt/87071413/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP 21.10.1 Maintenance Release

[Dave Wallace]

Folks,

As discussed in last Tuesday's VPP Community Meeting, there are some 
missing header files in the 21.10 VPP release which the HICN project 
requires. Therefore the VPP 21.10.1 Maintenance release is scheduled for 
this Wed. Nov 17, 2021 which will include the cherry-pick [0] that 
resolves this issue.


Please let us know if there are any additional cherry-picks that should 
be included in this maintenance release.


Thanks,
-daw-

[0] https://gerrit.fd.io/r/c/vpp/+/34339

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20493): https://lists.fd.io/g/vpp-dev/message/20493
Mute This Topic: https://lists.fd.io/mt/87071413/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] project call

[Dave Wallace]

+1

On 11/9/21 12:20 PM, Damjan Marion via lists.fd.io wrote:

Today on the project call, we were discussing about doing some changes on those 
calls.

Proposal from few of us who were attending is:

- we should make it less formal, stop doing readouts and focus on specific 
topics to discuss, if there is no topics to discuss we simply drop

- we move to biweekly, same time, 2nd and 4th Tue each month

- to increase attendance we encourage people having something to discuss to 
announce that in advance on the mailing list

- we should preferably use this mailing list if we need to make any decisions


What other people think?

Thanks,

—
Damjan







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20466): https://lists.fd.io/g/vpp-dev/message/20466
Mute This Topic: https://lists.fd.io/mt/86936610/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Headers files missing in VPP version 21.10

[Dave Wallace]

Hi Mauro,

I merged your cherry-pick to stable/21.10 [1] and will work with Andrew 
to schedule a maintenance release.


Thanks,
-daw-

On 11/3/21 1:09 PM, Mauro Sardara (msardara) via lists.fd.io wrote:


Hello All,

I am having an issue with the new VPP version 21.10 because of some 
header files missing.


The issue was fixed in master a few days ago [0], but it is still 
present in the tag v21.10, so
I cherry-picked the change and created a patch for the branch 
stable/2110 [1].


Is it possible to release a new version 21.10.1 containing this fix?

Thanks in advance for your support.

Regards,
Mauro.


[0]https://github.com/FDio/vpp/commit/d9fc708ee0c8c42fa09dda5d29e9cb0f985558dc#diff-931430ce72263164a78d72bf46cfb75cf63d5503fd60293a7f4fd9e70aca2383

[1]https://gerrit.fd.io/r/c/vpp/+/34339





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20440): https://lists.fd.io/g/vpp-dev/message/20440
Mute This Topic: https://lists.fd.io/mt/86796422/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] CI Outage due to CA Certificate issue

[Dave Wallace]

Folks,

The FD.io CI is once again fully operational.

The issue was resolved by updating centos7 CA root store [0] and 
replacing the use of https with the git transport protocol in 
ci-management scripts [1] by utilizing the $GIT_URL environment variable 
as the jenkins git plugin does for project repo cloning.


Ubuntu and other distros have recently updated of the ca-certificates 
package which removes the expired Let's Encrypt cert.  If you are having 
certificate issues, then the following will resolve the issue ubuntu-20.04:


sudo apt update
sudo apt install ca-certificates

Thank you for your patience during this outage.
-daw-

ps. I am in the process of building new docker executor images to 
include the updated ca-certificates and other package updates and will 
put them into production as soon as they have been verified.


[0] https://gerrit.fd.io/r/c/ci-management/+/33925
[1] https://gerrit.fd.io/r/c/ci-management/+/33931

On 9/30/21 4:36 PM, Dave Wallace via lists.fd.io wrote:

Folks,

Let's Encrypt had a root certificate expire today which is causing 
failures of the vpp-device jobs.  Here is the failure signature:


- %< -
fatal: unable to access 'https://gerrit.fd.io/r/csit/': server 
certificate verification failed. CAfile: none CRLfile: none

- %< -

I have opened a ticket [0] with LF-IT and they are working to resolve 
the issue.


Thanks,
-daw-

[0] 
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22993





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20270): https://lists.fd.io/g/vpp-dev/message/20270
Mute This Topic: https://lists.fd.io/mt/85983882/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] CI Outage due to CA Certificate issue

[Dave Wallace]

Folks,

Let's Encrypt had a root certificate expire today which is causing 
failures of the vpp-device jobs.  Here is the failure signature:


- %< -
fatal: unable to access 'https://gerrit.fd.io/r/csit/': server 
certificate verification failed. CAfile: none CRLfile: none

- %< -

I have opened a ticket [0] with LF-IT and they are working to resolve 
the issue.


Thanks,
-daw-

[0] https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22993

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20258): https://lists.fd.io/g/vpp-dev/message/20258
Mute This Topic: https://lists.fd.io/mt/85983882/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] FD.io CI Outage has been resolved

[Dave Wallace]

Folks,

Sorry for the late notice, but I've been meeting bound while 
troubleshooting today's FD.io CI outage.


There was a network configuration change in the Vexxhost datacenter that 
cause the public IP address of jenkins to become inaccessible from the 
Nomad cluster causing all jobs to fail. This has been resolved.


Another issue still remains, that is why the external address was being 
used. It was determined that Jenkins was configured this way in the a 
portion of the cloud configuration even though Jenkins was configured to 
use the internal IP address in the global configuration variables.


Unfortunately updating the cloud configuration failed to work after the 
network issues were resolved and restoring the cloud configuration to 
use jenkins.fd.io resolved the issue.


Given today's outage, I have recommended that Andrew push back the VPP 
21.10 branch pull to Thursday 9/23/2021.


Kudo's to Peter Mikus for identifying the root cause of the outage, 
Vanessa Valderrama for assisting during a PTO day to manage Jenkins 
configuration changes & restarts, and Anton Baranov & Mohammed Naser for 
fixing the data center network configuration.


Thanks,
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20174): https://lists.fd.io/g/vpp-dev/message/20174
Mute This Topic: https://lists.fd.io/mt/85775812/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Job Failures due to 'Java Connection Closed Exception'

[Dave Wallace]

Folks,

Starting around 1:15pm DST / 5:15pm UTC, there has been a 20-30% job 
failure rate due to 'Java Connection Closed Exception' causing a 100% 
verification failure rate of VPP gerrit changes.  I have been working 
with Vanessa in LF-IT and Mohammed at Vexxhost to resolve the issue.


Based on past causes of connection resets, all network paths between the 
Nomad cluster and Jenkins instance were tested for latency and packet 
loss without any issues being uncovered.  Jenkins was restarted which 
unfortunately did not resolve the issue.  Then the primary Nomad server 
which Jenkins is configured to connect to for spinning up executors was 
rebooted.  This too failed to resolve the issue.


Further investigation tonight with Mohammed's assistance (a huge THANK 
YOU to Mohammed for staying up late debugging this), seems to indicate 
that the docker containers are dying prematurely. However, the nomad 
logs are also being removed at the same time so there is presently no 
means of verifying if the containers are being terminated due to 
internal events.  The next step is to temporarily disable or reduce the 
frequency of nomad garbage collection, archive the nomad logs and then 
collate them with the system logs to determine the order of events that 
cause the docker containers to be terminated.


Thank you for your patience as the root cause of this outage is being 
investigated & fixed.

-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20034): https://lists.fd.io/g/vpp-dev/message/20034
Mute This Topic: https://lists.fd.io/mt/85179512/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] CI Job failures: Java Connection Closed Exception

[Dave Wallace]

Final update: Peter fixed the vpp-device job issue and I have issued 
'recheck' on all gerrit changes in the VPP queue which failed due to 
this week's outage.


Operation of the CI is now back to normal.  There are still a low rate 
of 'git clone' failures at a rate of ~ 1/day, so some 'recheck's may be 
required if a job fails to clone the vpp repo. The solution for this 
issue is tentatively scheduled to occur in early August.


Thanks again for your patience.
-daw-

On 7/20/2021 6:08 PM, Dave Wallace via lists.fd.io wrote:

Folks,

After troubleshooting latency issues in the datapath between the 
Jenkins openstack instance and the Nomad cluster, the host of the 
Ingress instance appeared to be the source of the problem and the 
Ingress instance was live migrated to another host.  In addition, the 
primary Nomad server was rebooted. These changes resolved the 'Java 
Connection Closed Exception' issues.


However, at this time, the vpp-device job is still failing due to a 
known issue which will be resolved when Peter Mikus comes online 
tomorrow morning CET.  Once the vpp-device job failures have been 
resolved, I will be issuing 'recheck' on open VPP gerrit changes which 
are failing due to the vpp-device job. Please feel free to 'recheck' 
your gerrit changes if you would like to verify that the rest of the 
CI jobs complete successfully.


I'd like to thank Mohammed Naser, Vanessa Valderrama, Anton Baranov, 
Peter Mikus & Maciek Konstantynowicz for their coordinated efforts in 
resolving this outage.


Thanks again for your patience during this CI outage.
-daw-

On 7/19/2021 10:51 PM, Dave Wallace via lists.fd.io wrote:

Folks,

Vanessa performed a Jenkins reset at my request to see if that would 
resolve this problem.  Unfortunately the Jenkins reset did not 
resolve the connection resets. A recheck of gerrit change after the 
Jenkins restart failed with multiple job failures due to TCP 
connection resets:


https://gerrit.fd.io/r/c/vpp/+/32858/6#message-c77806c2fd58c3c00935e1b5589a402e4b670f9f

There has also been no correlation with Ping Monitor events, Nomad 
cluster events, Nomad host, subnet, or docker image.


Investigation continues in the datapath between the Jenkins openstack 
instance and the Nomad cluster.


Thanks again for your patience.
-daw-

On 7/19/2021 11:29 AM, Dave Wallace via lists.fd.io wrote:

Folks,

There have been large numbers CI job failures due to 'Java 
Connection Closed Exception' that appear to have started occurring 
on July 17.


I have opened a ticket with Vexxhost and am actively diagnosing the 
problem with them.


Thank you for your patience while the issue is being resolved.
-daw-












-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19842): https://lists.fd.io/g/vpp-dev/message/19842
Mute This Topic: https://lists.fd.io/mt/84310372/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] CI Job failures: Java Connection Closed Exception

[Dave Wallace]

Folks,

After troubleshooting latency issues in the datapath between the Jenkins 
openstack instance and the Nomad cluster, the host of the Ingress 
instance appeared to be the source of the problem and the Ingress 
instance was live migrated to another host.  In addition, the primary 
Nomad server was rebooted. These changes resolved the 'Java Connection 
Closed Exception' issues.


However, at this time, the vpp-device job is still failing due to a 
known issue which will be resolved when Peter Mikus comes online 
tomorrow morning CET.  Once the vpp-device job failures have been 
resolved, I will be issuing 'recheck' on open VPP gerrit changes which 
are failing due to the vpp-device job.  Please feel free to 'recheck' 
your gerrit changes if you would like to verify that the rest of the CI 
jobs complete successfully.


I'd like to thank Mohammed Naser, Vanessa Valderrama, Anton Baranov, 
Peter Mikus & Maciek Konstantynowicz for their coordinated efforts in 
resolving this outage.


Thanks again for your patience during this CI outage.
-daw-

On 7/19/2021 10:51 PM, Dave Wallace via lists.fd.io wrote:

Folks,

Vanessa performed a Jenkins reset at my request to see if that would 
resolve this problem.  Unfortunately the Jenkins reset did not resolve 
the connection resets. A recheck of gerrit change after the Jenkins 
restart failed with multiple job failures due to TCP connection resets:


https://gerrit.fd.io/r/c/vpp/+/32858/6#message-c77806c2fd58c3c00935e1b5589a402e4b670f9f

There has also been no correlation with Ping Monitor events, Nomad 
cluster events, Nomad host, subnet, or docker image.


Investigation continues in the datapath between the Jenkins openstack 
instance and the Nomad cluster.


Thanks again for your patience.
-daw-

On 7/19/2021 11:29 AM, Dave Wallace via lists.fd.io wrote:

Folks,

There have been large numbers CI job failures due to 'Java Connection 
Closed Exception' that appear to have started occurring on July 17.


I have opened a ticket with Vexxhost and am actively diagnosing the 
problem with them.


Thank you for your patience while the issue is being resolved.
-daw-









-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19840): https://lists.fd.io/g/vpp-dev/message/19840
Mute This Topic: https://lists.fd.io/mt/84310372/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] CI Job failures: Java Connection Closed Exception

[Dave Wallace]

Folks,

Vanessa performed a Jenkins reset at my request to see if that would 
resolve this problem.  Unfortunately the Jenkins reset did not resolve 
the connection resets. A recheck of gerrit change after the Jenkins 
restart failed with multiple job failures due to TCP connection resets:


https://gerrit.fd.io/r/c/vpp/+/32858/6#message-c77806c2fd58c3c00935e1b5589a402e4b670f9f

There has also been no correlation with Ping Monitor events, Nomad 
cluster events, Nomad host, subnet, or docker image.


Investigation continues in the datapath between the Jenkins openstack 
instance and the Nomad cluster.


Thanks again for your patience.
-daw-

On 7/19/2021 11:29 AM, Dave Wallace via lists.fd.io wrote:

Folks,

There have been large numbers CI job failures due to 'Java Connection 
Closed Exception' that appear to have started occurring on July 17.


I have opened a ticket with Vexxhost and am actively diagnosing the 
problem with them.


Thank you for your patience while the issue is being resolved.
-daw-






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19836): https://lists.fd.io/g/vpp-dev/message/19836
Mute This Topic: https://lists.fd.io/mt/84310372/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] CI Job failures: Java Connection Closed Exception

[Dave Wallace]

Folks,

There have been large numbers CI job failures due to 'Java Connection 
Closed Exception' that appear to have started occurring on July 17.


I have opened a ticket with Vexxhost and am actively diagnosing the 
problem with them.


Thank you for your patience while the issue is being resolved.
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19835): https://lists.fd.io/g/vpp-dev/message/19835
Mute This Topic: https://lists.fd.io/mt/84310372/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP 21.01.1 Maintenance Release Scheduled for Wednesday July 14, 2021

[Dave Wallace]

Folks,

The VPP 21.01.1 Maintenance Release is scheduled for next Wednesday, 
July 14, 2021.


VPP Maintainers please review fixes for your feature and cherry-pick any 
that are appropriate to the stable/2101 branch before 1200 UTC on 
Tuesday July 13, 2021.


Thanks,
-daw-
"Your Friendly VPP Release Manager"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19728): https://lists.fd.io/g/vpp-dev/message/19728
Mute This Topic: https://lists.fd.io/mt/84070909/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP release 21.06 is complete!

[Dave Wallace]

Congratulations to the FD.io community and all who contributed to yet 
another on time VPP release!


Special thanks to Andrew for his work in automating and streamlining the 
release process.


Thanks,
-daw-

On 6/30/2021 3:18 PM, Andrew Yourtchenko wrote:

Hi all,

VPP release 21.06 is complete and is available from the usual
packagecloud.io/fdio/release location!

I have verified using the scripts [0] that the new release installs
and runs on the Centos8, Debian 10 (Buster) as well as Ubuntu 18.04
and 20.04.

Special shout-out goes to pnat plugin which has the hardcoded version of 0.0.1,
hopefully it will be rectified for 21.10 release :-)

The release notes are visible at
https://docs.fd.io/vpp/21.06/d5/d36/release_notes_2106.html

A small remark: if you are installing on Debian or Ubuntu 20.04 in a container,
you might need to "export VPP_INSTALL_SKIP_SYSCTL=1" before
installation such that it skips calling the sysctl command which will
fail.

Please let me know if you experience any  issues.

Thanks a lot to Dave Wallace, Florin Coras and Vanessa Valderrama for their help
during the release preparations and release process !

[0] https://github.com/ayourtch/vpp-relops/tree/master/docker-tests

--a /* your friendly 21.06 release manager */






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19666): https://lists.fd.io/g/vpp-dev/message/19666
Mute This Topic: https://lists.fd.io/mt/83900236/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Proposed removal of Centos-8 jobs from master

[Dave Wallace]

Hi Matt,

Excellent.  Will plan to merge the patch [0] removing 
vpp-*-master-centos8-* jobs tomorrow.


Thanks,
-daw-

[0] https://gerrit.fd.io/r/c/ci-management/+/32615

On 6/8/2021 12:04 PM, Matthew Smith wrote:


Hi,

I mentioned at the community meeting that Netgate currently builds & 
distributes VPP RPMs for CentOS 8 and I would need to confirm 
internally whether disabling those jobs would cause any problems for us.


I confirmed that we do not have any issue with removing those CI jobs. 
We generate our own RPMs and do not distribute the ones that are 
uploaded to packagecloud. Since the Makefiles & spec files for 
building RPMs will be left intact and we will still be able to 
generate RPMs on our own, we have no objection to the CI jobs being 
disabled.


Thanks!
-Matt


On Mon, Jun 7, 2021 at 10:43 AM Damjan Marion via lists.fd.io 
<http://lists.fd.io> <mailto:me@lists.fd.io>> wrote:





On 07.06.2021., at 17:24, Dave Wallace mailto:dwallac...@gmail.com>> wrote:

Folks,

The RPM builds have been unmaintained for a couple years now and
the CentOS-8 jobs have become the long pole in the CI
verification cycle as well as costing time to maintain the builds
due to changes upstream.

I am proposing that the vpp-*-master-centos-8-* jobs be removed
from the CI until someone steps up to invest in removal of the
technical debt that has accumulated in the RPM build infrastructure.

If no one steps up to maintain the RPM build infrastructure, then
I would also recommend that it be removed from the VPP build
infrastructure as well.

Damjan, can you please add this to the agenda for tomorrow's VPP
Monthly Community meeting?


Fully agree. Will add….

—
Damjan








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19539): https://lists.fd.io/g/vpp-dev/message/19539
Mute This Topic: https://lists.fd.io/mt/83372643/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Proposed removal of Centos-8 jobs from master

[Dave Wallace]

Folks,

The RPM builds have been unmaintained for a couple years now and the 
CentOS-8 jobs have become the long pole in the CI verification cycle as 
well as costing time to maintain the builds due to changes upstream.


I am proposing that the vpp-*-master-centos-8-* jobs be removed from the 
CI until someone steps up to invest in removal of the technical debt 
that has accumulated in the RPM build infrastructure.


If no one steps up to maintain the RPM build infrastructure, then I 
would also recommend that it be removed from the VPP build 
infrastructure as well.


Damjan, can you please add this to the agenda for tomorrow's VPP Monthly 
Community meeting?


Thanks,
-daw-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19534): https://lists.fd.io/g/vpp-dev/message/19534
Mute This Topic: https://lists.fd.io/mt/83372643/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] CentOs package issue fix

[Dave Wallace]

Folks,

I pushed a patch [0] that resolves the following package install issue 
on CentOS-8 jobs.


If you are seeing centos8 job failures with the following signature, 
please rebase your patch and recheck it:


- %< -
20:50:44  Error:
20:50:44   Problem: cannot install the best candidate for the job
20:50:44    - nothing provides glibc-devel = 2.28-151.el8 needed by 
glibc-static-2.28-151.el8.x86_64
20:50:44  (try to add '--skip-broken' to skip uninstallable packages or 
'--nobest' to use not only best candidate packages)

- %< -

I'm rebuilding the docker images to pick up the latest packages and will 
test/deploy them soon.


Thanks,
-daw-

[0] https://gerrit.fd.io/r/c/vpp/+/32561

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19526): https://lists.fd.io/g/vpp-dev/message/19526
Mute This Topic: https://lists.fd.io/mt/83296642/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [tsc] FDIO Jenkins Maintenance - 2021-05-11 1800UTC - 2000UTC

[Dave Wallace]

The maintenance is complete and so far the CI jobs are looking happier.

We will continue to monitor the performance of the system.

Thank you again for your patience.
-daw-

On 5/11/2021 1:50 PM, Dave Wallace via lists.fd.io wrote:

*What*:

Jenkins has been placed in shutdown mode in preparation to perform 
unplanned maintenance


*When*:

2021-05-11 1800 UTC to 2000 UTC

*Impact*:

Jenkins sandbox and production will be unavailable during this time

*Why*:

The vendor will be moving network gateways to the new data center 
where the nomad servers now reside to address TCP connection issues 
aborting FD.io CI jobs.







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19371): https://lists.fd.io/g/vpp-dev/message/19371
Mute This Topic: https://lists.fd.io/mt/82757043/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] FDIO Jenkins Maintenance - 2021-05-11 1800UTC - 2000UTC

[Dave Wallace]

*What*:

Jenkins has been placed in shutdown mode in preparation to perform 
unplanned maintenance


*When*:

2021-05-11 1800 UTC to 2000 UTC

*Impact*:

Jenkins sandbox and production will be unavailable during this time

*Why*:

The vendor will be moving network gateways to the new data center where 
the nomad servers now reside to address TCP connection issues aborting 
FD.io CI jobs.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19369): https://lists.fd.io/g/vpp-dev/message/19369
Mute This Topic: https://lists.fd.io/mt/82752846/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-