Hi All & Nathan,
Thanks for your input.
I followed your steps, build release VPP with my plugin change and make
production image. In production image, I faced same issue like my sample.so
plugin is not loaded when launch the vpp.
Again, I followed development image steps, build release VPP with m
Hi Feroz,
My replies are inline.
Cheers
-Nathan
Le jeu. 21 nov. 2019 à 22:06, Mohamed feroz Abdul majeeth <
feroz...@gmail.com> a écrit :
> Hi Nathan,
>
>
> Thanks for your response, I will try what you said.
> One more update:
> My sample.so plugins are loaded in contiv - vpp/dev-vswitch( deve
Hi Nathan,
Thanks for your response, I will try what you said.
One more update:
My sample.so plugins are loaded in contiv - vpp/dev-vswitch( development
image).
I started kubernetes and apply contiv vpp yaml with
contiv-vpp/dev-vswitch:3.3.2 image( development image). It's running and
open the vp
Hi Feroz,
If your plugin gets loaded in the vpp running directly on your machine but
not in contiv-vpp, it's likely that there is a version mismatch between the
two or something weird happening during contiv build process.
* You can check the loaded plugins directly in the debug cli (vppctl : show
Hi Team,
We add sample( sample.so) plugins with existing vpp plugins. I used 3.3.2
tag contiv vpp and copied sample plugins related code *patches *.diff
under contiv vpp patches folder( vpp/ docker/ vpp- vswitch /vpp/ patches).
Patches also applied correctly and able to create the contiv/vswitch
