Re: [vpp-dev] The latest master code build failure

Hi, This behavior follows this commit : 4c42e913c4f9723d27f6501f6e1b6a13b9c2f9f8 You should *make build-vpp-api* before building plugins. Regards, On 10/19/16 11:14, yu scott wrote: > Hi all > > I build the stable/1609 stable version code successfully in my pc,but > when I update my > vpp code

[vpp-dev] flowtable proposal

Hi, Following Christophe Fontaine's work during ietf hackathon in Berlin (https://github.com/christophefontaine/flowtable-plugin), I wrote a flowtable as a vpp plugin. Code is available here: https://github.com/GabrielGanne/vpp-flowtable/commits/master It contains the flowtable plugin, a port-mi

Re: [vpp-dev] flowtable proposal

e scripts? > > Delighted to see contributions, but am a bit fuzzy on where I might > use this. > > Ray K > > > On 19/10/2016 11:11, gannega wrote: >> Hi, >> >> Following Christophe Fontaine's work during ietf hackathon in Berlin >> (https://github.com/chr

[vpp-dev] draft - plugin's python api package

Hi, So, I understand we want to build separate python packages for each and every plugin. I have written a proposal for snat only as an example which generates the following tree : ./build-root/install-vpp_debug-native/plugins/vpp_papi_plugins/snat-plugin/ ├── setup.py ├── snat │ ├── __init__.

Re: [vpp-dev] draft - plugin's python api package

ailto:vpp-dev-boun...@lists.fd.io] On >> Behalf Of gannega >> Sent: Friday, October 28, 2016 08:22 >> To: vpp-dev@lists.fd.io >> Subject: [vpp-dev] draft - plugin's python api package >> >> Hi, >> >> So, I understand we want to build separate

[vpp-dev] flowtable plugin

Hi, I'm currently working on writing a flowtable node for vpp (It can be found in vppsb or on github ). In short, it inserts itself between given interface and ethernet-input, and basically provides a buffer associated to the flow which can be writte

Re: [vpp-dev] flowtable plugin

r. > > Classifier conveniently gives a u32 opaque, which is moved around with > the packet at least in the L2 case in L2 opaque - so it seems to allow > for a nice loose coupling, and get things done with the least amount > of new code. > > But would be interesting to chat more

Re: [vpp-dev] flowtable plugin

4 pm is good. I'll set up a webex. On 11/09/16 12:28, Andrew 👽 Yourtchenko wrote: > Hi Gabriel, > > Excellent! How about we meet tomorrow 4 pm then ? Or we can push the meeting > to Monday if that time tomorrow is inconvenient for you. > > --a > >> On 9 No

Re: [vpp-dev] flowtable plugin

at 12:28, Andrew 👽 Yourtchenko wrote: >> >> Hi Gabriel, >> >> Excellent! How about we meet tomorrow 4 pm then ? Or we can push the >> meeting to Monday if that time tomorrow is inconvenient for you. >> >> --a >> >>> On 9 Nov 2016, at 11:37,

Re: [vpp-dev] flowtable plugin

t;> >>>>> On 9 Nov 2016, at 12:28, Andrew 👽 Yourtchenko wrote: >>>>> >>>>> Hi Gabriel, >>>>> >>>>> Excellent! How about we meet tomorrow 4 pm then ? Or we can push the >>>>> meeting to Monday if that time

Re: [vpp-dev] flowtable plugin

the uses of the flowtable and the rest of vpp (if such was indeed your fear). What do you think ? Regards, On 11/10/16 17:42, Andrew 👽 Yourtchenko wrote: > On 11/10/16, gannega wrote: >> Hi, >> >> One question for Keith first: >> >> The flowtable currently uses t

Re: [vpp-dev] flowtable plugin

that. Thanks again, Best regards, On 11/23/16 14:55, Keith Burns wrote: > > > On Wed, Nov 23, 2016 at 5:23 AM gannega <mailto:gabriel.ga...@qosmos.com>> wrote: > > Hi Keith, > > This is a kind reminder. > > > Apologies for tardiness... > >

Re: [vpp-dev] flowtable plugin

A needs to send some > information to node C and there is > unknown B or many Bs in the middle? > > >> On 23 Nov 2016, at 15:15, gannega > <mailto:gabriel.ga...@qosmos.com>> wrote: >> >> Thanks for the explanation. >> >> So I can use anything I wan

Re: [vpp-dev] flowtable plugin

re FIB lookup and node C > after. FIB > might send your frames to different encap nodes which may overwrite opaque, > one candidate > is definitely ipsec which uses opaque for storing security associations. > > >> On 24 Nov 2016, at 13:27, gannega wrote: >> >>

Re: [vpp-dev] flowtable plugin

nt now. I'll see how to make sure the portmirroring node behaves correctly depending on its position in the graph node later. Best Regards, On 11/25/16 14:22, gannega wrote: > Thanks Damjan. > > I'll keep those examples in mind to make sure nothing bad can happen. > > >

[vpp-dev] crash when calling API sw_interface_dump

Hi, Since commit: aff7077d2031545a15efd12e7f65eac723799491 I have the following warning, then error : I looked at the commit, but I cannot find what's wrong with it. Is there something changed with the way I should call the API ? [python] import vpp_papi vpp_papi.connect('test') vpp

Re: [vpp-dev] crash when calling API sw_interface_dump

Sure. Thanks Ole. On 12/02/16 12:00, Ole Troan wrote: > Gabriel, > >> Since commit: aff7077d2031545a15efd12e7f65eac723799491 I have the >> following warning, then error : >> >> I looked at the commit, but I cannot find what's wrong with it. Is there >> something changed with the way I should cal

Re: [vpp-dev] crash when calling API sw_interface_dump

Hi Ole, The patches you pushed last Friday indeed fixed all my buggy calls. Thank you for this. FYI, I think it broke the vpp-python-api rpm packaging however: rpm -qpl build-root/vpp-python-api-17.01-rc0~187_gbed29e8.x86_64.rpm /usr/lib/python2.7/site-packages/vpp_papi/easy-install.pth /usr/lib

Re: [vpp-dev] building rpm packages failure

Hi, I believe this happens if you still have the dpdk binaries in build-root/install-vpp-native/dpdk/bin/ when building the vpp rpm. The install wildcards used at the begining of the spec file are too permissive. I propose this simple patch : https://gerrit.fd.io/r/#/c/4894/ Best regards, On