Re: [vpp-dev] VNET Device Drivers; increased memory footprint for af_packet v3

2023-03-21 Thread Laszlo Király 
Hi,

Excuse me for the misunderstanding. Most probably this is not an issue in VPP. 
In the mentioned 'previous version of vpp (git version 45207e0fb2) the 
af_packet_create_v2 api was used, so the memory increase is expected.
So, the question had lapsed.

/Laszlo


From: Laszlo Király
Sent: Tuesday, March 21, 2023 10:58 AM
To: vpp-dev@lists.fd.io 
Subject: VNET Device Drivers; increased memory footprint for af_packet v3

Hello fellow VPP developers!

I experienced an increase in memory allocation related to af_packet v3.
VPP is built from source from git version: e416893a5. The AF_PACKET interface 
is created by the go bin-api call AfPacketCreateV3 (invoking 
af_packet_create_v3 api call in VPP).
The amount of memory assigned to an af_packet socket appears to be 135MB per 
af_packet socket. In VPP based on git version 45207e0fb2 the memory assigned to 
an af_packet socket was around 20MB.

Is this memory allocation increase intentional? If not is it a known issue? Any 
workaround or patch exist (if it is a bug and it was fixed)?

Thanks in advance,
Laszlo

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

[vpp-dev] VNET Device Drivers; increased memory footprint for af_packet v3

2023-03-21 Thread Laszlo Király 
Hello fellow VPP developers!

I experienced an increase in memory allocation related to af_packet v3.
VPP is built from source from git version: e416893a5. The AF_PACKET interface 
is created by the go bin-api call AfPacketCreateV3 (invoking 
af_packet_create_v3 api call in VPP).
The amount of memory assigned to an af_packet socket appears to be 135MB per 
af_packet socket. In VPP based on git version 45207e0fb2 the memory assigned to 
an af_packet socket was around 20MB.

Is this memory allocation increase intentional? If not is it a known issue? Any 
workaround or patch exist (if it is a bug and it was fixed)?

Thanks in advance,
Laszlo

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

Re: [vpp-dev] periodical build failure of external dependency ipsec-mb

2023-02-14 Thread Laszlo Király 
Thank for the explanation, I will check it next time when pops up. If the 
mentioned problem identified, we will increase the memory for the worker node 
where the build is running.

Regards,
Laszlo

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

[vpp-dev] periodical build failure of external dependency ipsec-mb

2023-02-13 Thread Laszlo Király 
Hello,

Time to time our automated build fails during ipsec-mb external dependency. It 
is not a constant failure, usually passing for second run.
The failure have been seen on vpp versions  22.06 and 22.04.

--- building ipsec-mb 1.1 - log: /vpp/build/external/rpm/tmp/ipsec-mb.build.log
make[4]: *** [Makefile:791: obj/aes256_gcm_by48_api_vaes_avx512.o] Killed

Seems to me like the nasm (nasm 2.14.02) target is not ready when the gcc tries 
to use it as source. It can be some nasty dependency or timing issue in 
ipsec-mb build.

Did you faced similar phenomenon?

--
Thanks,
Laszlo Kiraly


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

[vpp-dev] way to report security vulnerabilities

2023-01-24 Thread Laszlo Király 
Hello fellow developers,

Could you please point me to some description of how to report security 
vulnerability on vpp? This time I do not have any, just for documentation 
purposes.

Regards/Laszlo Kiraly


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

Re: [vpp-dev] testing vpp question

2022-09-26 Thread Laszlo Király 
Hello,

I was using an unstable base version, but it's fine now.
Thanks for the advise,
Laszlo

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

[vpp-dev] testing vpp question

2022-09-23 Thread Laszlo Király 
Hi,
Could someone please advise me how to run vpp tests?

I followed the instructions described in developer documentation 
https://s3-docs.fd.io/vpp/22.10/developer/build-run-debug/index.html
I also checked the following Jenkins job configuration:  
https://jenkins.fd.io/job/vpp-verify-master-ubuntu2004-x86_64/configure
Based on this I created a Dockerfile to build and test vpp on ubuntu 20.04:

