I rechecked this patch twice, and it built successfully now.
But why need to recheck twice?
-Hongjun
From: Ole Troan [mailto:otr...@employees.org]
Sent: Friday, January 26, 2018 2:53 PM
To: Ni, Hongjun
Cc: Dave Barach (dbarach) ; Marco Varlese
; Gabriel Ganne ; Billy McFall
; Damjan Marion (d
Hi Hongjun,
> I have no OpenSUSE at hand, and could not give it a try.
Neither do I.
Ole
>
> From: Ole Troan [mailto:otr...@employees.org]
> Sent: Friday, January 26, 2018 2:08 PM
> To: Ni, Hongjun
> Cc: Dave Barach (dbarach) ; Marco Varlese
> ; Gabriel Ganne ; Billy McFall
> ; Damjan M
Hi Ole,
I have no OpenSUSE at hand, and could not give it a try.
-Hongjun
From: Ole Troan [mailto:otr...@employees.org]
Sent: Friday, January 26, 2018 2:08 PM
To: Ni, Hongjun
Cc: Dave Barach (dbarach) ; Marco Varlese
; Gabriel Ganne ; Billy McFall
; Damjan Marion (damarion) ; vpp-dev
Subjec
Hongjun,
This looks suspect:
03:32:31 APIGEN vlibmemory/memclnt.api.h 03:32:31 JSON API
vlibmemory/memclnt.api.json 03:32:31 SyntaxError: invalid syntax
(vppapigentab.py, line 11) 03:32:31
WARNING:vppapigen:/w/workspace/vpp-verify-master-opensuse/build-root/rpmbuild/BUILD/vpp-18.04/build-data/.
Hi all,
It seems that OpenSUSE build failed for this patch:
https://jenkins.fd.io/job/vpp-verify-master-opensuse/1285/console
Please help to take a look at it. Thanks a lot.
Thanks,
Hongjun
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Dave Barach (dbarac
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 aro
'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 afte
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 starting with release 17.10
https://nexus.fd.io/content/repositories/fd.io.stable.1707.centos7/io/fd/vp
Ole Troan schrieb am Do., 25. Jan. 2018 um 22:07 Uhr:
> > Not accepting IP[46] packets on any interface type that is not IP[46]
> enabled is a basic security feature. To IP4 enable an interface you have
> two option;
> > 1) Assign it an IP address
> > 2) Make it IP unnumbered to anoth
> Not accepting IP[46] packets on any interface type that is not IP[46] enabled
> is a basic security feature. To IP4 enable an interface you have two option;
> 1) Assign it an IP address
> 2) Make it IP unnumbered to another interface that does have an
> address, e.g.
> set int ip ad
Congratulations, way to go.
From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io] On
Behalf Of Dave Wallace
Sent: Wednesday, January 24, 2018 9:23 PM
To: vpp-dev@lists.fd.io; csit-...@lists.fd.io
Subject: [csit-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io
Hi Andrea,
Typically a tunnel used for tx/rx of L3/IP payload would have IP address and
optionally table-id set on the interface. It will then allow packets to be
routed into the tunnel for tx and, for rx packets, forward the payload IP
packets using the correct fib-index.
I see that you are
Hi Andreas,
Not accepting IP[46] packets on any interface type that is not IP[46] enabled
is a basic security feature. To IP4 enable an interface you have two option;
1) Assign it an IP address
2) Make it IP unnumbered to another interface that does have an address,
e.g.
set int ip
Hi,
Short story:
The VPP tunnel implementation HOWTO [1] says that a L3 tunnel needs an IP
address. How do I implement a P2P tunnel interface without assigning an IP
address to it?
Long story:
I'm implementing a GTP-U User Plane Node that conforms to 3GPP TS 29.244
[2] & [3]. For each Sx Sessio
Hi Charlie,
Please see this preso and associated paper from Kubecon - it is a pretty
comprehensive guide on where to start.
https://wiki.fd.io/images/3/31/Benchmarking-sw-data-planes-Dec5_2017.pdf
Also consider replicating the CSIT test environment locally.
It is very well documented and you
On Jan 25, 2018, at 12:59 AM, Marco Varlese
mailto:mvarl...@suse.de>> wrote:
Hi Ed,
On Thu, 2018-01-25 at 00:28 +, Ed Kern (ejk) wrote:
hey marco,
What your looking for (imo) is not a gerrit change. Its a jenkins side change
https://gerrit.fd.io/r/10237
Thank you for showing the path; I
W00t!
On 25/01/2018 05:23, Dave Wallace wrote:
Folks,
The VPP 18.01 Release artifacts are now available on nexus.fd.io
The ubuntu.xenial and centos packages can be installed following the
recipe on the wiki:
https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages
Thank you to all
Congrats to DaveW and the rest of the fd.io vpp team on the 18.01 release!
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Dave Wallace
Sent: Thursday, January 25, 2018 12:23 AM
To: vpp-dev@lists.fd.io; csit-...@lists.fd.io
Subject: [vpp-dev] VPP 18.01 Release
Congratulations!
De : au nom de Dave Wallace
Date : mercredi 24 janvier 2018 à 21:23
À : "vpp-dev@lists.fd.io" , "csit-...@lists.fd.io"
Objet : [vpp-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io
Folks,
The VPP 18.01 Release artifacts are now available on nexus.fd.io
The
Great news! Congrats everybody!!!
On Thu, 2018-01-25 at 00:23 -0500, Dave Wallace wrote:
>
> Folks,
>
>
>
> The VPP 18.01 Release artifacts are now available on nexus.fd.io
>
>
>
> The ubuntu.xenial and centos packages can be installed following
> the recipe
Woohoo!
From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io] On
Behalf Of Dave Wallace
Sent: Thursday, January 25, 2018 0:23
To: vpp-dev@lists.fd.io; csit-...@lists.fd.io
Subject: [csit-dev] VPP 18.01 Release artifacts are now available on nexus.fd.io
Folks,
The VPP 18.01 Re
21 matches
Mail list logo