Re: [vpp-dev] Trying to build vpp on amd64 platform via qemu static library qemu-aarch64-static in Docker container

2018-04-25 Thread Brian Brooks
Thanks, Ole. Stanislav, does this help? Are you able to natively compile on arm64 instead of cross? Brian -Original Message- From: Ole Troan Sent: Wednesday, April 25, 2018 11:56 AM To: Brian Brooks Cc: Stanislav Chlebec

Re: [vpp-dev] [csit-dev] VPP 18.04 has been released! Artifacts are available on nexus.fd.io

2018-04-25 Thread Dave Wallace
Most Excellent! Thanks Chris for all of your work on getting the release out the door. Also many thanks to all of the VPP committers and FD.io community members who contributed to 18.04 Best, -daw- On 04/25/2018 06:52 PM, Chris Luke wrote: All, I am happy to announce that VPP 18.04 has

Re: [vpp-dev] [csit-dev] VPP 18.04 has been released! Artifacts are available on nexus.fd.io

2018-04-25 Thread Tina Tsou
Bravo! Thank you, Tina On Apr 25, 2018, at 4:33 PM, Florin Coras > wrote: Yay! Thanks, Chris! Florin On Apr 25, 2018, at 3:52 PM, Chris Luke > wrote: All, I am happy to announce

Re: [vpp-dev] [csit-dev] VPP 18.04 has been released! Artifacts are available on nexus.fd.io

2018-04-25 Thread Florin Coras
Yay! Thanks, Chris! Florin > On Apr 25, 2018, at 3:52 PM, Chris Luke wrote: > > All, > > I am happy to announce that VPP 18.04 has been released! The release notes > can be found athttps://docs.fd.io/vpp/18.04/release_notes_1804.html >

[vpp-dev] VPP 18.04 has been released! Artifacts are available on nexus.fd.io

2018-04-25 Thread Chris Luke
All, I am happy to announce that VPP 18.04 has been released! The release notes can be found at https://docs.fd.io/vpp/18.04/release_notes_1804.html. The various release artifacts have made their way to the right places on nexus.fd.io. Packaging for Centos 7 (Intel), openSUSE Leap 42.3

[vpp-dev] vpls-dev in vpp (1) #vpp

2018-04-25 Thread mortaza . biabani
[Edited Message Follows] *Hi,* in this scenario (vpls) in  vpp : VPLS: NS-PE1 <--ce-link-1--> VPP-PE1 <--core-link-1--> core-bridge <--core-link-2--> VPP-PE2 <--ce-link-2--> NS-PE2   example: PE1 create host name vce-link-1 create host name vcore-link-1 set int state host-vce-link-1

[vpp-dev] vpls-dev in vpp (1) #vpp

2018-04-25 Thread mortaza . biabani
in this scenario (vpls) in  vpp : VPLS: NS-PE1 <--ce-link-1--> VPP-PE1 <--core-link-1--> core-bridge <--core-link-2--> VPP-PE2 <--ce-link-2--> NS-PE2   example: PE1 create host name vce-link-1 create host name vcore-link-1 set int state host-vce-link-1 up set int state

[vpp-dev] #vpp

2018-04-25 Thread mortaza . biabani
in this scenario (vpls) in  vpp : VPLS   PE1 create host name vce-link-1 create host name vcore-link-1 set int state host-vce-link-1 up set int state host-vcore-link-1 up set interface ip table host-vce-link-1 1   set int ip address host-vce-link-1 192.168.2.1/24 set int ip address

Re: [vpp-dev] Trying to build vpp on amd64 platform via qemu static library qemu-aarch64-static in Docker container

2018-04-25 Thread Ole Troan
Brian, > This appears to be related to cross compiling VPP. > vppapigen is built for the cross target, but then run on the host as part of > the build. > > Can someone who is familiar with the build system confirm? If so, is it worth > fixing a cross build such that vppapigen is compiled for

Re: [vpp-dev] Trying to build vpp on amd64 platform via qemu static library qemu-aarch64-static in Docker container

2018-04-25 Thread Brian Brooks
This appears to be related to cross compiling VPP. vppapigen is built for the cross target, but then run on the host as part of the build. Can someone who is familiar with the build system confirm? If so, is it worth fixing a cross build such that vppapigen is compiled for host target and run

[vpp-dev] how to include my pluging in rpm?

2018-04-25 Thread Avi Cohen (A)
Hi When I build rpm's I see that my plugins are not included in the output list , hence they also not installed when I do rpm install Where do I have to add my plugins so it will be included in the rpm's ? Best Regards Avi -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this

Re: [vpp-dev] Build error with my_plugin.api.h file.

2018-04-25 Thread Ole Troan
Hi Sara, > can you specify the vppapigen syntax ? Sure, especially if you can provide review and feedback. Cheers, Ole > On Wed, Apr 25, 2018 at 3:47 PM, Ole Troan wrote: > Sara, > > Can you run vppapigen manually. > And also include the .api you are having problems

Re: [vpp-dev] Build error with my_plugin.api.h file.

2018-04-25 Thread Sara Gittlin
Ole can you specify the vppapigen syntax ? -Sara On Wed, Apr 25, 2018 at 3:47 PM, Ole Troan wrote: > Sara, > > Can you run vppapigen manually. > And also include the .api you are having problems with. > > I presume you are on latest master? > > Cheers, > Ole > > > On 25

Re: [vpp-dev] Build error with my_plugin.api.h file.

2018-04-25 Thread Ole Troan
Sara, Can you run vppapigen manually. And also include the .api you are having problems with. I presume you are on latest master? Cheers, Ole > On 25 Apr 2018, at 14:41, Sara Gittlin wrote: > > Chris and Neale, > Can we go back to the original problem pasted below -

Re: [vpp-dev] Build error with my_plugin.api.h file.

2018-04-25 Thread Sara Gittlin
Chris and Neale, Can we go back to the original problem pasted below - the 53 is *not* a line in my_policer/forwarder.api -- I've encountered this build error few times and managed to get rid of it somehow. the error is always with the my_plugin.api.h file. Can

[vpp-dev] Notice: Branch stable/1804 closed for changes

2018-04-25 Thread Chris Luke
All, Today is VPP 18.04 release day; to help the release go smoothly we close the branch to changes during the release process. From this point, any changes submitted for review will go ignored until after the release is complete. Committers, Please avoid merging any changes into stable/1804