> chris_l...@cable.comcast.com>; Alessio Silvestro ;
> vpp-dev
> *Subject:* Re: [vpp-dev] VPP/How To Build The Sample Plugin
>
>
>
> OK, I figured out how to patch code to add a vat_plugin_path option to
> /etc/vpp/startup.conf, but that was not the answer to the immediat
Silverman [mailto:bur...@gmail.com]
Sent: Friday, June 2, 2017 17:54
To: Damjan Marion (damarion) ; Dave Barach
Cc: Kinsella, Ray ; Luke, Chris
; Alessio Silvestro ;
vpp-dev
Subject: Re: [vpp-dev] VPP/How To Build The Sample Plugin
OK, I figured out how to patch code to add a vat_plugin_path
ace for in-tree plugins which actually do
>>> something useful.
>>> >>>> If people want to create additional in-tree plugin, there is many
>>> samples already in src/plugins so I don't see an need for additional one.
>>> >>>>
>>
t; So to continue discussion on this particular change, what do you
>> think that it is broken?
>> >>>>
>> >>>> For me sequence:
>> >>>>
>> >>>> autoreconf -fis
>> >>>> ./configure
>> >>>> make
>> >>>> make inst
7/05/2017 18:27, Luke, Chris wrote:
Wishes often come true when you turn them into patches. :)
Chris.
*From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io]
*On Behalf Of *Burt Silverman
*Sent:* Saturday, May 27, 2017 10:33
*To:* Kinsella, Ray
*Cc:* Alessio Silvestro
most likely to try it and use it, are those least familiar
> with VPP.
> >>>>>
> >>>>> I tried the use it a few months ago in training and found the UX
> similar then. So I put together a number of changes to integrate the plugin
> into the VPP build
c/plugins so I don't see an need for additional
>>>>>>> one.
>>>>>>>
>>>>>>> So to continue discussion on this particular change, what do you think
>>>>>>> that it is broken?
>>>>>>>
&g
nce:
>>>>>>
>>>>>> autoreconf -fis
>>>>>> ./configure
>>>>>> make
>>>>>> make install
>>>>>>
>>>>>> Works perfectly fine. Off-course you need to have install vpp-dev
>&g
t.fd.io/r/#/c/6920/
Thanks,
Ray K
On 27/05/2017 18:27, Luke, Chris wrote:
Wishes often come true when you turn them into patches. :)
Chris.
*From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io]
*On Behalf Of *Burt Silverman
*Sent:* Saturday, May 27, 2017 10:33
*To:* Kinsella,
; with VPP.
>>>>>
>>>>> I tried the use it a few months ago in training and found the UX similar
>>>>> then. So I put together a number of changes to integrate the plugin into
>>>>> the VPP build system, provide a build var to enable and dis
, Ray
*Cc:* Alessio Silvestro ; vpp-dev
*Subject:* Re: [vpp-dev] VPP/How To Build The Sample Plugin
Thanks, Ray, this is exactly what I needed, by coincidence. I wish your
item 2. was placed commented out and almost word for word into the
standard $TOPDIR/src/vpp/conf/startup.conf -- that would
gt;>>
>>> https://gerrit.fd.io/r/#/c/6920/
>>>
>>> Thanks,
>>>
>>> Ray K
>>>
>>> On 27/05/2017 18:27, Luke, Chris wrote:
>>>> Wishes often come true when you turn them into patches. :)
>>>>
>>&
*Subject:* Re: [vpp-dev] VPP/How To Build The Sample Plugin
Thanks, Ray, this is exactly what I needed, by coincidence. I wish your
item 2. was placed commented out and almost word for word into the
standard $TOPDIR/src/vpp/conf/startup.conf -- that would make things
self documenting.
Burt
wrote:
>> Wishes often come true when you turn them into patches. :)
>>
>>
>>
>> Chris.
>>
>>
>>
>> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io]
>> *On Behalf Of *Burt Silverman
>> *Sent:* Saturday, May 27
:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io]
*On Behalf Of *Burt Silverman
*Sent:* Saturday, May 27, 2017 10:33
*To:* Kinsella, Ray
*Cc:* Alessio Silvestro ; vpp-dev
*Subject:* Re: [vpp-dev] VPP/How To Build The Sample Plugin
Thanks, Ray, this is exactly what I needed, by
Wishes often come true when you turn them into patches. :)
Chris.
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Burt Silverman
Sent: Saturday, May 27, 2017 10:33
To: Kinsella, Ray
Cc: Alessio Silvestro ; vpp-dev
Subject: Re: [vpp-dev] VPP/How To Build The
Thanks, Ray, this is exactly what I needed, by coincidence. I wish your
item 2. was placed commented out and almost word for word into the standard
$TOPDIR/src/vpp/conf/startup.conf -- that would make things self
documenting.
Burt
On Sat, May 27, 2017 at 8:30 AM, Kinsella, Ray
wrote:
> So there
So there is an easier way
1. make -C build-root PLATFORM=vpp TAG=vpp sample-plugin-install
2. adjusting the plugin path depending on where the VPP src is, add the
following to your startup.conf
plugins
{
path
/root/src/vpp/build-root/install-vpp-native/sample-plugin/lib64/vpp_plugins
blem last week,
>>
>>
>>
>> Try the following:
>>
>> autoreconf -fis
>>
>> .configure
>>
>> make
>>
>>
>>
>> Guy
>>
>> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
>
I had the same problem last week,
Try the following:
autoreconf -fis
.configure
make
Guy
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Alessio Silvestro
Sent: Friday, May 26, 2017 7:53 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] VPP/How To Build The
Hi all,
I am trying to build the sample vpp-engine plug-in as explained here (
https://wiki.fd.io/view/VPP/How_To_Build_The_Sample_Plugin).
I already tested my vpp installation, for instance it works when I created
a Source NAT.
I downloaded the most updated version of the sample-plugin and run
21 matches
Mail list logo
