Hi,
I've experimented with vpp_papi over VPP 16.03 recently. The way I got the
vpp_papi to work was by downloading the rpm that was available in the wiki,
which seems different from what I can install from the source: In the rpm I got
a library which let me perform operations by calling methods directly from the
module. For example:
import vpp_papi
vpp_papi.connect('test')
vpp_papi.sw_interface_dump(0, b'ignored')
This approach seems to be supported also by the wiki, the unit tests included
in the source, and previous messages in this mailing list.
However, with the API in src/vpp-api/python, it appears that I need to create a
VPP() object and provide it with an API file. I saw that there are a bunch of
.api files in the source, each with its own family of methods.
Today I've upgraded to 17.01, and the Python module I already had no longer
works (I get a segfault on vpp_papi.connect), and an rpm is no longer available
in the wiki.
Is the VPP() object the new approach to using the API, and I should alter my
code to support it; or did I do something wrong and my script should still work?
Thanks,
Lenny
_______________________________________________
vpp-dev mailing list
[email protected]
https://lists.fd.io/mailman/listinfo/vpp-dev
