[vpp-dev] vppctl doesn't report returned pings from rdma int
I noticed on a couple of servers that I have interconnected in packet.net that when using vppctl ping command, the rdma interface the ping command doesn't report returned packets. ping says 0 received, but the received packets show up in counts in show int though. --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13118): https://lists.fd.io/g/vpp-dev/message/13118 Mute This Topic: https://lists.fd.io/mt/31723900/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] rdma driver
On 05/13/2019 01:22 PM, Damjan Marion wrote: On 13 May 2019, at 19:15, Billy <mailto:bmcf...@redhat.com>> wrote: On Mon, May 13, 2019 at 10:18 AM Benoit Ganne (bganne) via Lists.Fd.Io <http://lists.fd.io/> <mailto:cisco@lists.fd.io>> wrote: Hi Thomas, > The external rdma driver includes parts of ib-verbs which are provided as > part of the fedora 30 such as /usr/include/rdma/ib_user_verbs.h. > This prevents installation of vpp on Fedora 30 and upgraded Fedora 29. I think I am trying to understand a similar issue with CentOS packaging. Just to make sure I understand correctly: what you see is vpp-deps RPM conflicting on installation with kernel-headers RPM because it is trying to install /usr/include/rdma/ib_user_verbs.h, which is already provided by kernel-headers. Correct? I don't think this is a problem in the rdma ext driver. I think that stuff that used to be in rdma-devel rpm is now in kernel-headers as of Fed30. Let me research further. I think Fedora 30 has moved some headers that used to be in the rdma rpm into the kernel-devel package as the Mellanox drivers have been mainstreamed. I suspect that this same problem will appear with CentOS 8. Yes, that is correct. $ sudo rpm -i build-root/*.rpm file /usr/include/rdma from install of vpp-devel-19.08-rc0~196_g7fe470a54.x86_64 conflicts with file from package kernel-headers-5.0.9-200.fc29.x86_64 file /usr/include/rdma/ib_user_verbs.h from install of vpp-devel-19.08-rc0~196_g7fe470a54.x86_64 conflicts with file from package kernel-headers-5.0.9-200.fc29.x86_64 If so, I am a little puzzled because packagecloud RPMs for CentOS do not include /usr/include/rdma/* files, and the same is true when I build those package myself. Fedora packages are different (and newer) than CentOS. So the difference is not unusual. Could you document the steps to reproduce the issue in VPP jira: https://jira.fd.io/projects/VPP/ https://jira.fd.io/browse/VPP-1674 Right solution to this problem will be that VPP RPM packaging stops blindly packaging all *.h files into vpp-devel package and it starts using CMake components instead. This particular section in extras/rpm/vpp.spec: for dir in $(find %{_mu_build_dir}/%{_vpp_install_dir}/*/include/ -maxdepth 0 -type d -print | grep -v dpdk) do for subdir in $(cd ${dir} && find . -type d -print) do mkdir -p -m755 %{buildroot}/usr/include/${subdir} done for file in $(cd ${dir} && find . -type f -print) do install -p -m 644 $dir/$file %{buildroot}%{_includedir}/$file done done I agree on this point. This is legacy code in the spec file that scrapes up all the header files is not the best way of doing things. Ideally, the RPM packaging the RPM packaging from the cmake files to build separate packages for exts and plugins each with its own devel rpm. I think the solution to Ben's problem is above though. -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13010): https://lists.fd.io/g/vpp-dev/message/13010 Mute This Topic: https://lists.fd.io/mt/31607407/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] rdma driver
Benoit, The external rdma driver includes parts of ib-verbs which are provided as part of the fedora 30 such as . /usr/include/rdma/ib_user_verbs.h. This prevents installation of vpp on Fedora 30 and upgraded Fedora 29. --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13004): https://lists.fd.io/g/vpp-dev/message/13004 Mute This Topic: https://lists.fd.io/mt/31607407/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] RPM package question related to https://gerrit.fd.io/r/#/c/18953/
Jerome, python3 is an implicit dependency of vpp-devel and I am not sure why. Because of that I put python36 explicitly in Requires because I was concerned about cross versions of Python between 34 and 36 having side affects. As for epel-release, it is harmless but is not strictly required installation time but I wanted to make sure the epel repo was installed so further dependency checks were resolved from the correct repo. --Tom On 05/10/2019 10:20 AM, Thomas F Herbert wrote: Jerome, Let me take a look at this today. I will submit a patch to take them out if I can verify that they are not needed. --Tom On 05/10/2019 05:11 AM, Jerome Tollet (jtollet) wrote: Hi Thomas, In https://gerrit.fd.io/r/#/c/18953/ you are putting epel-release and Python3 into the dependencies. 1. I can understand that those are needed as /BuildRequires:/, but are they really needed for /Requires: /? 2. Why do we need epel-release as runtime requirement? 3. Do we really need Python3 for VPP 19.04 itself? Jerome -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12980): https://lists.fd.io/g/vpp-dev/message/12980 Mute This Topic: https://lists.fd.io/mt/31575010/675058 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [therb...@redhat.com] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12995): https://lists.fd.io/g/vpp-dev/message/12995 Mute This Topic: https://lists.fd.io/mt/31575010/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] Question about rdma drivers in vpp 19.04
On 05/10/2019 12:46 PM, Benoit Ganne (bganne) wrote: I verified it on CentOS 7.6 and it works fine: Here i s my gist for Robert and Fred with the steps I used. https://gist.github.com/tfherbert/64cef832f03935c6a2a58729718a36ff Glad to hear, thanks a lot. In CentOS 7.6, for RDMA drivers to work, we need to install rdma rpm as I did in my 19.02 patch to get the library and the libibverbs.so library. This is documented in my patch to 19.02, https://gerrit.fd.io/r/#/c/18521/ Good point. We embed libibverb statically in the rdma plugin though, so the only remaining runtime dependency should be the kernel driver. Is this provided by rdma-core in RHEL? If so, as this is only needed by the rdma plugin, we could add rdma-core as a dependency of vpp-plugins. Regarding the startup dependency in system unit file, I am not familiar with system but can we add a "soft" dependency? Such as "must be started after rdma-load-modules@rdma.service if present"? Yes. Actually, as I think about it, I don't remember whether my test sequence verified that that had to be done. However, we know that the modules are loaded, they will persist. ben -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12992): https://lists.fd.io/g/vpp-dev/message/12992 Mute This Topic: https://lists.fd.io/mt/31570536/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] Question about rdma drivers in vpp 19.04
On 05/10/2019 12:46 PM, Benoit Ganne (bganne) wrote: I verified it on CentOS 7.6 and it works fine: Here i s my gist for Robert and Fred with the steps I used. https://gist.github.com/tfherbert/64cef832f03935c6a2a58729718a36ff Glad to hear, thanks a lot. In CentOS 7.6, for RDMA drivers to work, we need to install rdma rpm as I did in my 19.02 patch to get the library and the libibverbs.so library. This is documented in my patch to 19.02, https://gerrit.fd.io/r/#/c/18521/ Good point. We embed libibverb statically in the rdma plugin though, so the only remaining runtime dependency should be the kernel driver. Is this provided by rdma-core in RHEL? If so, as this is only needed by the rdma plugin, we could add rdma-core as a dependency of vpp-plugins. Regarding the startup dependency in system unit file, I am not familiar with system but can we add a "soft" dependency? Such as "must be started after rdma-load-modules@rdma.service if present"? Yes. I believe that just installing the RPMs will cause the kmod to get loaded. Although harmless, that step may be harmless but unnecessary. ben -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12990): https://lists.fd.io/g/vpp-dev/message/12990 Mute This Topic: https://lists.fd.io/mt/31570536/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] Question about rdma drivers in vpp 19.04
Ben, I verified it on CentOS 7.6 and it works fine: Here i s my gist for Robert and Fred with the steps I used. https://gist.github.com/tfherbert/64cef832f03935c6a2a58729718a36ff In CentOS 7.6, for RDMA drivers to work, we need to install rdma rpm as I did in my 19.02 patch to get the library and the libibverbs.so library. This is documented in my patch to 19.02, https://gerrit.fd.io/r/#/c/18521/ --Tom On 05/10/2019 12:06 PM, Benoit Ganne (bganne) wrote: Hi Robert, That could be an issue with /dev/infiniband/* access rights. Could you share the output of: ~# echo "create int rdma host-if enp94s0f1 name mlx5" > rdma.vpp ~# sudo timeout 10 strace /usr/bin/vpp "unix { nodaemon exec $PWD/rdma.vpp } plugins { plugin dpdk_plugin.so { disable } }" ~# dmesg Thanks! ben -Original Message- From: Robert Starmer Sent: vendredi 10 mai 2019 17:29 To: Thomas F Herbert Cc: Benoit Ganne (bganne) ; vpp-dev ; Damjan Marion (damarion) ; Dave Barach (dbarach) ; Fred Sharp Subject: Re: [vpp-dev] Question about rdma drivers in vpp 19.04 I just retried on a Packet.net m2.xlarge.x86 instance running Ubuntu 18.04 and I get: vpp# create int rdma host-if enp94s0f1 name mlx5 create interface rdma: Device Open Failed: Bad file descriptor On packet. I've removed the enp94s0f1 interface from the default bonded config, and the interface is in a Down state: 3: enp94s0f1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 98:03:9b:30:1e:f7 brd ff:ff:ff:ff:ff:ff The devices are ConnectX-4: lspci | grep -i mell 5e:00.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx] 5e:00.1 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx] Robert On Fri, May 10, 2019 at 7:46 AM Thomas F Herbert mailto:therb...@redhat.com> > wrote: Ben, I had this working with 19.02 with my patch using dpdk driver with rdma. https://gerrit.fd.io/r/#/c/18521/ Which I used in the rpms for CentOS. The challenge I had was that convincing dpdk to "see" the pci, That was because the server boots with the mlx ints in a bond and after removing the if from the bond, I had to explicitly whitelist it in vpp.conf. I don't know how to with the new ext rdma driver in 19.04 because it doesn't make sense to white list it for dpdk. On 05/10/2019 04:08 AM, Benoit Ganne (bganne) wrote: Hi Thomas, I just pushed a small doc: https://gerrit.fd.io/r/c/19364/3/src/plugins/rdma/rdma_doc.md I also tried: vpp# create interface rdma name mlx5 create interface rdma: invalid interface (only mlx5 supported for now) You are missing the 'host-if ' stanza, eg: vpp# create int rdma host-if enp94s0f0 name mlx5 Here enp94s0f0 is the netdev of the mhysical port you want to use. Here are my commands for 19.04 https://gist.github.com/tfherbert/624d8465c42b0aafb4859f144ba8a4e4 Let me know if you need more info. ben -- Thomas F Herbert NFV and Fast Data Planes Networking Group Office of the CTO Red Hat -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12987): https://lists.fd.io/g/vpp-dev/message/12987 Mute This Topic: https://lists.fd.io/mt/31570536/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 & Mellanox
On 05/10/2019 10:53 AM, Stephen Hemminger wrote: On Fri, 10 May 2019 12:49:51 + "Benoit Ganne (bganne) via Lists.Fd.Io" wrote: I guess you are relying on DPDK here. Are you able to use the card with DPDK testpmd? If not, you may be missing Mellanox OFED driver, depending upon DPDK version. Otherwise you can switch to VPP 19.04 and use the new native driver: https://gerrit.fd.io/r/c/19364/3/src/plugins/rdma/rdma_doc.md Best ben Current versions of Mellanox DPDK do not require OFED. With a recent DPDK > 18.05 and recent kernel all you need is the rdma core library. +1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12982): https://lists.fd.io/g/vpp-dev/message/12982 Mute This Topic: https://lists.fd.io/mt/31576338/675058 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [therb...@redhat.com] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12983): https://lists.fd.io/g/vpp-dev/message/12983 Mute This Topic: https://lists.fd.io/mt/31576338/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] Question about rdma drivers in vpp 19.04
Ben, I had this working with 19.02 with my patch using dpdk driver with rdma. https://gerrit.fd.io/r/#/c/18521/ Which I used in the rpms for CentOS. The challenge I had was that convincing dpdk to "see" the pci, That was because the server boots with the mlx ints in a bond and after removing the if from the bond, I had to explicitly whitelist it in vpp.conf. I don't know how to with the new ext rdma driver in 19.04 because it doesn't make sense to white list it for dpdk. On 05/10/2019 04:08 AM, Benoit Ganne (bganne) wrote: Hi Thomas, I just pushed a small doc: https://gerrit.fd.io/r/c/19364/3/src/plugins/rdma/rdma_doc.md I also tried: vpp# create interface rdma name mlx5 create interface rdma: invalid interface (only mlx5 supported for now) You are missing the 'host-if ' stanza, eg: vpp# create int rdma host-if enp94s0f0 name mlx5 Here enp94s0f0 is the netdev of the mhysical port you want to use. Here are my commands for 19.04 https://gist.github.com/tfherbert/624d8465c42b0aafb4859f144ba8a4e4 Let me know if you need more info. ben -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12981): https://lists.fd.io/g/vpp-dev/message/12981 Mute This Topic: https://lists.fd.io/mt/31570536/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] RPM package question related to https://gerrit.fd.io/r/#/c/18953/
Jerome, Let me take a look at this today. I will submit a patch to take them out if I can verify that they are not needed. --Tom On 05/10/2019 05:11 AM, Jerome Tollet (jtollet) wrote: Hi Thomas, In https://gerrit.fd.io/r/#/c/18953/ you are putting epel-release and Python3 into the dependencies. 1. I can understand that those are needed as /BuildRequires:/, but are they really needed for /Requires: /? 2. Why do we need epel-release as runtime requirement? 3. Do we really need Python3 for VPP 19.04 itself? Jerome -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12980): https://lists.fd.io/g/vpp-dev/message/12980 Mute This Topic: https://lists.fd.io/mt/31575010/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] Question about rdma drivers in vpp 19.04
Question about how to enable rdma driver and mlx4/5 interfaces I just loaded 19.04 on cncf infrastructure machine in packet.net with mlx 4 ints. I don't see the mlx interfaces in show int from vppctl. I am not sure how to find them. They ifs DO show up in show pci. I also tried: vpp# create interface rdma name mlx5 create interface rdma: invalid interface (only mlx5 supported for now) I had this working in 19.02 using dpdk mlx5 drivers and rdma rpm. Thanks, --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12973): https://lists.fd.io/g/vpp-dev/message/12973 Mute This Topic: https://lists.fd.io/mt/31570536/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] centos ninja failures
://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-verify-master- ubuntu1604/19027 https://jenkins.fd.io/job/vpp-verify-master-clang/6731/ : SUCCESS Logs: https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-verify-master- clang/6731 https://jenkins.fd.io/job/vpp-docs-verify-master/15343/ : SUCCESS Logs: https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-docs-verify-ma ster/15343 https://jenkins.fd.io/job/vpp-verify-master-centos7/18764/ : NOT_BUILT Logs: https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-verify-master- centos7/18764 7:11 PM fd.io JJB Patch Set 9: Verified+1 Build Successful https://jenkins.fd.io/job/vpp-verify-master-centos7/18764/ : SUCCESS Logs: https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-verify-master- centos7/18764 7:15 PM Thanks, Klement -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12956): https://lists.fd.io/g/vpp-dev/message/12956 Mute This Topic: https://lists.fd.io/mt/31543758/675058 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [therb...@redhat.com] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12957): https://lists.fd.io/g/vpp-dev/message/12957 Mute This Topic: https://lists.fd.io/mt/31543758/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] python2 requirements
Damjan, Renato, I am working on cleaning up Fedora dependencies. Do we have any need for python2 in vpp anymore? If python2 APIs are required, can python3 tools generate python2 APIs? --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12845): https://lists.fd.io/g/vpp-dev/message/12845 Mute This Topic: https://lists.fd.io/mt/31313432/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-devel install conflicts
On 04/22/2019 06:58 PM, Renato Botelho do Couto wrote: On 22/04/19 17:19, Damjan Marion wrote: On 22 Apr 2019, at 20:24, Renato Botelho do Couto wrote: Hello, When I build vpp using 'make pkg-rpm' on a CentOS 7 without having vpp-ext-deps installed it adds some includes to vpp-devel package that makes it to conflict with rdma-core-devel and kernel-headers: Transaction check error: file /usr/include/infiniband from install of vpp-devel-19.08-rc0~74_g99ad2fc3e.x86_64 conflicts with file from package rdma-core-devel-17.2-3.el7.x86_64 file /usr/include/infiniband/verbs.h from install of vpp-devel-19.08-rc0~74_g99ad2fc3e.x86_64 conflicts with file from package rdma-core-devel-17.2-3.el7.x86_64 file /usr/include/rdma from install of vpp-devel-19.08-rc0~74_g99ad2fc3e.x86_64 conflicts with file from package rdma-core-devel-17.2-3.el7.x86_64 file /usr/include/rdma from install of vpp-devel-19.08-rc0~74_g99ad2fc3e.x86_64 conflicts with file from package kernel-headers-3.10.0-957.10.1.el7.x86_64 file /usr/include/rdma/ib_user_verbs.h from install of vpp-devel-19.08-rc0~74_g99ad2fc3e.x86_64 conflicts with file from package kernel-headers-3.10.0-957.10.1.el7.x86_64 Are these files supposed to be part of vpp-devel? no If vpp-ext-deps is installed on system during build these headers don't end up on vpp-devel rpm. Yes, not surprised. RPM packaging id not in great shape. Instead of respecting cmake project components, it simply throws all .h files found in build tree into vpp-devel package... Will be great if somebody will pick it up and do it properly. I don't have much interest in messing with RPMs... We were focused on getting cmake support into downstream CentOS. Yes, all header files are stuck in vpp-devel by default. I think there should be a separate rpm for extensions and the spec file should be modified as well. Probably we should look into using cmake to build an rpm and devel rpm for each ext component. I will work on it and submit a patch. Thanks! I will be happy to help and collaborate. Please add me to review on your patch. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12837): https://lists.fd.io/g/vpp-dev/message/12837 Mute This Topic: https://lists.fd.io/mt/31300770/675058 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [therb...@redhat.com] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12844): https://lists.fd.io/g/vpp-dev/message/12844 Mute This Topic: https://lists.fd.io/mt/31300770/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 19.04 centos7 RPM package dependency errors
On 04/11/2019 06:48 PM, Paul Vinciguerra wrote: I looked at this a while back. The spec file doesn’t pick up the packages from the makefile. I can look at it in a few hours if you like. Let me know. I had intended to import the new packages from epel into Centos. Epel dependency causes problems for downstream packaging. Since this is a slow process, I can submit a patch to vpp to add the epel dependencies to the spec file since I won't be able to get rid of the epel dependency before the 19.04 release. On Apr 11, 2019, at 6:25 PM, Thomas F Herbert <mailto:therb...@redhat.com>> wrote: Dave and Ed, The Makefile has dependencies that work. However, you will need epel. The packages required are: yum install epel-release yum install mbedtls yum install python36 --Tom On 04/11/2019 05:11 PM, Florin Coras wrote: We do have it as a dependency because we want to make sure the plugin still builds. However, given that most of those who use tls use the openssl engine, we might consider not having mbedtls as a dependency for the packages that we push to packagecloud ... On a separate note, what centos do we run in the container? It seems that even python3 has some dependency errors. I guess that once we align the vagrant version with it, things should just work. Probably the vagrant image doesn't have some of these packages that are only in epel. Florin On Apr 11, 2019, at 1:55 PM, Ed Kern (ejk) <mailto:e...@cisco.com>> wrote: On Apr 11, 2019, at 2:22 PM, Florin Coras <mailto:fcoras.li...@gmail.com>> wrote: Are we building rpms on a host that has mbedtls installed? Yes the centos container has mbedtls installed….has for quite some time since it is a listed prerequisite straight out of the Makefile. Ed Just uninstalling it should disable the tlsmbedtls plugin, which is what we pretty much want. Florin On Apr 11, 2019, at 1:00 PM, Dave Wallace <mailto:dwallac...@gmail.com>> wrote: Tom/Billy, Do you know what the current status is with the VPP rpm's on master/19.04? I'm trying to install the VPP 19.04 packages frompackagecloud.io <http://packagecloud.io/>on a centos7 Vagrant/virtualbox VM (using .../vpp/extras/vagrant/Vagrantfile) to verify that the packages are correct. The 19.01 packages install fine, but the 19.04 and master packages fail with the following dependency errors: --> Finished Dependency Resolution Error: Package: vpp-plugins-19.04-rc1~b4.x86_64 (fdio_1904) Requires: libmbedtls.so.10()(64bit) Error: Package: vpp-devel-19.04-rc1~b4.x86_64 (fdio_1904) Requires: /usr/bin/python3 Error: Package: vpp-19.04-rc1~b4.x86_64 (fdio_1904) Requires: /usr/bin/python3 Error: Package: vpp-plugins-19.04-rc1~b4.x86_64 (fdio_1904) Requires: libmbedx509.so.0()(64bit) Error: Package: vpp-plugins-19.04-rc1~b4.x86_64 (fdio_1904) Requires: libmbedcrypto.so.2()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Thanks, -daw- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12768):https://lists.fd.io/g/vpp-dev/message/12768 Mute This Topic:https://lists.fd.io/mt/31034762/675152 Group Owner:vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io> Unsubscribe:https://lists.fd.io/g/vpp-dev/unsub [fcoras.li...@gmail.com <mailto:fcoras.li...@gmail.com>] -=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12769):https://lists.fd.io/g/vpp-dev/message/12769 Mute This Topic:https://lists.fd.io/mt/31034762/675649 Group Owner:vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io> Unsubscribe:https://lists.fd.io/g/vpp-dev/unsub [e...@cisco.com <mailto:e...@cisco.com>] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12773): https://lists.fd.io/g/vpp-dev/message/12773 Mute This Topic: https://lists.fd.io/mt/31034762/1594641 Group Owner: vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [pvi...@vinciconsulting.com <mailto:pvi...@vinciconsulting.com>] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12775): https://lists.fd.io/g/vpp-dev/message/12775 Mute This Topic: https://lists.fd.io/mt/31034762/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 19.04 centos7 RPM package dependency errors
Dave and Ed, The Makefile has dependencies that work. However, you will need epel. The packages required are: yum install epel-release yum install mbedtls yum install python36 --Tom On 04/11/2019 05:11 PM, Florin Coras wrote: We do have it as a dependency because we want to make sure the plugin still builds. However, given that most of those who use tls use the openssl engine, we might consider not having mbedtls as a dependency for the packages that we push to packagecloud ... On a separate note, what centos do we run in the container? It seems that even python3 has some dependency errors. I guess that once we align the vagrant version with it, things should just work. Florin On Apr 11, 2019, at 1:55 PM, Ed Kern (ejk) <mailto:e...@cisco.com>> wrote: On Apr 11, 2019, at 2:22 PM, Florin Coras <mailto:fcoras.li...@gmail.com>> wrote: Are we building rpms on a host that has mbedtls installed? Yes the centos container has mbedtls installed….has for quite some time since it is a listed prerequisite straight out of the Makefile. Ed Just uninstalling it should disable the tlsmbedtls plugin, which is what we pretty much want. Florin On Apr 11, 2019, at 1:00 PM, Dave Wallace <mailto:dwallac...@gmail.com>> wrote: Tom/Billy, Do you know what the current status is with the VPP rpm's on master/19.04? I'm trying to install the VPP 19.04 packages frompackagecloud.io <http://packagecloud.io/>on a centos7 Vagrant/virtualbox VM (using .../vpp/extras/vagrant/Vagrantfile) to verify that the packages are correct. The 19.01 packages install fine, but the 19.04 and master packages fail with the following dependency errors: --> Finished Dependency Resolution Error: Package: vpp-plugins-19.04-rc1~b4.x86_64 (fdio_1904) Requires: libmbedtls.so.10()(64bit) Error: Package: vpp-devel-19.04-rc1~b4.x86_64 (fdio_1904) Requires: /usr/bin/python3 Error: Package: vpp-19.04-rc1~b4.x86_64 (fdio_1904) Requires: /usr/bin/python3 Error: Package: vpp-plugins-19.04-rc1~b4.x86_64 (fdio_1904) Requires: libmbedx509.so.0()(64bit) Error: Package: vpp-plugins-19.04-rc1~b4.x86_64 (fdio_1904) Requires: libmbedcrypto.so.2()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Thanks, -daw- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12768):https://lists.fd.io/g/vpp-dev/message/12768 Mute This Topic:https://lists.fd.io/mt/31034762/675152 Group Owner:vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io> Unsubscribe:https://lists.fd.io/g/vpp-dev/unsub [fcoras.li...@gmail.com <mailto:fcoras.li...@gmail.com>] -=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12769):https://lists.fd.io/g/vpp-dev/message/12769 Mute This Topic:https://lists.fd.io/mt/31034762/675649 Group Owner:vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io> Unsubscribe:https://lists.fd.io/g/vpp-dev/unsub [e...@cisco.com <mailto:e...@cisco.com>] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12773): https://lists.fd.io/g/vpp-dev/message/12773 Mute This Topic: https://lists.fd.io/mt/31034762/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] Use of cmake breaks builds in master https://gerrit.fd.io/r/#/c/18600/
On 04/01/2019 05:44 AM, Damjan Marion (damarion) wrote: On 31 Mar 2019, at 05:39, Thomas F Herbert <mailto:therb...@redhat.com>> wrote: Damjan, I attempted to fix a problem with use of cmake breaking CentOS builds with the patch introduced with the new rdma-core and quicly driver. I had this fixed with patch https://gerrit.fd.io/r/#/c/18600/ but it wouldn't rebase after another change with quicly. The patch no longer applies because the quickly.mk in gone and the problem appears after a patch of some upstream code. Could you please take a look at this: Submodule path 'deps/picotls': checked out '70cd2a60125729f6d6c32c2ace36403b2b6168e6' --- patching quicly f25b70d37f8974af9cc48a4a565d13a9cdc5fd75 Applying patch: 0001-cmake-install.patch patching file CMakeLists.txt patching file deps/picotls/CMakeLists.txt --- configuring quicly f25b70d37f8974af9cc48a4a565d13a9cdc5fd75 - log: /home/therbert/vpp/build-root/rpmbuild/vpp-19.04/build-root/build-vpp-native/external/quicly.config.log --- building quicly f25b70d37f8974af9cc48a4a565d13a9cdc5fd75 - log: /home/therbert/vpp/build-root/rpmbuild/vpp-19.04/build-root/build-vpp-native/external/quicly.build.log /bin/bash: cmake: command not found make[5]: *** [packages/quicly.mk:43: /home/therbert/vpp/build-root/rpmbuild/vpp-19.04/build-root/build-vpp-native/external/.quicly.build.ok] Error 127 Yes, i reverted quicly packaging changes as they need a bit of polishing so you need to rebase your patch. My patch is re-based but is this reversion you speak of merged yet? I don't see it on master? -- Damjan -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12683): https://lists.fd.io/g/vpp-dev/message/12683 Mute This Topic: https://lists.fd.io/mt/30840381/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] Use of cmake breaks builds in master https://gerrit.fd.io/r/#/c/18600/
Damjan, I attempted to fix a problem with use of cmake breaking CentOS builds with the patch introduced with the new rdma-core and quicly driver. I had this fixed with patch https://gerrit.fd.io/r/#/c/18600/ but it wouldn't rebase after another change with quicly. The patch no longer applies because the quickly.mk in gone and the problem appears after a patch of some upstream code. Could you please take a look at this: Submodule path 'deps/picotls': checked out '70cd2a60125729f6d6c32c2ace36403b2b6168e6' --- patching quicly f25b70d37f8974af9cc48a4a565d13a9cdc5fd75 Applying patch: 0001-cmake-install.patch patching file CMakeLists.txt patching file deps/picotls/CMakeLists.txt --- configuring quicly f25b70d37f8974af9cc48a4a565d13a9cdc5fd75 - log: /home/therbert/vpp/build-root/rpmbuild/vpp-19.04/build-root/build-vpp-native/external/quicly.config.log --- building quicly f25b70d37f8974af9cc48a4a565d13a9cdc5fd75 - log: /home/therbert/vpp/build-root/rpmbuild/vpp-19.04/build-root/build-vpp-native/external/quicly.build.log /bin/bash: cmake: command not found make[5]: *** [packages/quicly.mk:43: /home/therbert/vpp/build-root/rpmbuild/vpp-19.04/build-root/build-vpp-native/external/.quicly.build.ok] Error 127 Thanks, --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12679): https://lists.fd.io/g/vpp-dev/message/12679 Mute This Topic: https://lists.fd.io/mt/30840381/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] Mellanox dependency changes
+Artem +vpp-dev On 03/27/2019 11:22 AM, Sirshak Das wrote: Hi Thomas Is this the patch under consideration ? https://gerrit.fd.io/r/#/c/18521/ So will this make mlx4/5 dpdk compilation default ? What about MOFED dependencies (Kernel Modules and all userspace verb libraries) ? With regard to CentOS, necessary kmods are loaded when rdma-core rpm is loaded, I heard its all now Upstreamed in Kernel but that’s post 4.20, so how would that work for distros with kernel version lower and MOFED uninstalled (ubuntu 18.04). I don't know the solution for Ubuntu 1604. There is no OFED required for CentOS7.6. CentOS7.6: This is the good news resolved for CentOS 7.6 and I have verified for 19.01 with patch above on CNCF packet.net infrastructure. Ubuntu1604: For Ubuntu, 1604 there is still have a problem: https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/18353/console ... *21:27:39* /w/workspace/vpp-verify-master-ubuntu1604/build/external/deb/_build/dpdk-19.02/drivers/net/mlx5/mlx5_mr.h:19:31: fatal error: infiniband/mlx5dv.h: No such file or directory *21:27:39* compilation terminated. Artem's patch, https://gerrit.fd.io/r/#/c/18199/ Also fails for Ubuntu1604 Ubuntu1804: Seems to be buiding: https://jenkins.fd.io/job/vpp-beta-verify-master-ubuntu1804/6150/ Thank you ++ Sirshak Das IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12651): https://lists.fd.io/g/vpp-dev/message/12651 Mute This Topic: https://lists.fd.io/mt/30795618/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] Build failure question
On 03/05/2019 09:40 AM, Damjan Marion wrote: On 5 Mar 2019, at 15:14, Thomas F Herbert <mailto:therb...@redhat.com>> wrote: On 03/05/2019 02:37 AM, Damjan Marion wrote: On 4 Mar 2019, at 22:52, Thomas F Herbert <mailto:therb...@redhat.com>> wrote: Damjan et. al. I get build failures when builging from a tarball outside of git tree on 19.01 I documented this in https://jira.fd.io/browse/VPP-1577 This is not reproduceable when building in git tree. Could you please take a look at the cmake output and give me some suggestions. —Tom It is likely fixed in master, please try with master. Yes, I believe it is fixed in master. Do you know which commit fixed it? May be: Yes, Thanks! I found it and backported the patch and am testing it. I had already found the problem with pack.cmake but missed the version include changes. I will update JIRA 1577 with results in case we decide to backport it. Author: Damjan Marion mailto:damar...@cisco.com>> AuthorDate: Mon Jan 28 17:55:59 2019 +0100 Commit: Marco Varlese <mailto:marco.varl...@suse.de>> CommitDate: Tue Jan 29 07:47:01 2019 + cmake: fix out-of-git-tree build Change-Id: Ib94637ec09799c23f3179599b54a2be6e2768425 Signed-off-by: Damjan Marion <mailto:damar...@cisco.com>> -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12436): https://lists.fd.io/g/vpp-dev/message/12436 Mute This Topic: https://lists.fd.io/mt/30219549/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] Build failure question
On 03/05/2019 02:37 AM, Damjan Marion wrote: On 4 Mar 2019, at 22:52, Thomas F Herbert <mailto:therb...@redhat.com>> wrote: Damjan et. al. I get build failures when builging from a tarball outside of git tree on 19.01 I documented this in https://jira.fd.io/browse/VPP-1577 This is not reproduceable when building in git tree. Could you please take a look at the cmake output and give me some suggestions. —Tom It is likely fixed in master, please try with master. Yes, I believe it is fixed in master. Do you know which commit fixed it? -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12434): https://lists.fd.io/g/vpp-dev/message/12434 Mute This Topic: https://lists.fd.io/mt/30219549/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] Build failure question
On 03/04/2019 05:12 PM, Paul Vinciguerra wrote: Is this a “must have” or a “nice to have” feature? I guess what I’m really asking is if this belongs in a CI job. This breaks the building of downstream RPMs for CentOS. Until the 1807 release, we have been maintaining this feature. The downstream RPMs are built from a spec file and tarball created by the dist target in the top level Makefile I am trying to write a patch to fix it. It would be preferable to have the patch backported but for now, I am looking for help from CMake experts to see what is causing this side affect. Paul On Mar 4, 2019, at 4:52 PM, Thomas F Herbert <mailto:therb...@redhat.com>> wrote: Damjan et. al. I get build failures when builging from a tarball outside of git tree on 19.01 I documented this in https://jira.fd.io/browse/VPP-1577 This is not reproduceable when building in git tree. Could you please take a look at the cmake output and give me some suggestions. --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12423): https://lists.fd.io/g/vpp-dev/message/12423 Mute This Topic: https://lists.fd.io/mt/30219549/1594641 Group Owner: vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [pvi...@vinciconsulting.com <mailto:pvi...@vinciconsulting.com>] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12425): https://lists.fd.io/g/vpp-dev/message/12425 Mute This Topic: https://lists.fd.io/mt/30219549/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] Build failure question
Damjan et. al. I get build failures when builging from a tarball outside of git tree on 19.01 I documented this in https://jira.fd.io/browse/VPP-1577 This is not reproduceable when building in git tree. Could you please take a look at the cmake output and give me some suggestions. --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12423): https://lists.fd.io/g/vpp-dev/message/12423 Mute This Topic: https://lists.fd.io/mt/30219549/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] Status of vpp 19.01 in CentOS distribution
Jerome and VPP community: This is the status of vpp release packages in CentOS. There are no upstream issues or build issues. The current status is that some of the dependent packages required for building vpp were not tagged properly for the CentOS build system buildroot. As soon as that is resolved, we will push vpp 19.01 release packages to the mirrors. ETA should be end of February or the beginning of March. --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12291): https://lists.fd.io/g/vpp-dev/message/12291 Mute This Topic: https://lists.fd.io/mt/29930611/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] Build failing on Fedora
I just verified with top of master that vpp builds fine on Fedora 28. As for the current Centos release 7.5, you must install epel as below which is not explicitly in build dependencies. yum install epel-release On 11/26/2018 01:57 PM, Jim Thompson wrote: On Nov 26, 2018, at 12:05 PM, Burt Silverman <mailto:bur...@gmail.com>> wrote: Hi Ed, Thank you for looking at my change, and I apologize for some laziness -- I should have made it more clear that I was only doing part of the job -- not adding the needed ifeq's so that this Fedora stuff would be isolated from other platforms. I leave it to somebody else to finish the job. Ouch, even the line I was most proud of has a glitch: + @sudo -E dnf debuginfo-install $(CONFIRM) glibc openssl-libs mbedtls-devel zlib openssl-libs I did not mean to add openssl-libs at the end (it already shows earlier in the line). The main goody (for Fedora) is that "dnf debuginfo-install" as opposed to simply "debuginfo-install" made an error disappear. The latter fails in an ungraceful fashion; I have not looked into that very deeply. Burt I’ve been dealing with this by installing epel. Fresh minimal 7.5 install on top of QEMU on a Mac (thanks to Damjan for pointing out that the newest QEMU uses hypervisor.framework!) https://gist.github.com/gonzopancho/4091e160f2cb86c0a94674b554ff#file-gistfile1-txt-L889-L890 https://gist.github.com/gonzopancho/4091e160f2cb86c0a94674b554ff#file-gistfile1-txt-L3995-L4254 And was about to write vpp-dev about same. So do we want epel here, and thus cmake3? Jim -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11416): https://lists.fd.io/g/vpp-dev/message/11416 Mute This Topic: https://lists.fd.io/mt/28281426/675058 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [therb...@redhat.com] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11418): https://lists.fd.io/g/vpp-dev/message/11418 Mute This Topic: https://lists.fd.io/mt/28281426/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] Build failing on Fedora
It is set to cmake3 cmake isn't available in Centos but cmake3 is. We should patch Makefile so Fedora dep is cmake but Centos/RHEL is cmake3. I will work on a fix. --Tom On 11/26/2018 01:57 PM, Jim Thompson wrote: On Nov 26, 2018, at 12:05 PM, Burt Silverman <mailto:bur...@gmail.com>> wrote: Hi Ed, Thank you for looking at my change, and I apologize for some laziness -- I should have made it more clear that I was only doing part of the job -- not adding the needed ifeq's so that this Fedora stuff would be isolated from other platforms. I leave it to somebody else to finish the job. Ouch, even the line I was most proud of has a glitch: + @sudo -E dnf debuginfo-install $(CONFIRM) glibc openssl-libs mbedtls-devel zlib openssl-libs I did not mean to add openssl-libs at the end (it already shows earlier in the line). The main goody (for Fedora) is that "dnf debuginfo-install" as opposed to simply "debuginfo-install" made an error disappear. The latter fails in an ungraceful fashion; I have not looked into that very deeply. Burt I’ve been dealing with this by installing epel. Fresh minimal 7.5 install on top of QEMU on a Mac (thanks to Damjan for pointing out that the newest QEMU uses hypervisor.framework!) https://gist.github.com/gonzopancho/4091e160f2cb86c0a94674b554ff#file-gistfile1-txt-L889-L890 https://gist.github.com/gonzopancho/4091e160f2cb86c0a94674b554ff#file-gistfile1-txt-L3995-L4254 And was about to write vpp-dev about same. So do we want epel here, and thus cmake3? Jim -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11416): https://lists.fd.io/g/vpp-dev/message/11416 Mute This Topic: https://lists.fd.io/mt/28281426/675058 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [therb...@redhat.com] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11417): https://lists.fd.io/g/vpp-dev/message/11417 Mute This Topic: https://lists.fd.io/mt/28281426/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 18.07.1 RPM release packages available in Centos
All, 18.07.1 release packages are in Centos mirrors. To install Centos update release packages of VPP on a Centos, install the Centos NFV SIG yum repo and then install vpp as follows. yum install centos-release-fdio yum install vpp* If already installed, yum update --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10731): https://lists.fd.io/g/vpp-dev/message/10731 Mute This Topic: https://lists.fd.io/mt/26654231/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 18.07 RPM release packages available in Centos
Jerome, 18.07 release packages are in Centos mirrors. To install Centos release packages of VPP on a Centos, install the Centos NFV SIG yum repo and then install vpp as follows. yum install centos-release-fdio yum install vpp* --Tom On 05/23/2018 10:32 AM, Jerome Tollet (jtollet) wrote: Hey Thomas, Can you let us know what you are planning to do for next releases? Are you manually building those RPMs or will you automatically include bugfix versions as well as future versions (e.g. 18.07)? Jerome On 5/21/2018 12:24 PM, Thomas F Herbert wrote: VPP 18.04 RPMs are available in the Centos mirrors by way of the Centos NFV SIG. From an updated Centos: To install VPP on a Centos host, intall the Centos NFV SIG yum repo and then install vpp as follows. yum install centos-release-fdio yum install vpp* --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* _._,_._,_ Links: You receive all messages sent to this group. View/Reply Online (#9338)<https://lists.fd.io/g/vpp-dev/message/9338>| Reply To Sender<mailto:dwallac...@gmail.com?subject=Private:%20Re:%20Re%3A%20%5Bvpp-dev%5D%20VPP%20RPMs%20available%20in%20Centos>| Reply To Group<mailto:vpp-dev@lists.fd.io?subject=Re:%20Re%3A%20%5Bvpp-dev%5D%20VPP%20RPMs%20available%20in%20Centos>| Mute This Topic<https://lists.fd.io/mt/19673150/675291>| New Topic<https://lists.fd.io/g/vpp-dev/post> Change Your Subscription<https://lists.fd.io/g/vpp-dev/editsub/675291> Group Home<https://lists.fd.io/g/vpp-dev> Contact Group Owner<mailto:vpp-dev+ow...@lists.fd.io> Terms Of Service<https://lists.fd.io/static/tos> Unsubscribe From This Group<https://lists.fd.io/g/vpp-dev/unsub> _._,_._,_ -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10492): https://lists.fd.io/g/vpp-dev/message/10492 Mute This Topic: https://lists.fd.io/mt/25646023/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] IRC SPAM
On 08/22/2018 09:14 PM, Burt Silverman wrote: That pidgin client is totally bizarre. For hours it would not cooperate regardless of what I told it. When it decided to cooperate, then even if I removed my password information, it still let me log in without shunting me to the land of undesirables. Meanwhile, I found the hidden trick to make the webchat interface work. Weird. Another note about pidgin: I find it reconnects only on startup particularly with many simultaneous chats! If you lose your network connection, you restart the app or kill -9 the pidgin process. Set all chats for persistence and auto re-connect. I think it has trouble restarting many tcp connections simultaneously because of backoff. See my email elsewhere on this chain about settings. Burt On Wed, Aug 22, 2018 at 2:39 PM, Thomas F Herbert <mailto:therb...@redhat.com>> wrote: On 08/22/2018 02:01 PM, Burt Silverman wrote: I registered and verified, but when I try to log in I always go to the unregistered area. How do I log in now? The instructions are pretty useless for a non SASL client user. I can only tell you my settings for irc. Hopefully it will help. I use pidgin client. I log on with my username and password and it is set for SSL, and authenticates with SASL. I connect to irc.freenode.net <http://irc.freenode.net> Burt On Wed, Aug 22, 2018 at 12:49 PM, Vanessa Valderrama mailto:vvalderr...@linuxfoundation.org>> wrote: In effort to prevent IRC SPAM we are requiring registration in the FD.io channels. * The following channels will require registration to join the channel o https://wiki.fd.io/view/IRC * Please follow these steps to register on Freenode o https://freenode.net/kb/answer/registration <https://freenode.net/kb/answer/registration> Thank you, Vanessa -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10257): https://lists.fd.io/g/vpp-dev/message/10257 <https://lists.fd.io/g/vpp-dev/message/10257> Mute This Topic: https://lists.fd.io/mt/24921658/541103 <https://lists.fd.io/mt/24921658/541103> Group Owner: vpp-dev+ow...@lists.fd.io <mailto:vpp-dev%2bow...@lists.fd.io> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub <https://lists.fd.io/g/vpp-dev/unsub> [bur...@gmail.com <mailto:bur...@gmail.com>] -=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10259):https://lists.fd.io/g/vpp-dev/message/10259 <https://lists.fd.io/g/vpp-dev/message/10259> Mute This Topic:https://lists.fd.io/mt/24921658/675058 <https://lists.fd.io/mt/24921658/675058> Group Owner:vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io> Unsubscribe:https://lists.fd.io/g/vpp-dev/unsub <https://lists.fd.io/g/vpp-dev/unsub> [therb...@redhat.com <mailto:therb...@redhat.com>] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10260): https://lists.fd.io/g/vpp-dev/message/10260 <https://lists.fd.io/g/vpp-dev/message/10260> Mute This Topic: https://lists.fd.io/mt/24921658/541103 <https://lists.fd.io/mt/24921658/541103> Group Owner: vpp-dev+ow...@lists.fd.io <mailto:vpp-dev%2bow...@lists.fd.io> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub <https://lists.fd.io/g/vpp-dev/unsub> [bur...@gmail.com <mailto:bur...@gmail.com>] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10281): https://lists.fd.io/g/vpp-dev/message/10281 Mute This Topic: https://lists.fd.io/mt/24921658/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] IRC SPAM
See below: On 08/23/2018 03:49 PM, Burt Silverman wrote: Hi Tom, Although I don't need to use pidgin, my obsessive gene has kicked in: the idea that it should work reliably, but does not for me -- can you give a complete list of the connection settings -- the Basic and the Advanced Settings -- perhaps with some commentary? Anyway, it seems that some things get "cached" so that if one tries to put in good settings after using bad settings -- it may not work out. I have tried it on Windows and on Ubuntu. I guess it temporarily worked on Windows; I have no idea why. Thanks, Tom. These are my settings. Caveat: I have no idea about using a web client as I don't use it. Also, there may be differences among clients as I use pidgin and have been for some time on Fedora and previously on a Mac but I don't remember the Mac version. Version: 2.13.0-1.fc27.x86_64 Protocol: IRC Username <...yours...> Server irc.freenode.net Password <...yours...> Port: 6697 Use SSL Authenticate with SASL Burt On Thu, Aug 23, 2018 at 11:36 AM, Thomas F Herbert mailto:therb...@redhat.com>> wrote: More on using IRC... One of our colleagues had some trouble connecting today. I think we figured out that since freenode IRC now requires everyone to authenticate and you are logging in with passwd authentication, you have to connect through SSL but not all of the old ports will work with SSL. Mine works consistently on port 6697 with SSL. Some folks were using legacy ports that no longer will work. I use Pidgin so I have no idea how this will affect those using the web client. --Tom On 08/22/2018 02:39 PM, Thomas F Herbert wrote: On 08/22/2018 02:01 PM, Burt Silverman wrote: I registered and verified, but when I try to log in I always go to the unregistered area. How do I log in now? The instructions are pretty useless for a non SASL client user. I can only tell you my settings for irc. Hopefully it will help. I use pidgin client. I log on with my username and password and it is set for SSL, and authenticates with SASL. I connect to irc.freenode.net <http://irc.freenode.net> Burt On Wed, Aug 22, 2018 at 12:49 PM, Vanessa Valderrama mailto:vvalderr...@linuxfoundation.org>> wrote: In effort to prevent IRC SPAM we are requiring registration in the FD.io channels. * The following channels will require registration to join the channel o https://wiki.fd.io/view/IRC * Please follow these steps to register on Freenode o https://freenode.net/kb/answer/registration <https://freenode.net/kb/answer/registration> Thank you, Vanessa -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10257): https://lists.fd.io/g/vpp-dev/message/10257 <https://lists.fd.io/g/vpp-dev/message/10257> Mute This Topic: https://lists.fd.io/mt/24921658/541103 <https://lists.fd.io/mt/24921658/541103> Group Owner: vpp-dev+ow...@lists.fd.io <mailto:vpp-dev%2bow...@lists.fd.io> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub <https://lists.fd.io/g/vpp-dev/unsub> [bur...@gmail.com <mailto:bur...@gmail.com>] -=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10259):https://lists.fd.io/g/vpp-dev/message/10259 <https://lists.fd.io/g/vpp-dev/message/10259> Mute This Topic:https://lists.fd.io/mt/24921658/675058 <https://lists.fd.io/mt/24921658/675058> Group Owner:vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io> Unsubscribe:https://lists.fd.io/g/vpp-dev/unsub <https://lists.fd.io/g/vpp-dev/unsub> [therb...@redhat.com <mailto:therb...@redhat.com>] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10260):https://lists.fd.io/g/vpp-dev/message/10260 <https://lists.fd.io/g/vpp-dev/message/10260> Mute This Topic:https://lists.fd.io/mt/24921658/675058 <https://lists.fd.io/mt/24921658/675058> Group Owner:vpp-dev+ow...@lists.fd.io <mailto:vpp-dev+ow...@lists.fd.io> Unsubscribe:https://lists.fd.io/g/vpp-dev/unsub <https://lists.fd.io/g/vpp-dev/unsub> [therb...@redhat.com <mailto:therb...@redhat.com>] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this
Re: [vpp-dev] IRC SPAM
More on using IRC... One of our colleagues had some trouble connecting today. I think we figured out that since freenode IRC now requires everyone to authenticate and you are logging in with passwd authentication, you have to connect through SSL but not all of the old ports will work with SSL. Mine works consistently on port 6697 with SSL. Some folks were using legacy ports that no longer will work. I use Pidgin so I have no idea how this will affect those using the web client. --Tom On 08/22/2018 02:39 PM, Thomas F Herbert wrote: On 08/22/2018 02:01 PM, Burt Silverman wrote: I registered and verified, but when I try to log in I always go to the unregistered area. How do I log in now? The instructions are pretty useless for a non SASL client user. I can only tell you my settings for irc. Hopefully it will help. I use pidgin client. I log on with my username and password and it is set for SSL, and authenticates with SASL. I connect to irc.freenode.net Burt On Wed, Aug 22, 2018 at 12:49 PM, Vanessa Valderrama <mailto:vvalderr...@linuxfoundation.org>> wrote: In effort to prevent IRC SPAM we are requiring registration in the FD.io channels. * The following channels will require registration to join the channel o https://wiki.fd.io/view/IRC * Please follow these steps to register on Freenode o https://freenode.net/kb/answer/registration <https://freenode.net/kb/answer/registration> Thank you, Vanessa -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10257): https://lists.fd.io/g/vpp-dev/message/10257 <https://lists.fd.io/g/vpp-dev/message/10257> Mute This Topic: https://lists.fd.io/mt/24921658/541103 <https://lists.fd.io/mt/24921658/541103> Group Owner: vpp-dev+ow...@lists.fd.io <mailto:vpp-dev%2bow...@lists.fd.io> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub <https://lists.fd.io/g/vpp-dev/unsub> [bur...@gmail.com <mailto:bur...@gmail.com>] -=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10259):https://lists.fd.io/g/vpp-dev/message/10259 Mute This Topic:https://lists.fd.io/mt/24921658/675058 Group Owner:vpp-dev+ow...@lists.fd.io Unsubscribe:https://lists.fd.io/g/vpp-dev/unsub [therb...@redhat.com] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10260): https://lists.fd.io/g/vpp-dev/message/10260 Mute This Topic: https://lists.fd.io/mt/24921658/675058 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [therb...@redhat.com] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10271): https://lists.fd.io/g/vpp-dev/message/10271 Mute This Topic: https://lists.fd.io/mt/24921658/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] IRC SPAM
On 08/22/2018 02:01 PM, Burt Silverman wrote: I registered and verified, but when I try to log in I always go to the unregistered area. How do I log in now? The instructions are pretty useless for a non SASL client user. I can only tell you my settings for irc. Hopefully it will help. I use pidgin client. I log on with my username and password and it is set for SSL, and authenticates with SASL. I connect to irc.freenode.net Burt On Wed, Aug 22, 2018 at 12:49 PM, Vanessa Valderrama <mailto:vvalderr...@linuxfoundation.org>> wrote: In effort to prevent IRC SPAM we are requiring registration in the FD.io channels. * The following channels will require registration to join the channel o https://wiki.fd.io/view/IRC * Please follow these steps to register on Freenode o https://freenode.net/kb/answer/registration <https://freenode.net/kb/answer/registration> Thank you, Vanessa -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10257): https://lists.fd.io/g/vpp-dev/message/10257 <https://lists.fd.io/g/vpp-dev/message/10257> Mute This Topic: https://lists.fd.io/mt/24921658/541103 <https://lists.fd.io/mt/24921658/541103> Group Owner: vpp-dev+ow...@lists.fd.io <mailto:vpp-dev%2bow...@lists.fd.io> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub <https://lists.fd.io/g/vpp-dev/unsub> [bur...@gmail.com <mailto:bur...@gmail.com>] -=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10259): https://lists.fd.io/g/vpp-dev/message/10259 Mute This Topic: https://lists.fd.io/mt/24921658/675058 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [therb...@redhat.com] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10260): https://lists.fd.io/g/vpp-dev/message/10260 Mute This Topic: https://lists.fd.io/mt/24921658/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] Destination Options processing in VPP
+ Daniel Voyer +Daniel Bernier On 08/21/2018 12:24 PM, Damjan Marion via Lists.Fd.Io wrote: Hi Tom and welcome to vpp-dev, On 21 Aug 2018, at 16:28, Tom Herbert wrote: Hello, I have some questions regarding Destination Options processing in VPP. Basically, I'd like to know they are properly supported per RFC8200. Probably not. I not, then I'd like to request the VPP stack is fixed to be protocol compliant in this. We do have SRV6 support. Are you saying from your code inspection that we have a non-compliance issue with RFC8200 or are you claiming a non-compliance issue with current segment routing drafts. Also, if this is a non-compliance issue, to your knowledge, has this been verified with testing? As you know VPP is open source project, we like to be standards compliant and we like new features. Showing up on the mailing list first time and immediately requesting somebody to do the work is a bit unfair. I'm sure people will try to help if you or somebody who works with you wants to work on this problem, but you cannot expect that folks will just stop doing what they do just to do the work you requested. Thanks, Damjan -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10242): https://lists.fd.io/g/vpp-dev/message/10242 Mute This Topic: https://lists.fd.io/mt/24877418/675058 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [therb...@redhat.com] -=-=-=-=-=-=-=-=-=-=-=- -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10246): https://lists.fd.io/g/vpp-dev/message/10246 Mute This Topic: https://lists.fd.io/mt/24877418/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] dpdk shared libraries
On 06/04/2018 09:28 AM, Damjan Marion (damarion) wrote: Dear Thomas, That should be doable today, as long as VPP version supports version of dpdk you want to link against. From the spec file you can invoke autotools project directly, and pass --enable-dpdk-shared to ./configure ./configure --enable-dpdk-shared --prefix=/wherever/rpm/spec/file/wants/files/to/show/up make make install I don't expect any perf difference, but the open question is how the distro dpdk libs deal with different vector optimisations I assume you are speaking of AVX? It looks like upstream DPDK (default settings) and the fedora RPM both have AVX2 enabled but not AVX512. I think that is consistent of what we do in VPP when we compile dpdk. -- Damjan On 4 Jun 2018, at 13:51, Thomas F Herbert <mailto:therb...@redhat.com>> wrote: OVS as of 9.x now uses shared libraries with dpdk packaged separately for downstream I want to raise the issue of shared vs. static libraries for dpdk in vpp. Would there be any performance penalty to going with shared? --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*
[vpp-dev] dpdk shared libraries
OVS as of 9.x now uses shared libraries with dpdk packaged separately for downstream I want to raise the issue of shared vs. static libraries for dpdk in vpp. Would there be any performance penalty to going with shared? --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*
Re: [vpp-dev] VPP RPMs available in Centos
Jerome, Currently, it is a manual process but not a terribly time intensive one. 18.04 and 18.01.1 are in the mirrors now. 18.01.2 within a week. 18.07 will require a minor bug fix in Centos infra with anticipated for Centos 7.5 hopefully before vpp 18.07 release date. --Tom On 05/23/2018 10:32 AM, Jerome Tollet (jtollet) wrote: Hey Thomas, Can you let us know what you are planning to do for next releases? Are you manually building those RPMs or will you automatically include bugfix versions as well as future versions (e.g. 18.07)? Jerome On 5/21/2018 12:24 PM, Thomas F Herbert wrote: VPP 18.04 RPMs are available in the Centos mirrors by way of the Centos NFV SIG. From an updated Centos: To install VPP on a Centos host, intall the Centos NFV SIG yum repo and then install vpp as follows. yum install centos-release-fdio yum install vpp* --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*
Re: [vpp-dev] git.fd.io not updating
I noticed this with an attempted git pull. The ECDSA host key for [gerrit.fd.io]:29418 has changed, Surrounded by nasty warnings. On 05/22/2018 02:58 AM, Marco Varlese wrote: Roughly a week ago, I noticed there was a DNS/IP change when cloning a new VPP repo... I wonder if what I saw is somehow connected to this issue. On Mon, 2018-05-21 at 16:34 -0700, Florin Coras wrote: Hi, It would seem that git.fd.io <http://git.fd.io> [1] thinks that we last committed a patch to vpp almost 1 week ago. Any idea what might’ve triggered this? Thanks, Florin [1] https://git.fd.io/vpp/log/ -- Marco V SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*
[vpp-dev] VPP RPMs available in Centos
VPP 18.04 RPMs are available in the Centos mirrors by way of the Centos NFV SIG. From an updated Centos: To install VPP on a Centos host, intall the Centos NFV SIG yum repo and then install vpp as follows. yum install centos-release-fdio yum install vpp* --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*
Re: [vpp-dev] Patches for 18.04
Chris and John Thanks. will do. --Tom On 04/06/2018 03:53 PM, Chris Luke wrote: You can cherry pick them to the stable branch, though preferably with a Jira ID in the first line (you can amend the commit message after you cherry pick it). Chris. *From:*vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> *On Behalf Of *Thomas F Herbert *Sent:* Friday, April 6, 2018 14:38 *To:* vpp-dev@lists.fd.io *Cc:* vpp-dev <vpp-dev@lists.fd.io>; Billy McFall <bmcf...@redhat.com> *Subject:* [vpp-dev] Patches for 18.04 Chris, I submitted two patches to master that should be in stable/18.04. 11556: Merged in Master: https://gerrit.fd.io/r/11556 11551: Submitted but not merged yet in master: https://gerrit.fd.io/r/11551 <https://gerrit.fd.io/r/11551> What should I do? Should I resubmit both patches direct to stable/18.04? --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*
Re: [vpp-dev] What RPM contains vpp debug symbols?
Yichen, Sorry it took me a long time to respond. debuginfo rpms were not produced for 17.10 and 18.01 because of a side affect of a "fix" to work around a problem with rpmbuild. The plan is to restore the building of debuginfo rpms in 18.04 and subsequent releases. This is documented in https://jira.fd.io/browse/VPP-1227 --Tom On 04/02/2018 02:21 PM, Yichen Wang wrote: Hi, Thomas, Just want to revive this thread… Do we know when can we have this fixed? We are testing and will likely to ship with VPP 18.04 once the final release comes out. Having the debuginfo RPM is **very** important in our product, as it will give clues when VPP crashes. Given it has been broken for 6months+, we would really need your helps so that we have the debuginfo RPM before we finalize our code. Thanks very much! Regards, Yichen *From: *Dave Wallace <dwallac...@gmail.com> *Date: *Thursday, January 25, 2018 at 8:20 PM *To: *Billy McFall <bmcf...@redhat.com> *Cc: *"vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>, "Yichen Wang (yicwang)" <yicw...@cisco.com> *Subject: *Re: [vpp-dev] What RPM contains vpp debug symbols? Thanks for the info Billy! -daw- On 1/25/18 8:26 PM, Billy McFall wrote: 'make pkg-rpm' is currently not generating an RPM with debug symbols. There is a bug in rpmbuild for packages with short names (i.e. - vpp) that was not allowing RPMs to be built upstream in CentOS and RHEL. The work around is to add a -0 to the package name to make it long enough. Much later after this change was merged, it was discovered that the debug RPM was not being built. Thomas Herbert is tracking the issue. rpmbuild has been fixed in Fedora but that fix has not been pulled into CentOS or RHEL. Not sure when it will make it. Thomas can give more details, I am just regurgitating what he previously reported to me. Billy McFall On Thu, Jan 25, 2018 at 6:57 PM, Dave Wallace <dwallac...@gmail.com<mailto:dwallac...@gmail.com>> wrote: Does anyone know what RPM contains debug symbols? Back in VPP 17.07 there used to be an RPM package called vpp-debuginfo-*.x86_64.rpm, but that package is no longer installed on nexus.fd.io<http://nexus.fd.io>starting with release 17.10 https://nexus.fd.io/content/repositories/fd.io.stable.1707.centos7/io/fd/vpp/vpp-debuginfo/17.07.01-release.x86_64/vpp-debuginfo-17.07.01-release.x86_64.rpm Thanks, -daw- ___ vpp-dev mailing list vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> https://lists.fd.io/mailman/listinfo/vpp-dev -- *Billy McFall* Networking Group CTO Office *Red Hat* -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*
[vpp-dev] Patches for 18.04
Chris, I submitted two patches to master that should be in stable/18.04. 11556: Merged in Master: https://gerrit.fd.io/r/11556 11551: Submitted but not merged yet in master: https://gerrit.fd.io/r/11551 What should I do? Should I resubmit both patches direct to stable/18.04? --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*
Re: [vpp-dev] Sad News from Intel - Venky Venkatesan
Jim, Thanks for letting us know. I am very sorry to hear about Venky's passing. --Tom On 04/05/2018 02:36 PM, St Leger, Jim wrote: Several of you have already heard the very sad news of the passing of our dear friend and colleague Venky. He was “Mr. DPDK” to many, a nod to his invention and creation of DPDK about ten years ago (before it was called DPDK.) Of course his footprints across the industry and literally across the globe are everywhere. If you know what ATCA is, well, Venky had his hands and inventions deeply into the creation of that PICMG spec and many of the first revision products. He touched on and gave guidance to projects spanning Linux/netdev, DPDK, Intel QuickAssist Technology, BSD stacks, OVS, OPNFV, FD.io, all-things-virtualization (KVM, Xen, VMware, Hyper-V, etc.), ETSI, IETF, containers, and so many other arenas that my brain can’t remember at this dark moment. If you knew him and engaged him, especially on deep technical discussions, you knew you were talking to someone with the rare combination of skills that went incredibly deep both on the hardware, silicon side of platforms but also on the software, networking side of the platforms. Rarely did I find a topic that Venky wasn’t well versed on. And by “topic” I mean everything from football to photography to history to politics and many other subjects well beyond the technical realm our day jobs find us in. Conversations with Venky were a treat. Traveling with him was an adventure. Debating with him was a lesson. I will so miss all of him. Below are some details on a memorial service this Sunday in Oregon and also a GoFundMe page. If you’re in Oregon or close by please join the service. Venky left behind a wife, Priya, and two young girls, Adhiti and Namrata. While I’m sure they are overwhelmed with sadness and grief at the moment they can use our support. Please consider supporting the GoFundMe memorial fund for his family. Lastly, my network extends through this distribution list. But Venky’s network was one hundred times broader. Please share this sad news through your own networks. Thanks, Jim *From:* A message from Sandra Rivera *Sent:* Thursday, April 5, 2018 10:58 AM *Subject:* Follow-up: A loss for our NPG organization All, We have an update on the memorial service plans in celebration of Venky Venkatesan’s life. The service will be held on Sunday, April 8^th at our Jones Farm Conference Center (JFCC) in Hillsboro, OR from 2-4PM, and is open to all who would like to join. Venky’s family will plan to attend, as well as friends and others who have worked closely with him over the years.Please note that this is not an Intel-sponsored event and therefore any travel or expenses related to attending need to be managed personally. Many of you have asked about donations, and we have helped setup a GoFundMe account for his family which will be used to fund scholarships for his children. https://www.gofundme.com/venky-venkatesan-memorial-fund If you have any questions about the service, please contact *Udayan Mukherjee*. Thank you all very much for your support during this difficult time. Sandra ** *From:* A message from Sandra Rivera *Sent:* Tuesday, April 3, 2018 9:34 PM *Subject:* A loss for our NPG organization To All, Today is a very sad day for our NPG team and Intel. Our dear friend and colleague, Venky Venkatesan, passed away early morning today after a tough battle with cancer. Aside from his deep contributions to the organization, Venky provided technical mentorship to many employees and greatly impacted our technical leadership pipeline. On a personal level, Venky was very dedicated to his family and also cared deeply about mentoring the next generation of engineers and scientists through efforts like coaching robotics teams and providing guidance to many interns and Intel employees. His passion, dedication and commitment to this organization, Intel, and the external community will be greatly missed. We will let you know as soon as more information is available for Venky’s memorial/celebration service. Sandra -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*
[vpp-dev] mbedtls in 18.04
WRT mbedtls: This issue was raised in a vpp meeting a few weeks ago. There was some discussion of making mbedtls package optional instead of a hard dependency for tls. Did we reach consensus on the mbedtls requirement one way or the other? Billy and I are preparing for 18.04 for Centos and RHEL. mbedtls is in Fedora/EPEL but not in RHEL and Centos and creates problems for us for these distros. If the consensus is to leave mbedtls as a hard requirement upstream, we could carry a patch in the downstream packaging for release 18.04 but we would prefer to have as few deviations as possible from upstream packaging. --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*
[vpp-dev] subunit requirement
Garbriel and all, I am working on the release packaging for 18.01.1 for Centos. I want to discuss the subunit requirement in deps and in the spec file originally introduced in this patch. https://gerrit.fd.io/r/gitweb?p=vpp.git;a=commitdiff;h=d3e671e0dbb879d90f00bdee608ee0bb5f6357ae Although subunit is in Fedora (and EPEL), it is not available in Centos so the subunit requirement breaks release builds for Centos. The following patch was merged in October and cherry-picked into 1710 which made this requirement Fedora only. e41289115ffb24d95a5d0bc2ef33001d06a28688 Subsequently in this commit b8bbd6521fbab6579e4c571f61489f995f56bc78, it was made a requirement for Centos as well. I want to propose an upstream patch to remove the subunit requirement for Centos but I should check with everyone as to the implications. --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*
Re: [vpp-dev] vpp-comparison-18.01 - Invitation to comment
nd. One thing that stands out to me is that VPP in general has much higher variability between the recorded samples than OVS (the exception being tests where OVS scored very low; the variability there is quite high since small differences between each sample are magnified). The general trend is that VPP variability is increasing at 1M flows and it's a bit mixed at 256 and 10K flows. Open in Sheets <https://docs.google.com/spreadsheets/d/1jFoQZieTT93xikWcjZU08J1kF6qn_tjTTC0A3mu0yyo/edit?usp=sharing_eip=5a78b247> Google Sheets: Create and edit spreadsheets online. Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA <https://maps.google.com/?q=1600+Amphitheatre+Parkway,+Mountain+View,+CA+94043,+USA=gmail=g> You have received this email because someone shared a spreadsheet with you from Google Sheets.Logo for Google Sheets <https://drive.google.com> -- *Billy McFall* Networking Group CTO Office *Red Hat* -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*
Re: [vpp-dev] [csit-dev] t4-virl3 moved from testing back into production - SSH timouts on VIRL
tup VPP PIDs: {'10.30.53.219': 23424, '10.30.53.218': 5433} *02:03:23.456*Test Teardown VPP PIDs: None *02:03:23.458*| FAIL | *02:03:23.458*Expected error 'ICMP echo Rx timeout' but got 'NoValidConnectionsError: [Errno None] Unable to connect to port 22 on or 10.30.53.220'. https://jenkins.fd.io/job/csit-vpp-functional-1801-ubuntu1604-virl/212/consoleFull *00:40:57.431*TC02: Process tagged send untagged [ ERROR ] VAT script execution timeout: sudo -S vpp_api_test in /tmp/openvpp-testing/resources/templates/vat/show_trace.vat script *00:41:53.602*| FAIL | *00:41:53.603*Teardown failed: *00:41:53.603*SSHTimeout: Timeout exception during execution of command: sudo -S vpp_api_test in /tmp/openvpp-testing/resources/templates/vat/show_trace.vat script https://jenkins.fd.io/job/csit-vpp-functional-1801-centos7-virl/212/consoleFull *02:00:59.621*TC07: DUT1 and DUT2 with L2BD and VLAN translate-2-2 with wrong outer tag used (DUT1) switch ICMPv6 between two TG links :: ... [ WARN ] Tests.Vpp.Func.L2Bd.Eth2P-Dot1Ad-L2Bdbasemaclrn-Vlantrans22-Func - TC07: DUT1 and DUT2 with L2BD and VLAN translate-2-2 with wrong outer tag used (DUT1) switch ICMPv6 between two TG links *02:02:31.332*The VPP PIDs are not equal! *02:02:31.332*Test Setup VPP PIDs: {'10.30.54.206': 25207, '10.30.54.205': 26542} *02:02:31.332*Test Teardown VPP PIDs: None *02:02:31.332*Tests.Vpp.Func.L2Bd.Eth2P-Dot1Ad-L2Bdbasemaclrn-Vlantrans22-Func - TC07: DUT1 and DUT2 with L2BD and VLAN translate-2-2 with wrong outer tag used (DUT1) switch ICMPv6 between two TG links *02:02:31.332*The VPP PIDs are not equal! *02:02:31.332*Test Setup VPP PIDs: {'10.30.54.206': 25207, '10.30.54.205': 26542} *02:02:31.332*Test Teardown VPP PIDs: None *02:02:31.343*| FAIL | *02:02:31.343*Setup failed: *02:02:31.343*NoValidConnectionsError: [Errno None] Unable to connect to port 22 on or 10.30.54.207 Could you, please, have a look on it? Thanks, Jan *From:*csit-...@lists.fd.io <mailto:csit-...@lists.fd.io>[mailto:csit-...@lists.fd.io]*On Behalf Of*Thomas F Herbert *Sent:*Tuesday, February 13, 2018 2:14 PM *To:*csit-...@lists.fd.io <mailto:csit-...@lists.fd.io> *Subject:*Re: [csit-dev] t4-virl3 moved from testing back into production Yes, Everything should work fine with the 1.4 image. --Tom On 02/13/2018 12:27 AM, Peter Mikus wrote: Thank you Ed. Peter Mikus Engineer – Software Cisco Systems Limited -Original Message- From:csit-...@lists.fd.io <mailto:csit-...@lists.fd.io> [mailto:csit-...@lists.fd.io] On Behalf Of Ed Kern (ejk) Sent: Tuesday, February 13, 2018 12:06 AM To:csit-...@lists.fd.io <mailto:csit-...@lists.fd.io> Cc: Thomas F Herbert<therb...@redhat.com> <mailto:therb...@redhat.com> Subject: [csit-dev] FYI: t4-virl3 moved from testing back into production This is still with the ‘older’ centos image. Thomas said the newer one isn’t quite ready yet. So this is just an fyi if folks see something amiss in the next few days with the virl jobs to let me know. thanks, Ed -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat*
Re: [vpp-dev] Failing verify jobs
I have verified that this is a VIRL problem but am not sure how to fix it. Please see my response on the csit list. On 12/30/2017 06:35 PM, Dave Wallace wrote: Hi Jon, Thanks for the report. I rebased this patch yesterday because there had been a couple of reports of CSIT job failures due to this VIRL failure. Given that most/all of the CSIT team is on PTO until 1/2/18, I don't expect that this will be addressed before Tuesday, but I'm sure that it will be addressed as soon as practicable when everyone is back. Happy New Year! -daw- On 12/30/2017 11:01 AM, Jon Loeliger wrote: Folks, So, I have a long-standing "DON'T MERGE"-ish patch that is a recurring rebase request to help identify failures of missing #include files in C API application biulds. It is: https://gerrit.fd.io/r/8189 It was recently rebased, and failed for an entirely different reason. That reason appears to be related to some VIRL server failure. Starting around 16:02:56 in the console log file https://jenkins.fd.io/job/vpp-csit-verify-virl-master/8806/console shows this: *16:02:56* ++ ssh -i priv_key -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o LogLevel=errorjenkins-in@10.30.51.29 <mailto:jenkins-in@10.30.51.29> 'start-testcase -vv --quota 65 --copy double-ring-nested.xenial --release csit-ubuntu-16.04.1_2017-10-21_2.0 /tmp/vpp_18.01-rc0~540-gda58107~b8806_amd64.deb' /tmp/vpp-api-java_18.01-rc0~540-gda58107~b8806_amd64.deb /tmp/vpp-api-lua_18.01-rc0~540-gda58107~b8806_amd64.deb /tmp/vpp-api-python_18.01-rc0~540-gda58107~b8806_amd64.deb /tmp/vpp-dbg_18.01-rc0~540-gda58107~b8806_amd64.deb /tmp/vpp-dev_18.01-rc0~540-gda58107~b8806_amd64.deb /tmp/vpp-dpdk-dkms_17.11-vpp1_amd64.deb /tmp/vpp-lib_18.01-rc0~540-gda58107~b8806_amd64.deb /tmp/vpp-plugins_18.01-rc0~540-gda58107~b8806_amd64.deb apparently yielded this error: *16:02:58* VIRL simulation start failed on 10.30.51.29 I have no clue other than "connection wasn't established" as to why that might be. In fact I have no idea what is going on here. :-) Thanks, jdl ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] gerrit 9904 VIRL verification is failing
The problem is almost definitely in VIRL. I noticed it on the 26th while load testing VIRL3 by doing rechecks of CSIT patches: https://gerrit.fd.io/r/r/8759 https://gerrit.fd.io/r/9890 https://gerrit.fd.io/r/9900 I think Ed Kern will need to look at this. I noticed while it was failing nova list showed nothing. Then I noticed that there was nothing listed on the other VIRL servers despite rechecking patch 9904. Today, I failed to launch a local simulation on virl3: virl@t4-virl3:~/tfh/csit/resources/tools/disk-image-builder/centos$ !719 virl_std_client -u $VIRL_USER -p $VIRL_PASSWORD simengine-launch -f listmaker/virl-listmaker-centos-7.3-1611.yaml INFO 2017-12-31 16:37:48,788 virl.std.client Client.simengine_launch called args=(mode 'rb' at 0x7f038b6ed5d0>, None, False, None, None, None, None, None, None) kargs={} INFO 2017-12-31 16:37:48,788 virl.std.client simengine_launch POST on URL "http://localhost:19399/simengine/rest/launch; INFO 2017-12-31 16:37:48,966 virl.std.client simengine_launch response 500 to POST on URL "http://localhost:19399/simengine/rest/launch?file=virl-listmaker-centos-7.3-1611.yaml; ERROR 2017-12-31 16:37:48,967 virl.std.client STD client call to Client.simengine_launch received invalid response status 500 (Cisco contact was not established. This may be temporary.) Exception cause: STD simengine-launch request received invalid response: 500 - Cisco contact was not established. This may be temporary. I grabbed the logs and saw this in the std.server.log virl_std_client -u $VIRL_USER -p $VIRL_PASSWORD simengine-systemlogs > logs.zip I saw the following in std_server.log vi std_server.log quest: "GET /simengine/rest/events/session" user "tb4-virl" ERROR 2017-12-31 16:23:18,788 PID=45336 virl.std.implementation Simulation "session" not found. Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1612, in full_dispatch_request rv = self.dispatch_request() File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1598, in dispatch_request return self.view_functions[rule.endpoint](**req.view_args) File "", line 2, in simengine_events File "/var/jenkins/workspace/VIRL_CORE_build/test-virl-repo/virl/std/implementation.py", line 330, in middleware File "", line 2, in simengine_events File "/var/jenkins/workspace/VIRL_CORE_build/test-virl-repo/virl/common/utils.py", line 94, in measurer File "/var/jenkins/workspace/VIRL_CORE_build/test-virl-repo/virl/std/implementation.py", line 2177, in simengine_events HttpException: Simulation "session" not found. --Tom On 12/27/2017 09:48 AM, Thomas F Herbert wrote: On 12/27/2017 09:02 AM, Neale Ranns (nranns) wrote: Hi Nitin, Hit the ‘reply’ button and post a review comment of: recheck that will poke Jenkins to redo the verification. /neale -Original Message- From:<vpp-dev-boun...@lists.fd.io> on behalf of "Saxena, Nitin"<nitin.sax...@cavium.com> Date: Wednesday, 27 December 2017 at 14:38 To: "Dave Barach (dbarach)"<dbar...@cisco.com>,"vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> Subject: [vpp-dev] gerrit 9904 VIRL verification is failing Hi, I sent a patch (https://gerrit.fd.io/r/#/c/9904/) for review in which "vpp-csit-verify-virl-master" job is failing. Console logs (https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-csit-verify-virl-master/8798/console.log.gz) shows following error. call_home\nFlmClientException: Cisco contact was not established. This may be temporary.\nPlease make sure the VIRL server is connected to the Internet and capable of reaching the configured Cisco master.\nAlso make sure that the minion key provided to you matches your minion ID and domain, and remains valid.\nCurrent status is: Last successful contact was more than 7 days ago.\nLast call home check result was: Call has timed out; failed to connect or minion key not accepted.\n" I have also seen what looks like the same thing on VIRL3 which is currently not in production. I reported it yesterday to the CSIT mailing list. https://jenkins.fd.io/job/csit-vpp-functional-master-ubuntu1604-virl/3290/ } + VIRL_SID[${index}]= + retval=1 + '[' 1 -ne 0 ']' + echo 'VIRL simulation start failed on 10.30.51.29' VIRL simulation start failed on 10.30.51.29 === Seems like a temporary problem. What is the gerrit command such that Jenkins again start doing verification. Thanks, Nitin ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listi
Re: [vpp-dev] gerrit 9904 VIRL verification is failing
On 12/27/2017 09:02 AM, Neale Ranns (nranns) wrote: Hi Nitin, Hit the ‘reply’ button and post a review comment of: recheck that will poke Jenkins to redo the verification. /neale -Original Message- From: <vpp-dev-boun...@lists.fd.io> on behalf of "Saxena, Nitin" <nitin.sax...@cavium.com> Date: Wednesday, 27 December 2017 at 14:38 To: "Dave Barach (dbarach)" <dbar...@cisco.com>, "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> Subject: [vpp-dev] gerrit 9904 VIRL verification is failing Hi, I sent a patch (https://gerrit.fd.io/r/#/c/9904/) for review in which "vpp-csit-verify-virl-master" job is failing. Console logs (https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-csit-verify-virl-master/8798/console.log.gz) shows following error. call_home\nFlmClientException: Cisco contact was not established. This may be temporary.\nPlease make sure the VIRL server is connected to the Internet and capable of reaching the configured Cisco master.\nAlso make sure that the minion key provided to you matches your minion ID and domain, and remains valid.\nCurrent status is: Last successful contact was more than 7 days ago.\nLast call home check result was: Call has timed out; failed to connect or minion key not accepted.\n" I have also seen what looks like the same thing on VIRL3 which is currently not in production. I reported it yesterday to the CSIT mailing list. https://jenkins.fd.io/job/csit-vpp-functional-master-ubuntu1604-virl/3290/ } + VIRL_SID[${index}]= + retval=1 + '[' 1 -ne 0 ']' + echo 'VIRL simulation start failed on 10.30.51.29' VIRL simulation start failed on 10.30.51.29 === Seems like a temporary problem. What is the gerrit command such that Jenkins again start doing verification. Thanks, Nitin ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Please install missing RPMs: \npackage python34 is not installed
What commit are you building? This has not been a problem for some time and is not a problem on stable/1710 or the top of tree current master. There was a dependency introduced by an earlier commit which was subsequently removed. --Tom On 12/14/2017 10:05 PM, wrote: Hi, everyone ?0?2 ?0?2I build vpp on centos 7.3, and had executed make install-dep. It is ok. but when i make build vpp . it print "Please install missing RPMs: \npackage python34 is not installed". Then i install python3.4 and?0?2 after installed the python is ok. make build vpp is still : "Please install missing RPMs: \npackage python34 is not installed", Why ? ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] [csit-dev] New Option for fd.io mailing lists: groups.io
I have found the UI for moderation on Mailman a little difficult. Both systems require authentication via email to join. I would think that would reduce most bots/SPAM. So the advantage if any of Groups.io is that it has a better gui. Do we se have use for its wiki or calendar? I have found the moderation view of the mailman gui a little confusing and maybe this I think may be the best advantage of groups.io. At least from the standpoint of a somewhat light user of moderation. I think it would be transparent to participants. --Tom On 12/14/2017 10:45 AM, Ed Warnicke wrote: A new option has become available for handling mailing lists: groups.io <http://groups.io> As a community, we need to look at this option, provide feedback, and come to a decision as to whether or not to migrate. A critical part of that is having folks take a look, ask questions, and express opinions :) We have a sandbox example at https://groups.io/g/lfn you can look at And an example with active list and imported archive: https://lists.odpi.org/g/odpi-sig-bi Major benefits include searchability, better web interface, etc. The LF was kind enough to write a FAQ for us as we consider as a community whether to migrate or not: *FAQs* *Q: What are the key differences between Mailman and Groups.io?* ●Groups.io has a modern interface, robust user security model, and interactive, searchable archives ●Groups.io provides advanced features including muting threads and integrations with modern tools like GitHub, Slack, and Trello ●Groups.io also has optional extras like a shared calendar, polling, chat, a wiki, and more ●Groups.io uses a concept of subgroups, where members first join the project “group” (a master list), then they choose the specific “subgroup” lists they want to subscribe to *Q: How is the experience different for me as a list moderator or participant?* In many ways, it is very much the same. You will still find the main group at your existing URL and sub-groups equate to the more focused mailing lists based on the community’s needs. Here is an example of main group and sub-group URL patterns, and their respective emails: https://lists.fd.io/g/tsc https://lists.fd.io/g/discuss https:/lists.fd.io/g/vpp-dev <http://lists.fd.io/g/vpp-dev> t...@lists.fd.io <mailto:t...@lists.fd.io> disc...@lists.fd.io <mailto:disc...@lists.fd.io> vpp-...@llists.fd.io <mailto:vpp-...@llists.fd.io> What is different is Groups.io’s simple but highly functional UI that will make the experience of moderating or participating in the community discussions more enjoyable. ___ csit-dev mailing list csit-...@lists.fd.io https://lists.fd.io/mailman/listinfo/csit-dev -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Fwd: :: Setting Mac address on Vlan interface
ble 5 via 1.1.1.5 host-tap3.1 >> >> >> >> set ip arp host-tap2.1 1.1.1.5 02:00:00:00:00:01 >> >> set ip arp host-tap3.1 1.1.1.5 02:00:00:00:00:01 >> >> >> >> However traffic flows having Source Mac addresses as that of respective >> Vlan interfaces. Is there any way I could set Vlan interfaces with my own >> desired Mac Addresses, so that the traffic has user defined Mac addresses >> as Source Mac addresses. >> >> >> >> Thanks. >> >> Best Regards, >> >> Omer Majeed >> >> >> >> ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Jenkins jobs not starting from a "clean" state?
Marco V SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg -- Marco V SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg ___________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] And Boost Log too?
boost and boost-devel should suffice. On 11/08/2017 03:30 PM, Jon Loeliger wrote: On Wed, Nov 8, 2017 at 2:29 PM, Neale Ranns (nranns) <nra...@cisco.com <mailto:nra...@cisco.com>> wrote: Hi Jon, It doesn’t need it. I must have left that in by mistake. I’ll take it out. Awesome. Thanks! jdl ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Networking Group Office of the CTO *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] debuginfo rpms missing from nexus yum repos.
Hi, I noticed while working on csit that vpp debuginfo rpms are "missing" from Nexus Centos repo and have been since late September. The newest ones date back to September. Does anybody know why? --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Office of the CTO *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] [centos-dev][NFV SIG] VPP 17.10 rc1 available in Centos for testing.
Centos developers, VPP version 17.10 is available in Centos CBS for testing, This is a build of 17.10-rc1. https://cbs.centos.org/koji/buildinfo?buildID=20183 For more information about VPP and fd.io, https://wiki.fd.io/view/Main_Page https://fd.io/ --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Downstream builds for Centos
VPPers: We have had some progress during the last week with builds in Centos: This is a build of 1710-rc0. https://cbs.centos.org/koji/buildinfo?buildID=20183 As soon as The final upstream 1710 release is tagged, I will push this to "release" tag and try to get it into a Centos yum repo. Stay tuned. --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Process question for gerrit
On 10/12/2017 11:33 AM, Dave Wallace wrote: Hi Tom, IMHO, it would be best for developers to cherry-pick bug fixes into master that they have committed to stable/* branches. Yes. Thanks. I agree as does Florin. Done for both patches. Thanks, -daw- On 10/12/2017 10:11 AM, Thomas F Herbert wrote: Process question: Some bug fixes were merged directly into vpp-stable/1710 that should also be cherry-picked into master. Should we developers cherry-pick our own gerrits to master or should the maintainers do this? Either way is OK with me. --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] VPP 17.10 RC2
Florin, OK. That makes sense. I will cherry-pick two patches that were merged in stable/1710 --Tom On 10/12/2017 10:46 AM, Florin Coras wrote: Hi Tom, I’d appreciate it if patch owners would cherry-pick the patches. It might be the case that some fixes may not need to be cherry picked to master and in other cases, when master and stable run out of sync, the cherry-picks might actually require more work. Regards, Florin On Oct 12, 2017, at 7:13 AM, Thomas F Herbert <therb...@redhat.com <mailto:therb...@redhat.com>> wrote: On 10/11/2017 06:14 PM, Florin Coras wrote: Folks, 17.10 RC2 tag has been laid. Nonetheless, our patching process continues to remain the same until formal release [1], i.e., fixes first to stable/1710 and then cherry-pick to master. Florin, should us submitters cherry-pick our own bug-fix patches to master or should we wait for you do them all? Regards, Florin [1] https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_17.10 ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] VPP 17.10 RC2
On 10/11/2017 06:14 PM, Florin Coras wrote: Folks, 17.10 RC2 tag has been laid. Nonetheless, our patching process continues to remain the same until formal release [1], i.e., fixes first to stable/1710 and then cherry-pick to master. Florin, should us submitters cherry-pick our own bug-fix patches to master or should we wait for you do them all? Regards, Florin [1] https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_17.10 ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Process question for gerrit
Process question: Some bug fixes were merged directly into vpp-stable/1710 that should also be cherry-picked into master. Should we developers cherry-pick our own gerrits to master or should the maintainers do this? Either way is OK with me. --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Process for submitting patches to stable/1710
OK, Thanks! I added Damjan to review. --Tom On 10/10/2017 05:17 PM, Florin Coras wrote: Hi Tom, As long as the patches have a jira ticket, procedurally all is fine with me. However, since we’re so close to release, I’d like Damjan, since he’s the build infra manager, to vet the changes. Regards, Florin On Oct 10, 2017, at 12:24 PM, Thomas F Herbert <therb...@redhat.com <mailto:therb...@redhat.com>> wrote: Dave, Florin, I have two patches in gerrit for stable/1710, both with JIRAs. Is there a chance that these can make it into 1710-rc2? They both fix problems that break rpm builds but add no additional features. I want to confirm I am following the correct procedure. One was originally submitted to master and rebased to stable/1710 and the other one was submitted directly to stable/1710. https://gerrit.fd.io/r/8721 https://gerrit.fd.io/r/8720 https://jira.fd.io/browse/VPP-1015 https://jira.fd.io/browse/VPP-1014 --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Dependency on libsubunit ? (and failing to run tests)
On 10/10/2017 10:46 AM, Marco Varlese wrote: Hi Klement, Yes, once check-devel is in place, then we can remove -lsubunit from test/ext/Makefile. Things would still work (at least on openSUSE). I submitted a patch for review: https://gerrit.fd.io/r/#/c/8736 Subunit is a prerequisite for check version 0.10 which is used in Fedora. However, I don't know if check version 0.10 actually needs to be bound with subunit or whether this is just an RPM dependency. Cheers, Marco On Tue, 2017-10-10 at 14:03 +, Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco) wrote: Hi Marco, this issue is already being investigated by Tom Herbert. Strange thing is that check requires subunit. I wonder if it works if you install check only. Could you try removing -lsubunit from test/ext/Makefile? Thanks, Klement Quoting Marco Varlese (2017-10-10 16:00:00) Hi all, As of last week I could happily run tests (e.g. make test) on my distribution (openSUSE). When I tried again today - with latest master - I couldn't anymore: make[2]: Entering directory '/home/mvarlese/repo/vpp/test/ext' cc -o /home/mvarlese/repo/vpp/build-root/vapi_test/vapi_c_test -std=gnu99 -g -Wall -pthread -I/home/mvarlese/repo/vpp/src -I/home/mvarlese/repo/vpp/build- root/install-vpp-native//vpp/include -I/home/mvarlese/repo/vpp/build- root/vapi_test/ vapi_c_test.c -L/home/mvarlese/repo/vpp/build-root/build- vpp- native/vpp/.libs/ -L/home/mvarlese/repo/vpp/build-root/build-vpp- native/vpp/vpp- api/vapi/.libs/ -lvppinfra -lvlibmemoryclient -lsvm -lpthread -lcheck -lsubunit -lrt -lm -lvapiclient /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -lsubunit collect2: error: ld returned 1 exit status I tried to find the newly introduced dependency on libsubunit but wasn't successful. Can anybody shed some light? Separate, we do not have that package on our distro... Cheers, Marco ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] [releng] Proposal to redirect #opendaylight-releng to #lf-releng
+ci-...@fd.io This probably should also go to ci-man which is roubhly the equivalent of releng in opnfv. --TFH On 10/03/2017 02:12 PM, Thanh Ha wrote: On Tue, Sep 26, 2017 at 6:38 PM, Thanh Ha <thanh...@linuxfoundation.org <mailto:thanh...@linuxfoundation.org>> wrote: Hi Everyone, We'd like to pitch an idea to have #opendaylight-releng irc channel redirect to a new #lf-releng channel. Something that's occurred to us is that many of the networking at LF projects have their own separate releng channels in which folks typically ask JJB related questions. Each of these channels are typically moderately active. Something we've been thinking about is the idea of merging all these releng channels into #lf-releng which we're hoping can combine the communities JJB experts so that JJB and other releng related questions can be more broadly asked. Thoughts? Regards, Thanh Hi Everyone, For those that don't know me. I am one of the release engineers working on the OpenDaylight project. I've added the fd.io <http://fd.io>, opnfv, and onap communities to this list to get feedback on the idea proposed above. Let me know if there's other mailing lists in the respective projects we should be cc'ing to include in the discussions. I'd like to hear from the fd.io <http://fd.io>, opnfv, and onap for their thoughts on the proposal to create a single lf-releng channel on IRC and have all the respective releng channels redirect to it. Since our respective releng projects use similar technologies like JJB, Jenkins, etc... it might be a benefit to pool together our expertise so that it is easier to ask questions to the broader community when we need help with things like JJB, Gerrit, etc... You can follow the discussion thread so far from the ODL community discussed here: https://lists.opendaylight.org/pipermail/dev/2017-September/004066.html Regards, Thanh ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19
On 09/25/2017 05:02 AM, Marco Varlese wrote: Thanks for the thorough explanation Klement!Based on that, I think (2) is still the better option for the current situation... Tom, how would that sound to you? "Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)" <ksek...@cisco.com> 09/25/17 10:40 AM >>> Quoting Marco Varlese (2017-09-25 10:26:50) Hi Klement, "Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)" <ksek...@cisco.com> 09/25/17 9:33 AM >>> At the time of creating this patch, epel was part of Makefile and python34 was installed as dependency from that repo. (see https://gerrit.fd.io/r/#/c/6983/53/Makefile) At later time, the epel stuff disappeared and with it also the possibility to add python34 as a centos dependency - commit bd8e242024fcc2daffa77bdd6e2da1296ace5c69. I remember pointing this out in discussion with Neale, but I didn't get a chance to test whether centos works or not before it was merged. That's OK. You would have had to test with a system without EPEL Repo enabled to discover this problem. I should have paid closer attention when this patch was first discussed in May. Please add me as a reviewer for patches that have implications for RPM packaging and requirements. I think it would be nice though to update other scripts too so to have one single python version used across the board. Currently, to build VPP on our distribution I need to require both python and python3 packages since some python scripts use one rather than the other. Aligning python versions would make downstream consumption better I believe. Is this something which will/could be done? See below. As for the solution, I can think of 3 options: 1.) require python3 (which has been around for some ~9 years now) 2.) disable generation of the C (and C++) API if python3 is not detected I think this would be a fair compromise for distros not supporting (yet) python3. However, I am not sure how this would result in the VPP CI... wouldn't this break all tests running over those API? Tests are python2.7 because scapy wasn't python3 capable when we designed the test framework. These are language bindings, not different API calls. Only test_vapi, which tests that the language bindings of different types (simple request, dump, event, etc.) work would have to be disabled. I think this is a good interim work-around until the distros have Python3. I can submit another patch to allow this the inclusion would be enabled as a default but could be disabled only in downstream builds in RHEL and Centos 7. When will we have tests in CSIT that use the C/C++ APIs in 17.10? Neale, are we planning to cherry-pick this patch into 17.10? Do we have yet tests in CSIT that use the C/C++ APIs in 17.10? 3.) convert the script to python2.7 (which is in the opposite direction of where we would want to go wrt python version) Thanks, Klement Cheers, Marco Quoting Thomas F Herbert (2017-09-23 15:55:10) All: Commit 8f2a4ea, Gerrit, [1]https://gerrit.fd.io/r/#/c/6983/ "Add new C API" introduces a dependency on Python 3 and breaks downstream builds for Centos. Unfortunately, neither RHEL nor Centos currently support Python 3. Most VPPers are probably building with EPEL repo so this problem didn't show up until now but actually there is no dependency on EPEL in the Makefile or spec file. If anybody can suggest a solution short of pushing Python 3 into the downstream repos, I am open to suggestions. --Tom -- Thomas F Herbert NFV and Fast Data Planes Office of Technology Red Hat References Visible links 1. https://gerrit.fd.io/r/#/c/6983/ ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Problem with new c api patch commit 8f2a4ea merged on September 19
All: Commit 8f2a4ea, Gerrit, https://gerrit.fd.io/r/#/c/6983/ "Add new C API" introduces a dependency on Python 3 and breaks downstream builds for Centos. Unfortunately, neither RHEL nor Centos currently support Python 3. Most VPPers are probably building with EPEL repo so this problem didn't show up until now but actually there is no dependency on EPEL in the Makefile or spec file. If anybody can suggest a solution short of pushing Python 3 into the downstream repos, I am open to suggestions. --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] CentOS 7.4
After update you need reboot to install new kernel and make sure kernel headers are consistent with new kernel. I think the update "should" update all installed RPMs including those that were previously installed with make install-dep. nasm for Centos is updated outside of yum because nasm 2.12+ is still not available in downstream Centos distro. On 09/19/2017 04:03 PM, Burt Silverman wrote: Problem solved after 1)rebooting, 2) cd ~/vpp; rm -rf *; git checkout . 3) make install-dep; make bootstrap; make build-release. Possibly it was just the reboot and make install-dep, I am not sure, but I saw nasm getting updated at that point. Thanks, Tom, for hints. Burt On Mon, Sep 18, 2017 at 10:59 PM, Burt Silverman <bur...@gmail.com <mailto:bur...@gmail.com>> wrote: I updated my CentOS using "yum update" and that leaves me with CentOS 7.4. So I get those fPIC errors that others have reported on non CentOS systems but that have glibc 2.17. Are others seeing the same thing? It looks to me that the official builds under CentOS are being done WITHOUT "yum update". Thanks. Burt -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] https://gerrit.fd.io/r/#/c/8236/
On 08/30/2017 01:57 PM, Gabriel Ganne wrote: https://gerrit.fd.io/r/#/c/8260/ It adds bc to the dependency list, but also replaces a $(shell $(echo …)) by $(shell `echo …`) They should be the same, but it seems to change the way the Makefile variables are interpreted. The problem I saw was on Fedora and Centos both of which have bc. The problem it needs a double $ to escape the "$()" from make because it "thinks" it is a reference to a variable. commit 14afc64629e9b35a2e5c5941232236a78c2ecd75 Author: Thomas F Herbert <therb...@redhat.com> Date: Wed Aug 30 10:13:51 2017 -0400 Fix shell error. Change-Id: I06af51eef20c2191199613f951f569ef1727b9c4 Signed-off-by: Thomas F Herbert <therb...@redhat.com> diff --git a/Makefile b/Makefile index 1548f36..ef92e2f 100644 --- a/Makefile +++ b/Makefile @@ -78,7 +78,7 @@ ifeq ($(OS_ID)-$(OS_VERSION_ID),fedora-25) RPM_DEPENDS += python-devel RPM_DEPENDS += python2-virtualenv RPM_DEPENDS_GROUPS = 'C Development Tools and Libraries' -else ifeq ($(shell if [ $(echo "$(OS_VERSION_ID) > 25" | bc) -eq 1 ] ; then echo "y" ; fi),"y") +else ifeq ($(shell if [ $$(echo "$(OS_VERSION_ID) > 25" | bc) -eq 1 ] ; then echo "y" ; fi),"y") RPM_DEPENDS += python2-devel RPM_DEPENDS += python2-virtualenv RPM_DEPENDS_GROUPS = 'C Development Tools and Libraries' I tested on rhel 7, Ubuntu 16.04, and debian 8. Best regards, -- Gabriel Ganne *From:*Dave Wallace [mailto:dwallac...@gmail.com] *Sent:* mercredi 30 août 2017 16:27 *To:* Burt Silverman <bur...@gmail.com>; Gabriel Ganne <gabriel.ga...@enea.com> *Cc:* Thomas F Herbert <therb...@redhat.com>; vpp-dev <vpp-dev@lists.fd.io> *Subject:* Re: [vpp-dev] https://gerrit.fd.io/r/#/c/8236/ I agree. @Gabriel, please push a patch which adds bc to DEB_DEPENDS in vpp/Makefile. Thanks, -daw- On 08/30/2017 09:14 AM, Burt Silverman wrote: To me, it doesn't seem to be a crime to add bc to the dependencies. I guess another approach would be to remove the dot in 16dot04 and then just use shell arithmetic. The release numbers are always in the same format, 2 digits DOT 2 digits, so I would think that should work. Burt On Wed, Aug 30, 2017 at 3:47 AM, Gabriel Ganne <gabriel.ga...@enea.com <mailto:gabriel.ga...@enea.com>> wrote: Hi, This probably is be because you don't have bc. It is not in the dependency list. I'm so used to having it around that I did not think to check. Sorry. If so, the best thing probably is to revert and not to increase the dependency list just to silence a warning. Regards, -- Gabriel Ganne *From:*Dave Wallace <dwallac...@gmail.com <mailto:dwallac...@gmail.com>> *Sent:* Wednesday, August 30, 2017 6:25:32 AM *To:* Thomas F Herbert; Gabriel Ganne *Cc:* vpp-dev *Subject:* Re: [vpp-dev] https://gerrit.fd.io/r/#/c/8236/ <https://url10.mailanyone.net/v1/?m=1dn3xX-0006Hd-50=57e1b682=cStJh6yQU2F9FWBIKNcsjRgTf-ntcQfeHTWOgVHSer9pSh1n2Ke77HoWikhOjcSWh0z-O2rHVl18yF2FOHhjhruUhq8VyojK4u6e0BbsFIHZleaRifwRLCWsosaGdVw__FJqiQlIB_Gvaa1w9Jm_gQAlPYBetc4L-9HozLkobTyK5775Sj6qZDN6ijVpzsIcF1ulKmuWUEnw9sNtRAXHMyDXYthGBQFz_EFyNSgCszs> Tom, What OS are you running? Thanks, -daw- On 08/29/2017 07:58 PM, Thomas F Herbert wrote: This patch creates may have fixed one problem with Ubuntu 16.04 but created another: $ make /bin/sh: line 0: [: -eq: unary operator expected ... -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> https://lists.fd.io/mailman/listinfo/vpp-dev <https://url10.mailanyone.net/v1/?m=1dmuZP-0007YU-5v=57e1b682=Qsrdfe_DPl_SvvWzv--VtKCBJOKVTEg4VL0ZnkHG2v411y213_M9DM_3rjAI_f7X2ifYtM6xQxMwYWfBDcZTqZxJaNy5yHnZcs5MFE_YJQCWz0i2q6fT4KpnC8m_c_MsVfHOcIcUpBQ7dUboUbtyy5Ey7roG_YlGZSbaOR7rmgDeloqmgdxJ1d-Duo6FX-6ARriIWYlW9895XudmB85pM0kVgfReq85yx9Z-4QG_addHGYW74uqlKVoVuMF6O6ni> ___ vpp-dev mailing list vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> https://lists.fd.io/mailman/listinfo/vpp-dev <https://url10.mailanyone.net/v1/?m=1dn3xX-0006Hd-50=57e1b682=EqcMBcwLbPIpILbjmEVtzuPv1tv4iapVkLyJrlkzz0UhLpP0wGZLZTNDpeO9UJwtlk5EUSaYSRG16iZ7f2x6tCkRecTwkKo0B_NuE_yrCrMiUQkJOqx1KujPdK
[vpp-dev] https://gerrit.fd.io/r/#/c/8236/
This patch creates may have fixed one problem with Ubuntu 16.04 but created another: $ make /bin/sh: line 0: [: -eq: unary operator expected ... -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Please review patch 8117 and 8215
On 08/25/2017 01:34 PM, Damjan Marion (damarion) wrote: Tom, let me know when they are verified and I will merge them…. Damjan, Thanks! Both patches are now verified. Thanks, Damjan On 25 Aug 2017, at 18:16, Thomas F Herbert <therb...@redhat.com <mailto:therb...@redhat.com>> wrote: Ignore previous message for now. I have to re-base the patch. On 08/25/2017 11:53 AM, Thomas F Herbert wrote: All, Could someone please review the patch below? Probably the gerrit emails are buried in various inboxes. https://gerrit.fd.io/r/#/c/8117/ Thanks, --TFH -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Please review patch 8117
Ignore previous message for now. I have to re-base the patch. On 08/25/2017 11:53 AM, Thomas F Herbert wrote: All, Could someone please review the patch below? Probably the gerrit emails are buried in various inboxes. https://gerrit.fd.io/r/#/c/8117/ Thanks, --TFH -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Please review patch 8117
All, Could someone please review the patch below? Probably the gerrit emails are buried in various inboxes. https://gerrit.fd.io/r/#/c/8117/ Thanks, --TFH -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] MLX3
All, Billy and I are purchasing new server(s) and it is currently being specified with Mellanox ConnectX-3. I see it is supported but how much experience do we have with this card? Do we have to use OFED etc. for perf tuning or is that only for the ConnextX-4 and 5? Thanks --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] VPP compile error building vpp ipsec on Fed 26
I am getting a compile error when building on Fedora 26. I am building master commit 3f6ff19a30e9fbe5befb4cc3521d1812e5612197 With openssl-devel-1.1.0f-7.fc26.x86_64 installed. CC vnet/ipsec/ipsec.lo In file included from /home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-data/../src/vnet/ipsec/ipsec.c:25:0: /home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-data/../src/vnet/ipsec/esp.h:63:18: error: field ‘encrypt_ctx’ has incomplete type EVP_CIPHER_CTX encrypt_ctx; ^~~ /home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-data/../src/vnet/ipsec/esp.h:65:18: error: field ‘decrypt_ctx’ has incomplete type EVP_CIPHER_CTX decrypt_ctx; ^~~ /home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-data/../src/vnet/ipsec/esp.h:67:12: error: field ‘hmac_ctx’ has incomplete type HMAC_CTX hmac_ctx; ^~~~ /home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-data/../src/vnet/ipsec/esp.h: In function ‘esp_init’: /home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-data/../src/vnet/ipsec/esp.h:274:7: error: implicit declaration of function ‘HMAC_CTX_init’; did you mean ‘HMAC_CTX_new’? [-Werror=implicit-function-declaration] HMAC_CTX_init (&(em->per_thread_data[thread_id].hmac_ctx)); ^ HMAC_CTX_new /home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-data/../src/vnet/ipsec/esp.h: In function ‘hmac_calc’: /home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-data/../src/vnet/ipsec/esp.h:301:3: error: ‘HMAC_Init’ is deprecated [-Werror=deprecated-declarations] HMAC_Init (ctx, key, key_len, md); ^ In file included from /usr/include/openssl/opensslconf.h:42:0, from /usr/include/openssl/bn.h:31, from /usr/include/openssl/asn1.h:24, from /usr/include/openssl/objects.h:916, from /usr/include/openssl/evp.h:27, from /usr/include/openssl/hmac.h:15, from /home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-data/../src/vnet/ipsec/esp.h:18, from /home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-data/../src/vnet/ipsec/ipsec.c:25: /usr/include/openssl/hmac.h:28:1: note: declared here DEPRECATEDIN_1_1_0(__owur int HMAC_Init(HMAC_CTX *ctx, const void *key, int len, ^ cc1: all warnings being treated as errors make[6]: *** [Makefile:6098: vnet/ipsec/ipsec.lo] Error 1 make[6]: *** Waiting for unfinished jobs make[6]: Leaving directory '/home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-root/build-vpp-native/vpp' make[5]: *** [Makefile:6979: all-recursive] Error 1 make[5]: Leaving directory '/home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-root/build-vpp-native/vpp' make[4]: *** [Makefile:3562: all] Error 2 make[4]: Leaving directory '/home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-root/build-vpp-native/vpp' make[3]: *** [Makefile:697: vpp-build] Error 2 make[3]: Leaving directory '/home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-root' make[2]: *** [Makefile:933: install-packages] Error 1 make[2]: Leaving directory '/home/therbert/fd.io/vpp/extras/rpm/vpp-17.10/build-root' error: Bad exit status from /var/tmp/rpm-tmp.kz3qOs (%build) ... -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] https://gerrit.fd.io/r/#/c/7856/ Review gerrit please
I saw it. Thanks, --Tom On 08/08/2017 11:29 AM, Neale Ranns (nranns) wrote: Merged. Thanks, neale *From: *<vpp-dev-boun...@lists.fd.io> on behalf of Thomas F Herbert <therb...@redhat.com> *Date: *Tuesday, 8 August 2017 at 16:05 *To: *vpp-dev <vpp-dev@lists.fd.io> *Subject: *[vpp-dev] https://gerrit.fd.io/r/#/c/7856/ Review gerrit please All: Could someone please review this patch? https://gerrit.fd.io/r/#/c/7856/ I have some additional dependent patches on this patch to submit. --TFH -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] node.js
Hi, I am doing the accounting on required packages for downstream builds. Does anyone know why epel-rpm-macros are included in our dependencies. This RPM provides an rpm macro which overrides another macro that defines the arch's on which node.js runs? What is the history as to this being in our dependencies: Makefile line 93 node.js is server side javascript. I don't see any instance or know of any reason why we need node.js? Am I missing something? --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] https://gerrit.fd.io/r/#/c/7856/ Review gerrit please
All: Could someone please review this patch? https://gerrit.fd.io/r/#/c/7856/ I have some additional dependent patches on this patch to submit. --TFH -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] VPP 908 and nasm revision
On 07/25/2017 06:43 AM, Sergio Gonzalez Monroy wrote: Hey Tom, It wasn't so much about having a new nasm version but when we already have a newer version installed in the system, the build fails because we do not have the specific 2.12 version. Maybe a simple workaround would be to have nasm in a fedora specific _DEPENDS variable and keep the fixed version for RHEL/CENTOS? Yes, since Fedora has 2.12 downstream, I will do that in the next patch series which I am working on now. Thanks, Sergio On 24/07/2017 16:08, Thomas F Herbert wrote: Sergio, I updated JIRA 908, https://jira.fd.io/browse/VPP-908 Could you please send me the new required revision of nasm? --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] VPP 908 and nasm revision
Sergio, I updated JIRA 908, https://jira.fd.io/browse/VPP-908 Could you please send me the new required revision of nasm? --Tom -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Nexus server seems to be down: https://nexus.fd.io
It is back up now. On 06/25/2017 02:36 PM, Ed Warnicke wrote: What symptoms are you seeing... my normal spot checks show it up, but it may be down more subtly than they would detect. http was hanging. It lasted an hour or more. Ed On Sun, Jun 25, 2017 at 9:58 AM, Thomas F Herbert <therb...@redhat.com <mailto:therb...@redhat.com>> wrote: The nexus server seems to be down for about 40 minutes now. Has anyone else noticed this? --TFH -- *Thomas F Herbert* Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> https://lists.fd.io/mailman/listinfo/vpp-dev <https://lists.fd.io/mailman/listinfo/vpp-dev> -- *Thomas F Herbert* Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] [csit-dev] CI Tests Failing
hudson.model.ResourceController.execute(ResourceController.java:98) > 19:48:45at hudson.model.Executor.run(Executor.java:405) > 19:48:45 Build step 'Execute a set of scripts' marked build as failure > > > > ___ > vpp-dev mailing list > vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> > https://lists.fd.io/mailman/listinfo/vpp-dev <https://lists.fd.io/mailman/listinfo/vpp-dev> ___ csit-dev mailing list csit-...@lists.fd.io <mailto:csit-...@lists.fd.io> https://lists.fd.io/mailman/listinfo/csit-dev <https://lists.fd.io/mailman/listinfo/csit-dev> -- *Thomas F Herbert* Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Question: make realclean
On 05/08/2017 10:11 AM, Damjan Marion (damarion) wrote: On 3 May 2017, at 17:20, Jon Loeliger <j...@netgate.com <mailto:j...@netgate.com>> wrote: Hey VPP Builders, Do you ever use "cd build-root; make distclean"? Does it look sort of like this: jdl $ cd build-root/ jdl $ make distclean rm -rf /home/jdl/workspace/vpp/build-root/build-*/ rm -rf /home/jdl/workspace/vpp/build-root/build-tool-* rm -rf /home/jdl/workspace/vpp/build-root/install-* rm -rf /home/jdl/workspace/vpp/build-root/images-* rm -rf /home/jdl/workspace/vpp/build-root/tools rm -rf /home/jdl/workspace/vpp/build-root/*.deb rm -rf /home/jdl/workspace/vpp/build-root/*.rpm rm -rf /home/jdl/workspace/vpp/build-root/*.changes rm -rf /home/jdl/workspace/vpp/build-root/python if [ -e /usr/bin/dh ];then (cd /home/jdl/workspace/vpp/build-root/deb/;debian/rules clean); fi rm -f /home/jdl/workspace/vpp/build-root/deb/debian/*.install rm -f /home/jdl/workspace/vpp/build-root/deb/debian/changelog Remember back in commit c06eeb0e3c9c1a9fa8f913e2d785b03220bfdabd Author: Damjan Marion <damar...@cisco.com <mailto:damar...@cisco.com>> Date: Tue Apr 18 15:26:39 2017 +0200 Fix "make dist" to include version number, docouple it from rpm packaging Change-Id: If2f9976d668089026c97b897cf449bff09050631 Signed-off-by: Damjan Marion <damar...@cisco.com <mailto:damar...@cisco.com>> when we moved the RPM building pieces out of build-root/rpm and placed them under extras/rpm instead? Should we have also modified the distclean make target to rm the rpms out of extras/rpm too? Or was that an intentional change as well? Makes sense to do that from top level makefile, i.e. run "git clean -fdX” but I would prefer that build-root/Makefile only takes care for build-root/. +1 ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Question: make realclean
On 05/03/2017 03:22 PM, Jon Loeliger wrote: On Wed, May 3, 2017 at 1:39 PM, Thomas F Herbert <therb...@redhat.com <mailto:therb...@redhat.com>> wrote: On 05/03/2017 12:23 PM, Jon Loeliger wrote: Naturally, I meant "make distclean" on the Subject: line. :-) distclean removes the tarball created by the "make dist" target. OK, but, so? I think I missed your point. My point was that the "make distclean" is trying to remove RPM packages from a location that no longer holds them. And subsequently, it does not remove them from the directory that *does* hold them. Sorry, I missread. I thought you were talking about the top level Makefile wipedist target. The distclean in build-root/Makefile looks obsolete. It is I think left over before the most recent refactor of the build system. Was that somehow intentional? It looks broken to me. jdl -- *Thomas F Herbert* Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Question: make realclean
On 05/03/2017 12:23 PM, Jon Loeliger wrote: Naturally, I meant "make distclean" on the Subject: line. :-) distclean removes the tarball created by the "make dist" target. On Wed, May 3, 2017 at 10:20 AM, Jon Loeliger <j...@netgate.com <mailto:j...@netgate.com>> wrote: Hey VPP Builders, Do you ever use "cd build-root; make distclean"? Does it look sort of like this: ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* Fast Data Planes Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] "Jenkins is going to shut down" bar in jenkins webpage
Does anyone know what is meant by the Red Bar in jenkins that says "Jenkins is going to shut down" --Tom -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] vpp-plugins RPM dependency
Damjan, Thanks! On 03/24/2017 12:34 PM, Damjan Marion (damarion) wrote: On 23 Mar 2017, at 14:26, Thomas F Herbert <therb...@redhat.com <mailto:therb...@redhat.com>> wrote: On 03/22/2017 04:36 PM, Feng Pan wrote: So this would suggest that VPP by default (that is, by doing 'yum install vpp') will not have dpdk support, and vpp-plugins must also be installed to add it, I would think dpdk plugin should be either packaged or installed together with VPP by default, and can be disabled if desired. In any case, will deployment model stay this way? I'll need to make changes to puppet module to include other packages if that's how it will be going forward. Also, dpdk section should be commented out in the config file so we can start VPP service using the default config. The dpdk plugin build process precipitated major headaches working for downstream packaging for Centos as well. I had a patch ready to submit for building from a dist tarball as a step toward building from a source rpm but that can't be used now. The main problem is vpp can no longer build from a isolated tarball without git. Out-of-tree build problem is very easily fixable, as I suggested in the review comments.It is unlikely to be more than 10 lines of shell script. Yes, I agree. It turns out to be a minor problem. I have a patch I will soon submit which will fix this. Installing the development rpm as part of downstream installation is not an option either. installation of devel rpm is not mandatory step, you can build vpp without development package installed. Yes, correct. The coming patch will utilize the dpdk tarball for now. The build process does not support dependency on an external rpm yet such as that which is built in rpm_dpdk project. I am thinking out load here but the best option for achieving packaging for 17.04 is to build dpdk from the tarball, bypass the dpdk rpm and include the upstream dpdk tarball in the srpm. Hopefully we can get a better solution figured out by next release over 17.0x that will work with the dpdk plugin concept. I’m not getting what is wrong with current setup, vpp is simple autotools project and packaging is free to invoke “cd src; ./configure; make; make install” as it is done with hundreds of different projects. There is nothing wrong with the current setup. It is an improvement to have DPDK as a plugin. I had to update the script for creating the dist and had to make a few minor changes to the dpdk Makefile that shouldn't affect current builds. -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] 5798: Simple patch to add checking for deps for RPMs
What is the outlook for this patch: https://gerrit.fd.io/r/#/c/5798/ Patch set 2 was submitted on 3/21 to address Damjan's comments. --Tom -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] vpp-plugins RPM dependency
On 03/22/2017 04:36 PM, Feng Pan wrote: So this would suggest that VPP by default (that is, by doing 'yum install vpp') will not have dpdk support, and vpp-plugins must also be installed to add it, I would think dpdk plugin should be either packaged or installed together with VPP by default, and can be disabled if desired. In any case, will deployment model stay this way? I'll need to make changes to puppet module to include other packages if that's how it will be going forward. Also, dpdk section should be commented out in the config file so we can start VPP service using the default config. The dpdk plugin build process precipitated major headaches working for downstream packaging for Centos as well. I had a patch ready to submit for building from a dist tarball as a step toward building from a source rpm but that can't be used now. The main problem is vpp can no longer build from a isolated tarball without git. Installing the development rpm as part of downstream installation is not an option either. The build process does not support dependency on an external rpm yet such as that which is built in rpm_dpdk project. I am thinking out load here but the best option for achieving packaging for 17.04 is to build dpdk from the tarball, bypass the dpdk rpm and include the upstream dpdk tarball in the srpm. Hopefully we can get a better solution figured out by next release over 17.0x that will work with the dpdk plugin concept. Thanks Feng On Wed, Mar 22, 2017 at 2:46 PM, Ed Warnicke <hagb...@gmail.com <mailto:hagb...@gmail.com>> wrote: Commenting out the dpdk stanza is a great workaround but we may want to look at bit more closely at the issue... as installing the vpp project should result in an out of the box runnable vpp. Ed On Wed, Mar 22, 2017 at 11:44 AM, Dave Barach (dbarach) <dbar...@cisco.com <mailto:dbar...@cisco.com>> wrote: Simply remove the “dpdk” stanza from /etc/vpp/startup.conf if you want to run vpp without the dpdk plugin. Thanks… Dave *From:*vpp-dev-boun...@lists.fd.io <mailto:vpp-dev-boun...@lists.fd.io> [mailto:vpp-dev-boun...@lists.fd.io <mailto:vpp-dev-boun...@lists.fd.io>] *On Behalf Of *Feng Pan *Sent:* Wednesday, March 22, 2017 1:47 PM *To:* vpp-dev <vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>> *Subject:* [vpp-dev] vpp-plugins RPM dependency Hi All, With latest master builds of VPP (on Centos with rpm repo), it seems like it's necessary to install vpp-plugins package for vpp to start, without it, I get the following error when running vpp (with default config file): vlib_plugin_early_init:360: plugin path /usr/lib/vpp_plugins vlib_call_all_config_functions: unknown input `dpdk ' Looking at the spec file, vpp package depends on vpp-lib only, so it appears that we need to add vpp-plugins to the dependency list too. However, it also looks like vpp-plugins depends on vpp package, so I'm trying to figure out what the right dependency relationship is :) Thanks Feng ___ vpp-dev mailing list vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> https://lists.fd.io/mailman/listinfo/vpp-dev <https://lists.fd.io/mailman/listinfo/vpp-dev> ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Make pkg-rpm seems to be failing...
Please review: https://gerrit.fd.io/r/#/c/5798/ On 03/20/2017 12:06 PM, Ed Warnicke wrote: Jon, Looking at : https://git.fd.io/vpp/tree/Makefile#n138 In make bootstrap... for deb packages on Ubuntu its checking to see if things are missing and failing fast if they are. I'd suggest we look at doing something similar for rpms. Anyone interested in submitting a patch? Ed On Mon, Mar 20, 2017 at 8:53 AM, Jon Loeliger <j...@netgate.com <mailto:j...@netgate.com>> wrote: Burt and Ole, On Sun, Mar 19, 2017 at 7:26 AM, <otr...@employees.org <mailto:otr...@employees.org>> wrote: Hmm, so https://gerrit.fd.io/r/#/c/5781/ <https://gerrit.fd.io/r/#/c/5781/> isn't sufficient? Necessary, yes. Sufficient? No. On the other hand... On Sun, Mar 19, 2017 at 11:51 AM, Burt Silverman <bur...@gmail.com <mailto:bur...@gmail.com>> wrote: Ugh, I made a terrible bone head mistake... Possibly I never ran make install-dep. Even if I had, I was unaware that it is a good idea to run it again, just to be sure, in a case like this. I probably thought it was like make bootstrap, where running a 2nd time doesn't help. Apologies to Ed and Ole for misinformation. So, Jon, were you in the same boat with me -- didn't do a double check of make install-dep? I guess so, because you still had the problem after Ole's fix. Burt This was precisely the problem here. I'll try to say this as politely as I can... Wow. That's some blind-siding sh*t. So, let's talk about that a bit. First, thank you for identifying the issue! This does indeed fix the build locally, and bring us back to online par. Thank you! Second, the notion of requiring repeated running of the make install-dep target as part of our daily build process from our CI engine is just not going to happen. NFW. We're not running anything has root like that. It's a bad idea for many reasons. On the flip side, I can make a job that "notices" a change in the installed packaged requirement and run that as, say, a daily job and incidentally notice that updates are needed. Sure, polling like that sucks; an interrupt here with a simple "Heads up! The install-deps have changed" would have been awesome! Thanks, jdl ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Make pkg-rpm seems to be failing...
On 03/20/2017 12:06 PM, Ed Warnicke wrote: Jon, Looking at : https://git.fd.io/vpp/tree/Makefile#n138 In make bootstrap... for deb packages on Ubuntu its checking to see if things are missing and failing fast if they are. I'd suggest we look at doing something similar for rpms. Anyone interested in submitting a patch? I will submit the patch as there are other rpm packaging things I am working on. Ed On Mon, Mar 20, 2017 at 8:53 AM, Jon Loeliger <j...@netgate.com <mailto:j...@netgate.com>> wrote: Burt and Ole, On Sun, Mar 19, 2017 at 7:26 AM, <otr...@employees.org <mailto:otr...@employees.org>> wrote: Hmm, so https://gerrit.fd.io/r/#/c/5781/ <https://gerrit.fd.io/r/#/c/5781/> isn't sufficient? Necessary, yes. Sufficient? No. On the other hand... On Sun, Mar 19, 2017 at 11:51 AM, Burt Silverman <bur...@gmail.com <mailto:bur...@gmail.com>> wrote: Ugh, I made a terrible bone head mistake... Possibly I never ran make install-dep. Even if I had, I was unaware that it is a good idea to run it again, just to be sure, in a case like this. I probably thought it was like make bootstrap, where running a 2nd time doesn't help. Apologies to Ed and Ole for misinformation. So, Jon, were you in the same boat with me -- didn't do a double check of make install-dep? I guess so, because you still had the problem after Ole's fix. Burt This was precisely the problem here. I'll try to say this as politely as I can... Wow. That's some blind-siding sh*t. So, let's talk about that a bit. First, thank you for identifying the issue! This does indeed fix the build locally, and bring us back to online par. Thank you! Second, the notion of requiring repeated running of the make install-dep target as part of our daily build process from our CI engine is just not going to happen. NFW. We're not running anything has root like that. It's a bad idea for many reasons. On the flip side, I can make a job that "notices" a change in the installed packaged requirement and run that as, say, a daily job and incidentally notice that updates are needed. Sure, polling like that sucks; an interrupt here with a simple "Heads up! The install-deps have changed" would have been awesome! Thanks, jdl ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] vhost user and upstream dpdk
Damjan, Thanks for your response. My answer is inline below. --TFH On 03/16/2017 02:25 PM, Damjan Marion wrote: On 16 Mar 2017, at 14:24, Thomas F Herbert <therb...@redhat.com <mailto:therb...@redhat.com>> wrote: Do we still have a plan convergence toward upstream DPDK for vhost-user? This has come up in a discussion in this bugz, https://bugzilla.redhat.com/show_bug.cgi?id=1422534 and this patch to vhost_user https://gerrit.fd.io/r/#/c/5700/ --TFH No, we don't have such plans, i don't see a reason why we would invest significant time in adopting 3rd party library if we have own working code. what is your particular concern? DPDK has had a vhost user implementation for quite some time and it is used by other projects built on DPDK. It is generally condidered better to not duplicate similar functionality found in upstream projects. Also, it is far easier for downstream organizations supporting both DPDK/OVS and VPP to have a single code base for an identical functaionality. -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Make pkg-rpm seems to be failing...
On 03/19/2017 12:51 PM, Burt Silverman wrote: Ugh, I made a terrible bone head mistake... Possibly I never ran make install-dep. Even if I had, I was unaware that it is a good idea to run it again, just to be sure, in a case like this. I probably thought it was like make bootstrap, where running a 2nd time doesn't help. Apologies to Ed and Ole for misinformation. So, Jon, were you in the same boat with me -- didn't do a double check of make install-dep? I guess so, because you still had the problem after Ole's fix. Right. epel_rpm_macros are required for the py2_build and th3 py2_install now used for Ole's build changes. Burt On Sun, Mar 19, 2017 at 7:26 AM, <otr...@employees.org <mailto:otr...@employees.org>> wrote: > On 19 Mar 2017, at 05:03, Burt Silverman <bur...@gmail.com <mailto:bur...@gmail.com>> wrote: > > I may have found it. Install python2-rpm-macros from yum. Also install python-rpm-macros. It's looking good. > > Hopefully Ed or Ole can make sure those are part of the install-deps: unlike some other things, these are not so easy to find. Hmm, so https://gerrit.fd.io/r/#/c/5781/ <https://gerrit.fd.io/r/#/c/5781/> isn't sufficient? Best regards, Ole > > Burt > > On Sat, Mar 18, 2017 at 6:10 PM, Jon Loeliger <j...@netgate.com <mailto:j...@netgate.com>> wrote: > > > On Fri, Mar 17, 2017 at 6:33 PM, Burt Silverman <bur...@gmail.com <mailto:bur...@gmail.com>> wrote: > It probably worked during a 12 hour window. I think Neale then made a 2nd change incompatible with the earlier change. > > Burt > > Well, yeah, maybe. But after doing the .end_node dance, > I'm back to the %py2_build problem on a CentOS RPM build > of "make pkg-rpm". > > That's building commit: > > commit 898273fbb588811824bb27ad0ef203d358a7121a > Author: Neale Ranns <nra...@cisco.com <mailto:nra...@cisco.com>> > Date: Sat Mar 18 02:57:38 2017 -0700 > > Check change in unnumbered setting before updating IP enabled state > > Using "make bootstrap; make build-release; make pkg-rpm". > > HTH, > jdl > > > ___ > vpp-dev mailing list > vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> > https://lists.fd.io/mailman/listinfo/vpp-dev <https://lists.fd.io/mailman/listinfo/vpp-dev> ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Problem building from source tarball without git
I have been working on a patch to build a SRPM for downstream packaging but ran into a problem and need more eyes. This is dependent on my earlier patch for building a dist tarball 20a29c7b4d1b5b68112498bee21ee7f3fe123b13 which encapsulates the version metadata in a .version file in build-root/scripts. The version metadata can be determined from within the tarball when there is no git which is done by executing build-root/scripts/version which will work with or without git. See JIRA-498 However, now, this is broken by newer build changes which generates a different .version in build-root/build-vpp-native/vpp and this .version is used to construct the file version.h which is a dependency for the builds to work. I looked at src/vpp.am and it "looks like" the .version target should work because of: VPP_VERSION = $(shell $(srcdir)/scripts/version) but I think that it should check for a non zero exit code from git rev-parse. Steps to reproduce $ cd tmp $ git clone $ cd vpp $ make dist $ cd .. $ xzf ../vpp/build-root/rpm/vpp-17.04-rc0~395_gd96bad8.tar.gz $ cd vpp-17.04 $ make bootstrap $ make build-release ... CC vpp/vnet/bin_vpp-main.o /home/therbert/tmp/dist/vpp-17.04/build-data/../src/vpp/vnet/main.c:21:29: fatal error: vpp/app/version.h: No such file or directory compilation terminated. Full results in https://gist.github.com/tfherbert/3e26ab4ce8989ba35158573ccc641591 Thanks for looking at this. -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Fwd: [Bug 1422534] vdev->vq[i] .used_idx does not consider the right value for vhostuser
Maxime, The OK. Thanks. I am forwarding this to Pierre as he has been working on vhost-user. I thought we were now using dpdk's vhost-user driver as of 17.01. It is interesting how we haven't seen this in our csit testing and we are testing multi-queue. Also will this manifest only on certain revisions of Qemu/KVM? --TFH Forwarded Message Subject: [Bug 1422534] vdev->vq[i] .used_idx does not consider the right value for vhostuser Date: Wed, 08 Mar 2017 08:56:49 + From: bugzi...@redhat.com To: therb...@redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=1422534 --- Comment #27 from Maxime Coquelin--- Tom, I had a look at mainline VPP: $ build-root/scripts/version 17.04-rc0~382-ga0b34a7 Looking at 16.06 release, it seems to be a regression, as the vring struct is not reset before getting last_avail_idx, only the enable bit is cleared: case VHOST_USER_GET_VRING_BASE: DBG_SOCK("if %d msg VHOST_USER_GET_VRING_BASE idx %d num %d", vui->hw_if_index, msg.state.index, msg.state.num); /* Spec says: Client must [...] stop ring upon receiving VHOST_USER_GET_VRING_BASE. */ vui->vrings[msg.state.index].enabled = 0; msg.state.num = vui->vrings[msg.state.index].last_avail_idx; msg.flags |= 4; msg.size = sizeof(msg.state); break; The regression seems to have been introduced by below commit, which landed into v17.01 release: $ git blame src/vnet/devices/virtio/vhost-user.c -L 1031 e21c5286 vnet/vnet/devices/virtio/vhost-user.c (Pierre Pfister 2016-09-21 08:04:59 +0100 1031) vhost_user_vring_close (vui, msg.state.index); $ git show e21c5286 commit e21c52861d7c503bef7fc464f23bbc7891e150d7 Author: Pierre Pfister Date: Wed Sep 21 08:04:59 2016 +0100 vhost-user: multiqueue support This patch adds multi-queue support to non-dpdk's vhost-user driver. Waiting for a unified way to manage threads, this patch defines a way to assign threads to interfaces that is specific to vhost. Change-Id: I86298788b1a4e886c5431f187dc17175d12c7a8b Signed-off-by: Pierre Pfister $ git tag --contains e21c5286 v17.01 v17.01-rc1 v17.01-rc2 v17.01.1 v17.04-rc0 We should invite Pierre Pfister from Cisco in the discussion, as he might have some ideas on the fix to do. I guess that reverting to just clearing the enabled bit is not the right fix. Maybe the vring struct shouldn't be re-initialized in the close function, but should be called directly when needed. I'm attaching a debug patch to confirm the root cause if someone want to have a try. It is not intended to be the fix for this issue, and has not neither been compiled nor tested. Regards, Maxime -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Y79DLPsrVV=cc_unsubscribe ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] fd.io CSIT vhost-user test scenario implementation priorities
Please weigh in: We are starting to plan fd.io CSIT Vhost-user test scenario priorities for implementation in 17.04 and in 17.07 CSIT releases. Vhost-user performance is critical for VNF acceptance in potential use cases for VPP/fd.io adaption. We had previous email thread here: https://lists.fd.io/pipermail/csit-dev/2016-November/001192.html along with a TWS https://wiki.fd.io/view/TWS meetings on 12/02/16 and 12/07/16 summarized in this wiki: https://wiki.fd.io/view/CSIT/vhostuser_test_scenarios Topologies and tests Current in 17.01: 10ge2p1x520-dot1q-l2bdbasemaclrn-eth-2vhost-1vm 10ge2p1x520-dot1q-l2xcbase-eth-2vhost-1vm 10ge2p1x520-ethip4-ip4base-eth-2vhost-1vm 10ge2p1x520-ethip4vxlan-l2bdbasemaclrn-eth-2vhost-1vm 10ge2p1x520-eth-l2bdbasemaclrn-eth-2vhost-1vm 10ge2p1x520-eth-l2xcbase-eth-2vhost-1vm 10ge2p1x710-eth-l2bdbasemaclrn-eth-2vhost-1vm 40ge2p1xl710-eth-l2bdbasemaclrn-eth-2vhost-1vm single and multi-queue testing of pmd baseline Proposed in links above 1p1nic-dot1q-l2bdbase-eth-2vhost-1vm 1p1nic-ethip4vxlan-l2bdbase-eth-2vhost-1vm 1p1nic-dot1q-l2bdbase-eth-4vhost-2vm-chain 1p1nic-ethip4vxlan-l2bdbase-eth-4vhost-2vm-chain 1p1nic-dot1q-l2bdbase-eth-2vhost-1vm-chain-2nodes 1p1nic-ethip4vxlan-l2bdbase-eth-2vhost-1vm-2nodes Proposed topologies for OpenStack from links above: 2p1nic-dot1q-l2bdscale-flows-eth-vhost-vm-chain 2p1nic-ethip4vxlan-l2bdscale-flows-eth-vhost-vm-chain New scenarios Proposed: Primary Overlay vxlan and VTEP 2p1nic-ethip4vxlan-l2bdbase-eth-2vhost-1vm 2p1nic-ethip4vxlan-l2bdbase-eth-20vhost-10vm MPLS over Ethernet Scaling Multiple VMs 2p1nic-dot1q-l2bdbase-eth-20vhost-10vm Workloads: VNF based on Linux relying kernel virtio driver - kernel linux bridge, kernel L3/IPv4 routing IPv4/v6 VPP vRouter Did I leave out anything? ... -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] FW: Re: Interesting perf test results from Red Hat's test team
Hi Danny, My response is inline below. On 02/27/2017 03:01 AM, Zhou, Danny wrote: Hi Tom, Karl, In the last “Todo List” page, there is RFC2544 0% packet loss test item, do you want to measure the min/max latency as well? Is your question particularly about vhost-user testing? Also, I am interested in why you brought up latency. Are you doing your own latency testing in conjunction with your nsh-sfc work and do you think we need to do latency in CSIT as well in testing nsh-sfc perf on vhosts? I will let Karl answer as to the testing he has done and is doing. However, in fd.io CSIT, the latency for vhost-user results are here: https://docs.fd.io/csit/rls1701/report/vpp_performance_tests/packet_latency_graphs/vm_vhost.html --TFH -Danny *From:*vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On Behalf Of *Thomas F Herbert *Sent:* Friday, February 17, 2017 1:55 AM *To:* vpp-dev@lists.fd.io *Cc:* Karl Rister <kris...@redhat.com> *Subject:* Re: [vpp-dev] FW: Re: Interesting perf test results from Red Hat's test team Jan, I have answered below but am forwarding this to Karl who performed the testing to get the exact answers. --TFH On 02/16/2017 08:59 AM, Jan Scheurich wrote: *From:* Jan Scheurich *Sent:* Thursday, 16 February, 2017 14:41 *To:* therb...@redhat.com <mailto:therb...@redhat.com> *Cc:* vpp-...@fd.io <mailto:vpp-...@fd.io> *Subject:* Re: [vpp-dev] Interesting perf test results from Red Hat's test team Hi Thomas, Thanks for these interesting measurements. I am not quite sure I fully understand the different configurations and traffic cases you have been testing: ·*/[Zhou, Danny] /*ToDo you vary the number of vhost-user queues to the guest and/or the number of RX queues for the phy port? These are vhost user queues. Because OVS and/or VPP is running in the host. ·Did you add cores at the same time you added queues? Yes ·When you say flows, do you mean L3/L4 packet flows (5-tuples) or forwarding rules/flow rules? These are L2 matches. ·When you e.g. say N flows (srcip, dstip) do you mean matching on these fields, modifying these fields or both Would it be possible to provide the exact VPP and OVS configurations that were used (ports, queues, cores, ports, forwarding rules/flows)? Thanks, Jan Here are test results on VPP 17.01 compared with OVS/DPDK 2.6/1611 performed by Karl Rister of Red Hat. This is PVP testing with 1, 2 and 3 queues. It is an interesting comparison with the CSIT results. Of particular interest is the drop off on the 3 queue results. --TFH -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* -- next part -- An HTML attachment was scrubbed... URL: <_http://lists.fd.io/pipermail/vpp-dev/attachments/20170215/83249b21/attachment-0001.html_> -- next part -- A non-text attachment was scrubbed... Name: vpp-17.01_vs_ovs-2.6.pdf Type: application/pdf Size: 243918 bytes Desc: not available URL: <_http://lists.fd.io/pipermail/vpp-dev/attachments/20170215/83249b21/attachment-0001.pdf_> ___ vpp-dev mailing list vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Interesting perf test results from Red Hat's test team
On 02/17/2017 06:18 PM, Alec Hothan (ahothan) wrote: Hi Karl Can you also tell which version of DPDK you were using for OVS and for VPP (for VPP is it the one bundled with 17.01?). DPDK 1611 and VPP 1701. “The pps is the bi-directional sum of the packets received back at the traffic generator.” Just to make sure…. If your traffic gen sends 1 Mpps to each of the 2 interfaces and you get no drop (meaning you receive 1 Mpps from each interface). What do you report? 2 Mpps or 4 Mpps? You seem to say 2Mpps (sum of all RX). The CSIT perf numbers report the sum(TX) = in the above example CSIT reports 2 Mpps. The CSIT numbers for 1 vhost/1 VM (practically similar to yours) are at about half of what you report. https://docs.fd.io/csit/rls1701/report/vpp_performance_results_hw/performance_results_hw.html#ge2p1x520-dot1q-l2xcbase-eth-2vhost-1vm-ndrpdrdisc scroll down the table to tc13 tc14, 4t4c (4 threads) L2XC, 64B NDR, 5.95Mpps (aggregated TX of the 2 interfaces) PDR 7.47Mpps. while the results in your slides put it at around 11Mpps. So either your testbed really switches 2 times more packets than the CSIT one, or you’re actually reporting double the amount compared to how CSIT reports it… Thanks Alec *From: *Karl Rister <kris...@redhat.com> *Organization: *Red Hat *Reply-To: *"kris...@redhat.com" <kris...@redhat.com> *Date: *Thursday, February 16, 2017 at 11:09 AM *To: *"Alec Hothan (ahothan)" <ahot...@cisco.com>, "Maciek Konstantynowicz (mkonstan)" <mkons...@cisco.com>, Thomas F Herbert <therb...@redhat.com> *Cc: *Andrew Theurer <atheu...@redhat.com>, Douglas Shakshober <dsh...@redhat.com>, "csit-...@lists.fd.io" <csit-...@lists.fd.io>, vpp-dev <vpp-dev@lists.fd.io> *Subject: *Re: [vpp-dev] Interesting perf test results from Red Hat's test team On 02/15/2017 08:58 PM, Alec Hothan (ahothan) wrote: Great summary slides Karl, I have a few more questions on the slides. · Did you use OSP10/OSPD/ML2 to deploy your testpmd VM/configure the vswitch or is it direct launch using libvirt and direct config of the vswitches? (this is a bit related to Maciek’s question on the exact interface configs in the vswitch) There was no use of OSP in these tests, the guest is launched via libvirt and the vswitches are manually launched and configured with shell scripts. · Unclear if all the charts results were measured using 4 phys cores (no HT) or 2 phys cores (4 threads with HT) Only the slide 3 has any 4 core (no HT) data, all other data is captured using HT on the appropriate number of cores: 2 for single queue, 4 for two queue, and 6 for three queue. · How do you report your pps? ;-) Are those o vswitch centric (how many packets the vswitch forwards per second coming from traffic gen and from VMs) o or traffic gen centric aggregated TX (how many pps are sent by the traffic gen on both interfaces) o or traffic gen centric aggregated TX+RX (how many pps are sent and received by the traffic gen on both interfaces) The pps is the bi-directional sum of the packets received back at the traffic generator. · From the numbers shown, it looks like it is the first or the last · Unidirectional or symmetric bi-directional traffic? symmetric bi-directional · BIOS Turbo boost enabled or disabled? disabled · How many vcpus running the testpmd VM? 3, 5, or 7. 1 VCPU for house keeping and then 2 VCPUs for each queue configuration. Only the required VCPUs are active for any configuration, so the VCPU count varies depending on the configuration being tested. · How do you range the combinations in your 1M flows src/dest MAC? I’m not aware about any real NFV cloud deployment/VNF that handles that type of flow pattern, do you? We increment all the fields being modified by one for each packet until we hit a million and then we restart at the base value and repeat. So all IPs and/or MACs get modified in unison. We actually arrived at the srcMac,dstMac configuration in a backwards manner. On one of our systems where we develop the traffic generator we were getting an error when doing srcMac,dstMac,srcIp,dstIp that we couldn't figure out in the time needed for this work so we were going to just go with srcMac,dstMac due to time constraints. However, on the system where we actually did the testing both worked so I just collected both out of curiosity. Thanks Alec
Re: [vpp-dev] [csit-dev] Fix for vpp-verify-master-ubuntu1604 build failures
the verify jobs that are now in progress. Thanks, -daw- ___ csit-dev mailing list csit-...@lists.fd.io https://lists.fd.io/mailman/listinfo/csit-dev -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Build on Fedora 25 failed
On 01/17/2017 06:03 PM, Kevin Wilson wrote: Hi, Still build fails. After installing redhat-rpm-config, and again wiping out the vpp tree and cloning again from scratch, and running again the process from beginning, first /build-root/vagrant/build.sh which completed ok and then: cd build-root and make V=0 PLATFORM=vpp TAG=vpp install-rpm ... ... make[1]: Leaving directory '/work/src/vpp/build-root' warning: Macro %python2_minor_version defined but not used within scope error: File /work/src/vpp/build-root/rpm/SOURCES/vpp-17.04-rc0~127_gd8e4787.tar.gz: No such file or directory /work/src/vpp/build-data/platforms.mk:107: recipe for target 'install-rpm' failed make: *** [install-rpm] Error 1 ... Any ideas? execute make dist from the top level directory before executing the make command from build-root or just execute make pkg-rpm from the top level directory. Kevin ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] vHost user test scenarios for CSIT - TWS meeting
<mkons...@cisco.com <mailto:mkons...@cisco.com>> wrote: OK, this sounds convincing at least to em. Set for 09:00 - 10:00am PST tomorrow, Friday, 2-Dec. I will set up webex, and advertise it on csit-dev and vpp-dev and on TWS page. Give me an hour or so.. working in PST TZ makes me slower than UK - is it CA air? ;) -Maciek On 1 Dec 2016, at 05:02, Thomas F Herbert <therb...@redhat.com <mailto:therb...@redhat.com>> wrote: On 11/30/2016 08:41 PM, Maciek Konstantynowicz (mkonstan) wrote: All, We didn’t have much time to discuss the vhostuser use cases on CSIT project call earlier today. On the call we also didn’t have all the interested parties that were providing feedback to date. Hence agreed to hold a separate Tech WorkStream call to cover this. Quick check on #fdio-csit irc, this Friday AM PST seems to work for folks. What about 08:00-09:00 PST this Friday? 0900-10:00 PST would be better for me. If yes, I will post meeting details here: https://wiki.fd.io/view/TWS -Maciek On 29 Nov 2016, at 18:53, Thomas F Herbert <therb...@redhat.com <mailto:therb...@redhat.com>> wrote: Maciek, Thanks! --TFH On 11/29/2016 09:27 PM, Maciek Konstantynowicz (mkonstan) wrote: All, Here is the first draft: https://wiki.fd.io/view/CSIT/vhostuser_test_scenarios <https://wiki.fd.io/view/CSIT/vhostuser_test_scenarios> I did my best to capture all inputs as per this thread. But it’s hardly readable yet - requires more TLC :) See what you think - feel free to add/edit things directly on FD.io <http://fd.io/> wiki page. Suggest to discuss next steps on csit weekly call tomorrow, details here: https://wiki.fd.io/view/CSIT/Meeting <https://wiki.fd.io/view/CSIT/Meeting> -Maciek On 28 Nov 2016, at 07:37, Thomas F Herbert <therb...@redhat.com <mailto:therb...@redhat.com>> wrote: All, At last week's CSIT meeting, Maciek (mkons...@cisco.com <mailto:mkons...@cisco.com>) offered to compile a summary suggestions on this mailing list. On 11/22/2016 11:34 AM, Pierre Pfister (ppfister) wrote: Hello Thomas, Sorry I haven't reached out faster, I was travelling. Please have a look at vppsb/vhost-test It includes a standalone script which provides VPP and VM configuration for PVP tests. - Runs testpmd in the VM - Supports various CPU configuration for VPP - Can run with or without gdb, debug or release Not committed yet: - Supports VM restart - Support for VPP restart - Support for multiple additional (dead) vhost interface I did that outside of the context of CSIT so people can: - Look at it and see what are the optimisations that are used - Use it without CSIT I will keep using and improving it because I use it for my own development and testing purposes. Rest of this inline. Le 8 nov. 2016 à 22:25, Thomas F Herbert <therb...@redhat.com <mailto:therb...@redhat.com>> a écrit : All: Soliciting opinions from people as to vhost-user testing scenarios and guest modes in fd.io <http://fd.io/> CSIT testing of VPP - vhost-user. I will forward to this mailing list as well as summarize any additional feedback. I asked some people that happen to be here at OVSCON as well as some Red Hat and Intel people. I am also including some people that are involved in upstream vhost-user work in DPDK. So far, I have the following feedback with an attempt to condense feedback and to keep the list small. If I left out anything, let me know. In addition to the PVP tests done now with small packets. Testpmd in guest is OK for now. 1 Add multiple VMs (How many?) Makes sense to me. 2 is enough (4 would be good number). 2 Both multi-queue and single-queue Yes. Ideally, 1-2-4 queues. With different number of workers (0 workers, i.e. single VPP thread, 1 worker, queues*2 workers). 3 Tests that cause the equivalent of multiple flows in OVS. Varying variety of traffic including layer 2 and layer 3 traffic. Yes. Should test with L2 and L3. 4 Multiple IF's (Guest or Host or Both?) Possibly. But more importantly, I think, we need to have VM restart and interface restart (delete - create). OpenStack integration generates a significant amount of delete-recreate of vhost interface. The following might not be doable by 17.01 and if not consider the following as a wish list for future: 1 vxLan tunneled traffic 2 VPP in guest with layer 2 and layer 3 vRouted traffic. 3 Additional Overlay/Underlay: MPLS --TFH -- *Thomas F Herbert* SDN Group Office of Technology *Red Hat* __