cat extras/docker/build/Dockerfile.ubuntu-20-04
FROM ubuntu:20.04 as vppbuildandtest
RUN apt-get update
RUN DEBIAN_FRONTEND=noninteractive TZ=US/Central apt-get install -y git make 
python3 sudo asciidoc
COPY . /vpp
WORKDIR /vpp
RUN curl -s 
https://packagecloud.io/install/repositories/fdio/${REPO}/script.deb.sh |  bash
RUN apt-get update
RUN apt-get -y --allow-downgrades --allow-remove-essential 
--allow-change-held-packages install vpp-ext-deps
RUN DEBIAN_FRONTEND=noninteractive TZ=US/Central UNATTENDED=y make install-dep
RUN make UNATTENDED=yes test-dep
RUN make UNATTENDED=yes pkg-verify
RUN src/tools/vppapigen/test_vppapigen.py
RUN make UNATTENDED=yes test

Until now I was able to run without errors, but the last several attempts 
failed with the failure:

 Running setup.py develop for vpp-papi
ERROR: Command errored out with exit status 1:
 command: /usr/bin/python3 -c 'import sys, setuptools, tokenize; 
sys.argv[0] = '"'"'/vpp/src/vpp-api/python/setup.py'"'"'; 
__file__='"'"'/vpp/src/vpp-api/python/setup.py'"'"';f=getattr(tokenize, 
'"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', 
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' develop 
--no-deps
 cwd: /vpp/src/vpp-api/python/
Complete output (17 lines):
running develop
error: can't create or remove files in install directory

The following error occurred while trying to add or remove files in the
installation directory:

[Errno 2] No such file or directory: 
'/usr/lib/python3.8/site-packages/test-easy-install-112.write-test'

Tried to fix the error adding the required directory 
'/usr/lib/python3.8/site-packages/', but other python modules missing.
After installing 'psutil' and 'scapy' now facing another failure:

make -C test VPP_BUILD_DIR=/vpp/build-root/build-vpp-native/vpp 
VPP_BIN=/vpp/build-root/install-vpp-native/vpp/bin/vpp 
VPP_INSTALL_PATH=/vpp/build-root/install-vpp-native/ EXTENDED_TESTS= PYTHON= 
OS_ID=ubuntu RND_SEED= CACHE_OUTPUT= TAG=vpp test
make[1]: Entering directory '/vpp/test'
Traceback (most recent call last):
  File "/vpp/test/run_tests.py", line 17, in 
from framework import (
  File "/vpp/test/framework.py", line 35, in 
from vpp_papi_provider import VppPapiProvider
  File "/vpp/test/vpp_papi_provider.py", line 231, in 
class VppPapiProvider(object):
  File "/vpp/test/vpp_papi_provider.py", line 983, in VppPapiProvider
protocol=socket.IPPROTO_RAW,
NameError: name 'socket' is not defined


/Laszlo

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

Re: [vpp-dev] opensuse uplift

2022-09-07 Thread Laszlo Király 
Hi,
The correct link to FDio gerrit: https://gerrit.fd.io/r/c/vpp/+/37067
--
Laszlo Kiraly

From: Laszlo Király
Sent: Tuesday, September 6, 2022 6:50 PM
To: vpp-dev@lists.fd.io 
Subject: opensuse uplift

Hello devs,
<https://gerrit.nordix.org/c/fdio/vpp/+/14826>
It's just a notice, that I reworked a minor fix for build on openSUSE. Excuse 
me if I confused the reviewer with my updates on this commit.
The link for gerrit review: https://gerrit.nordix.org/c/fdio/vpp/+/14826

--
Laszlo Kiraly

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

[vpp-dev] opensuse uplift

2022-09-06 Thread Laszlo Király 
Hello devs,

It's just a notice, that I reworked a minor fix for build on openSUSE. Excuse 
me if I confused the reviewer with my updates on this commit.
The link for gerrit review: https://gerrit.nordix.org/c/fdio/vpp/+/14826

--
Laszlo Kiraly

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

Re: [vpp-dev] vlan tag rewrite failure on traffic (other side is a kernel vlan interface)

2022-01-17 Thread Laszlo Király 
Hello,

It turned out that the problem was caused by the checksum offload set on 
virtual interfaces on the sender side.
The workaround is to set the following on host A:
docker exec rvm-tester ethtool -K eth0 tx off

So, it's definitely NOT a vpp fault. Sorry for bothering you with this issue.

--
Regards,
Laszlo Kiraly


From: Laszlo Király
Sent: Tuesday, January 11, 2022 4:31 PM
To: vpp-dev@lists.fd.io 
Subject: vlan tag rewrite failure on traffic (other side is a kernel vlan 
interface)

Hello,

I am facing a problem using VLAN tag rewrite functionality on VPP.

The communication between a kernel vlan interface and a VPP VLAN sub-interface 
fails. The ICMP is working but TCP/UDP packets are dropped by the kernel (just 
one side - see the test description)

Find attached the detailed topology, test details, the reproduction 
instructions, vpp version and 'show' commands output and tcpdump capture files 
as well.

Please advise me with the way forward:
- It can be a configuration problem - what should be changed?
- Might be a fault in kernel checksum (has a low chance, but can happen)
- Can be a fault in VPP tag rewrite - can I raise a ticket? Do you need 
additional information?


1. Network Topology
 See attached file: topo.txt

2. Test Description

The 'Host A' should reach the 'Host B' by eth1.100 and respectively veth1 
interfaces. The 'ping' works, but when trying to establish a TCP connection 
(ncat/iperf) the connection fails.
2/A Client is on 'Host A'
Based on captured trace the SYN arrives to veth1 but it is dropped and does 
not reach the server listening on 'host B', 'orange' nw namespace.

2/B Client is on 'Host B', 'orange' namespace
Based on trace the SYN is received and replied by the server on 'Host A'. 
The SYN ACK can be seen in tcpdump, but dropped by the kernel.

Seems that the case when VPP adding VLAN tag to the packet is working but when 
removing the VLAN tag from the packet the kernel drops the packet.

Based on kernel statistics the TcpInCsumErrors counter increasing, however the 
VLAN is on ethernet level.

3. Reproduction Steps

See attached file: test-vtr-tcpfailure.txt

4. VPP Version and 'show' Command Outputs

See attached file: test-vtr-cmds.txt

5. Capture Files

Tcpdump captures:
ext-in-tcp-failure-sut-eth1.pcap
ext-in-tcp-failure-sut-veth1.pcap
ext-in-tcp-failure-tester.pcap
out-tcp-failure-sut-eth1.pcap
out-tcp-failure-sut-veth1.pcap
out-tcp-failure-tester.pcap

--
Laszlo Kiraly

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

[vpp-dev] vlan tag rewrite failure on traffic (other side is a kernel vlan interface)

2022-01-11 Thread Laszlo Király 
Hello,

I am facing a problem using VLAN tag rewrite functionality on VPP.

The communication between a kernel vlan interface and a VPP VLAN sub-interface 
fails. The ICMP is working but TCP/UDP packets are dropped by the kernel (just 
one side - see the test description)

Find attached the detailed topology, test details, the reproduction 
instructions, vpp version and 'show' commands output and tcpdump capture files 
as well.

Please advise me with the way forward:
- It can be a configuration problem - what should be changed?
- Might be a fault in kernel checksum (has a low chance, but can happen)
- Can be a fault in VPP tag rewrite - can I raise a ticket? Do you need 
additional information?


1. Network Topology
 See attached file: topo.txt

2. Test Description

The 'Host A' should reach the 'Host B' by eth1.100 and respectively veth1 
interfaces. The 'ping' works, but when trying to establish a TCP connection 
(ncat/iperf) the connection fails.
2/A Client is on 'Host A'
Based on captured trace the SYN arrives to veth1 but it is dropped and does 
not reach the server listening on 'host B', 'orange' nw namespace.

2/B Client is on 'Host B', 'orange' namespace
Based on trace the SYN is received and replied by the server on 'Host A'. 
The SYN ACK can be seen in tcpdump, but dropped by the kernel.

Seems that the case when VPP adding VLAN tag to the packet is working but when 
removing the VLAN tag from the packet the kernel drops the packet.

Based on kernel statistics the TcpInCsumErrors counter increasing, however the 
VLAN is on ethernet level.

3. Reproduction Steps

See attached file: test-vtr-tcpfailure.txt

4. VPP Version and 'show' Command Outputs

See attached file: test-vtr-cmds.txt

5. Capture Files

Tcpdump captures:
ext-in-tcp-failure-sut-eth1.pcap
ext-in-tcp-failure-sut-veth1.pcap
ext-in-tcp-failure-tester.pcap
out-tcp-failure-sut-eth1.pcap
out-tcp-failure-sut-veth1.pcap
out-tcp-failure-tester.pcap

--
Laszlo Kiraly
+---+
| host-eth0.100 |--x l2 xconnect
| POP 1 |  |
+---+ ++
| host-eth0 | | host-veth0 |
+---+ ++ VPP
___
+--+ 172.10.0.253  +-+  +---++---+  kernel
| eth1.100 |---| eth0|  | veth0 || veth1 |
+--+   +-+  +---++---+
| eth1 |  172.10.0.1
+--+

Host A Host B (VPP L2 pipe and VLAN tag rewrite)
eth1.100 kernel vlan i/f   eth0 kernel interface
   veth0, veth1 veth interfaces
   veth1 in 'orange' network namespace
# Create the network
docker network create bridge-2

# Create and set up the rvm-tester container
cat Dockerfile << EOF
FROM networkstatic/iperf3

RUN apt-get update \
&& apt-get install -y tcpdump ncat telnet procps psmisc\
&& rm -rf /var/lib/apt/lists/*

ENTRYPOINT [ "tail", "-f", "/dev/null" ]
EOF
docker pull networkstatic/iperf3
docker build . -tag rvm-tester:latest
rm Dockerfile
docker run --cap-add=NET_ADMIN --rm -d --network bridge-2 -v 
/tmp/tcpdump:/tmp/tcpdump --name rvm-tester rvm-tester:latest tail -f /dev/null
docker exec rvm-tester ip link set eth0 down
docker exec rvm-tester ip link add link eth0 name eth0.100 type vlan id 100
docker exec rvm-tester ip link set eth0 up
docker exec rvm-tester ip addr add 172.10.0.253/24 dev eth0.100

# Get the image and run vpp in docker container
docker pull ghcr.io/edwarnicke/govpp/vpp:v22.02-rc0-165-gb44d0defb
docker run --privileged --rm -d --network bridge-2 -v /tmp/tcpdump:/tmp/tcpdump 
--name vpp-sut ghcr.io/edwarnicke/govpp/vpp:v22.02-rc0-165-gb44d0defb tail -f 
/dev/null

# Create vpp config
cat > vpp.conf << EOF
unix {
  nodaemon
  log /var/log/vpp/vpp.log
  full-coredump
  cli-listen /var/run/vpp/cli.sock
  gid vpp
}

buffers {
buffers-per-numa 32768
default data-size 3776
}

api-trace {
  on
}

api-segment {
  gid vpp
}

socksvr {
  socket-name /var/run/vpp/api.sock
}

statseg {
  socket-name /var/run/vpp/stats.sock
}

cpu {
}

plugins {
plugin dpdk_plugin.so { disable }
}
EOF

# Copy vpp config to container
docker cp vpp.conf vpp-sut:/etc/vpp/vpp.conf
rm vpp.conf

# install additional tools
docker exec vpp-sut apt update
docker exec vpp-sut apt install -y ncat jq

# Set the network inside the container
docker exec vpp-sut ip netns add orange
docker exec vpp-sut ip link add veth0 type veth peer name veth1
docker exec vpp-sut ip addr add 192.168.111.1/24 dev veth0
docker exec vpp-sut ip link set veth0 up
docker exec vpp-sut ip link set veth1 netns orange
docker exec vpp-sut ip netns exec orange ip

Re: [vpp-dev] Reason for removing SUSE packaging support

2021-11-18 Thread Laszlo Király 
Hello Ben,

Thanks for the feedback. I did the update based on your comments: 
https://gerrit.fd.io/r/c/vpp/+/34357
Can I ask for a review?

--
Laszlo


From: Benoit Ganne (bganne) 
Sent: Friday, November 5, 2021 6:17 PM
To: Laszlo Király ; vpp-dev@lists.fd.io 

Subject: RE: [vpp-dev] Reason for removing SUSE packaging support

Hi Laszlo,

Thanks! A few comments:
 - I think it would be easier to just merge both patches
 - I would put the Dockerfile under extras/rpm instead of a dedicated 
directory, alongside a small README to explain how to use it for testing
 - you should add yourself in MAINTAINERS as the maintainer for rpm packaging. 
A maintainer duty is to review patches on its subsystem (rpm packaging in your 
case) in gerrit and +1 if they are ready for merging so a committer can merge 
them, and to answer/fix issues when reported

Best
ben

> -Original Message-
> From: Laszlo Király 
> Sent: vendredi 5 novembre 2021 15:56
> To: vpp-dev@lists.fd.io
> Cc: Benoit Ganne (bganne) 
> Subject: Re: [vpp-dev] Reason for removing SUSE packaging support
>
> Hello,
>
> I pushed the patches for providing support to build vpp on opensuse leap:
> https://gerrit.fd.io/r/c/vpp/+/34356
>
> https://gerrit.fd.io/r/c/vpp/+/34357
>
> The rpm build can be tried out by the provided docker manifest file:
>  docker build -f extras/docker/build/Dockerfile.opensuse .
>
>
> Could you give me some advice how to continue with this? Can I add someone
> as a reviewer?
> --
> Laszlo
>
> 
>
> From: Benoit Ganne (bganne) 
> Sent: Monday, July 26, 2021 10:08 AM
> To: Laszlo Király 
> Cc: vpp-dev@lists.fd.io 
> Subject: RE: [vpp-dev] Reason for removing SUSE packaging support
>
> If you provide patches and volunteer to be the maintainer that would be
> great. The main request is to be reactive on the code you maintain (answer
> users and/or bug reports).
> You can start by submitting patches and an entry in MAINTAINERS.
> I suspect the best would be to have extras/rpm/centos/ and
> extras/rpm/suse/ but I am no expert.
>
> Best
> ben
>
> > -Original Message-
> > From: vpp-dev@lists.fd.io  On Behalf Of Laszlo
> Király
> > Sent: lundi 26 juillet 2021 08:35
> > To: Damjan Marion 
> > Cc: vpp-dev@lists.fd.io
> > Subject: Re: [vpp-dev] Reason for removing SUSE packaging support
> >
> > Thanks for the clarification.
> > Currently we are building the vpp in SUSE environment and probably must
> be
> > maintained in the long term. If I would like to contribute to build
> > support for opensuse-leap which are the expectations? Are there any
> other
> > todos beside the update of documentation and build scripts?
> >
> > --
> > Laszlo Kiraly
> > Ericsson Software Technology
> > laszlo.kir...@est.tech
> >
> > 
> >
> > From: Damjan Marion 
> > Sent: Monday, July 19, 2021 12:08 PM
> > To: Laszlo Király 
> > Cc: vpp-dev@lists.fd.io 
> > Subject: Re: [vpp-dev] Reason for removing SUSE packaging support
> >
> >
> > Simply because there was nobody interested to volunteer to maintain it.
> >
> > -
> > Damjan
> >
> >
> >
> >
> >On 19.07.2021., at 12:04, Laszlo Király 
> > wrote:
> >
> >
> >
> >
> >Hello,
> >
> >Could somebody evolve why the build support for Suse was removed?
> >Which was the last release with support for build on openSuse?  I
> > found this commit only mentioning this removal:
> >
> >commit bc35f469c89daf0126937580b6972516b5007d3a
> >Author: Dave Wallace 
> >Date:   Fri Sep 18 15:35:01 2020 +
> >
> >build: remove opensuse build infra
> >
> >- VPP on opensuse has not been supported
> >  for several releases.
> >
> >Type: fix
> >
> >Signed-off-by: Dave Wallace 
> >Change-Id: I2b5316ad5c20a843b8936f4ceb473f932a5338d9
> >
> >
> >
> >Is it planned to add it back soon? Or later?
> >
> >--
> >Laszlo Kiraly
> >Ericsson Software Technology
> >
> >laszlo.kir...@est.tech
> >
> >
> >
> >
>


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20512): https://lists.fd.io/g/vpp-dev/message/20512
Mute This Topic: https://lists.fd.io/mt/84304700/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] Reason for removing SUSE packaging support

2021-11-05 Thread Laszlo Király 
Hello,

I pushed the patches for providing support to build vpp on opensuse leap:
https://gerrit.fd.io/r/c/vpp/+/34356
https://gerrit.fd.io/r/c/vpp/+/34357
The rpm build can be tried out by the provided docker manifest file:
 docker build -f extras/docker/build/Dockerfile.opensuse .

Could you give me some advice how to continue with this? Can I add someone as a 
reviewer?
--
Laszlo


From: Benoit Ganne (bganne) 
Sent: Monday, July 26, 2021 10:08 AM
To: Laszlo Király 
Cc: vpp-dev@lists.fd.io 
Subject: RE: [vpp-dev] Reason for removing SUSE packaging support

If you provide patches and volunteer to be the maintainer that would be great. 
The main request is to be reactive on the code you maintain (answer users 
and/or bug reports).
You can start by submitting patches and an entry in MAINTAINERS.
I suspect the best would be to have extras/rpm/centos/ and extras/rpm/suse/ but 
I am no expert.

Best
ben

> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of Laszlo Király
> Sent: lundi 26 juillet 2021 08:35
> To: Damjan Marion 
> Cc: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Reason for removing SUSE packaging support
>
> Thanks for the clarification.
> Currently we are building the vpp in SUSE environment and probably must be
> maintained in the long term. If I would like to contribute to build
> support for opensuse-leap which are the expectations? Are there any other
> todos beside the update of documentation and build scripts?
>
> --
> Laszlo Kiraly
> Ericsson Software Technology
> laszlo.kir...@est.tech
>
> 
>
> From: Damjan Marion 
> Sent: Monday, July 19, 2021 12:08 PM
> To: Laszlo Király 
> Cc: vpp-dev@lists.fd.io 
> Subject: Re: [vpp-dev] Reason for removing SUSE packaging support
>
>
> Simply because there was nobody interested to volunteer to maintain it.
>
> —
> Damjan
>
>
>
>
>On 19.07.2021., at 12:04, Laszlo Király 
> wrote:
>
>
>
>
>Hello,
>
>Could somebody evolve why the build support for Suse was removed?
>Which was the last release with support for build on openSuse?  I
> found this commit only mentioning this removal:
>
>commit bc35f469c89daf0126937580b6972516b5007d3a
>Author: Dave Wallace 
>Date:   Fri Sep 18 15:35:01 2020 +
>
>build: remove opensuse build infra
>
>- VPP on opensuse has not been supported
>  for several releases.
>
>Type: fix
>
>Signed-off-by: Dave Wallace 
>Change-Id: I2b5316ad5c20a843b8936f4ceb473f932a5338d9
>
>
>
>Is it planned to add it back soon? Or later?
>
>--
>Laszlo Kiraly
>Ericsson Software Technology
>
>laszlo.kir...@est.tech
>
>
>
>


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20437): https://lists.fd.io/g/vpp-dev/message/20437
Mute This Topic: https://lists.fd.io/mt/84304700/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] Reason for removing SUSE packaging support

2021-07-26 Thread Laszlo Király 
Thanks for the clarification.
Currently we are building the vpp in SUSE environment and probably must be 
maintained in the long term. If I would like to contribute to build support for 
opensuse-leap which are the expectations? Are there any other todos beside the 
update of documentation and build scripts?

--
Laszlo Kiraly
Ericsson Software Technology
laszlo.kir...@est.tech


From: Damjan Marion 
Sent: Monday, July 19, 2021 12:08 PM
To: Laszlo Király 
Cc: vpp-dev@lists.fd.io 
Subject: Re: [vpp-dev] Reason for removing SUSE packaging support


Simply because there was nobody interested to volunteer to maintain it.

—
Damjan


On 19.07.2021., at 12:04, Laszlo Király  wrote:


Hello,

Could somebody evolve why the build support for Suse was removed?
Which was the last release with support for build on openSuse?  I found this 
commit only mentioning this removal:

commit bc35f469c89daf0126937580b6972516b5007d3a
Author: Dave Wallace 
Date:   Fri Sep 18 15:35:01 2020 +

build: remove opensuse build infra

- VPP on opensuse has not been supported
  for several releases.

Type: fix

Signed-off-by: Dave Wallace 
Change-Id: I2b5316ad5c20a843b8936f4ceb473f932a5338d9


Is it planned to add it back soon? Or later?

--
Laszlo Kiraly
Ericsson Software Technology
laszlo.kir...@est.tech




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

[vpp-dev] Reason for removing SUSE packaging support

2021-07-19 Thread Laszlo Király 
Hello,

Could somebody evolve why the build support for Suse was removed?
Which was the last release with support for build on openSuse?  I found this 
commit only mentioning this removal:

commit bc35f469c89daf0126937580b6972516b5007d3a
Author: Dave Wallace 
Date:   Fri Sep 18 15:35:01 2020 +

build: remove opensuse build infra

- VPP on opensuse has not been supported
  for several releases.

Type: fix

Signed-off-by: Dave Wallace 
Change-Id: I2b5316ad5c20a843b8936f4ceb473f932a5338d9


Is it planned to add it back soon? Or later?

--
Laszlo Kiraly
Ericsson Software Technology
laszlo.kir...@est.tech

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