ipng/ipng.ch
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Replace all post_url with Hugo ref blocks

Browse Source
This commit is contained in:
Pim van Pelt
2024-08-05 01:43:55 +02:00
parent c1f1775c91
commit a2f10236a3
56 changed files with 221 additions and 241 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
content/articles/2024-01-27-vpp-papi.md
View File

@ -17,8 +17,7 @@ design. However, there is this also a CLI utility called `vppctl`, right, so wha
the CLI is used a lot by folks to configure their dataplane, but it really was always meant to be
a debug utility. There's a whole wealth of programmability that is _not_ exposed via the CLI at all,
and the VPP community develops and maintains an elaborate set of tools to allow external programs
to (re)configure the dataplane. One such tool is my own [[vppcfg]({% post_url 2022-04-02-vppcfg-2
%})] which takes a YAML specification that describes the dataplane configuration, and applies it
to (re)configure the dataplane. One such tool is my own [[vppcfg]({{< ref "2022-04-02-vppcfg-2" >}})] which takes a YAML specification that describes the dataplane configuration, and applies it
safely to a running VPP instance.
## Introduction
@ -142,7 +141,7 @@ The VPP API defines three types of message exchanges:
If the convention is kept, the API machinery will correlate the `foo` and `foo_reply` messages into
RPC services. But it's also possible to be explicit about these, by defining _service_ scopes in the
`*.api` files. I'll take two examples, the first one is from the Linux Control Plane plugin (which
I've [[written about]({% post_url 2021-08-12-vpp-1 %})] a lot while I was contributing to it back in
I've [[written about]({{< ref "2021-08-12-vpp-1" >}})] a lot while I was contributing to it back in
2021).
**Dump/Detail (example)**: When enumerating _Linux Interface Pairs_, the service definition looks like
@ -193,7 +192,7 @@ and an additional 80 or so APIs defined by _plugins_ like the Linux Control Plan
Implementing APIs is pretty user friendly, largely due to the `vppapigen` tool taking so much of the
boilerplate and autogenerating things. As an example, I need to be able to enumerate the interfaces
that are MPLS enabled, so that I can use my [[vppcfg]({% post_url 2022-03-27-vppcfg-1 %})] utility to
that are MPLS enabled, so that I can use my [[vppcfg]({{< ref "2022-03-27-vppcfg-1" >}})] utility to
configure MPLS. I contributed an API called `mpls_interface_dump` which returns a
stream of `mpls_interface_details` messages. You can see that small contribution in merged [[Gerrit
39022](https://gerrit.fd.io/r/c/vpp/+/39022)].