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 plugins) to ensure check the plugin state at runtime. * If both don't run the same version running <vppctl : show version> will give two different commits. * The problem might also come from vpp's config file (/host/etc/vpp/contiv-vswitch.conf in contiv's case) but it's less probable if it doesn't appear in the logs.
If this doesn't help finding the discrepancy, you can build a contiv-vpp image from your working binaries with : cd CONTIV_DIR && make contiv-agent contiv-init cd VPP_DIR && make build-release ; make pkg-deb cp $VPP_DIR/build-root/*.deb /scratch/ cd /scratch && wget https://github.com/contiv/vpp/blob/master/docker/vpp-vswitch/dev/govpp.conf cd /scratch && wget https://github.com/contiv/vpp/blob/master/docker/vpp-vswitch/prod/vswitch/vpp.conf cd /scratch && wget https://github.com/contiv/vpp/blob/master/docker/vpp-vswitch/prod/vswitch/vppctl You can then build a docker image with https://gist.github.com/sknat/cc016e4905cb875f62c74e28e2cc5661 Hope this helps Cheers -Nathan Le jeu. 21 nov. 2019 à 06:41, Mohamed feroz Abdul majeeth < feroz...@gmail.com> a écrit : > 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 docker > image. Even I seen its generated sample.so in vpp_ plugins folder in > *contiv-vpp/*vpp container which is having builded vpp code. > I started kubernetes and apply contiv vpp yaml with > contiv-vpp/vswitch:3.3.2 image. It's running and open the vppctl but not > able to see sample plugins related cli commands so I seen logs(kubectl logs > contiv-vswitch-lqxfp -n kube-system -c contiv-vswitch). In logs, there is > no sample.so plugin loading information details. > > For verification, I followed same vpp build steps in bare metal which is > follow in contiv vpp code, sample.so plugin is loaded when I launch the > vpp and I'm able to see sample.so plugins cli commands details. > > In docker/container only, *sample**.so* <http://custom.so> plugin is not > loaded when launch the vpp. > > Please help me and guide me. How to solve this problem. > > Thanks, > Feroz > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#14653): https://lists.fd.io/g/vpp-dev/message/14653 > Mute This Topic: https://lists.fd.io/mt/61032023/1706314 > Group Owner: vpp-dev+ow...@lists.fd.io > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [ > nathan.skrzypc...@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14659): https://lists.fd.io/g/vpp-dev/message/14659 Mute This Topic: https://lists.fd.io/mt/61032023/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
