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

Add device-type, to ensure that plan --novpp generates MTU statements

Browse Source
This commit is contained in:
Pim van Pelt
2023-05-25 16:54:01 +02:00
parent 3249432681
commit cf5f1f0944
4 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/config-guide.md
View File

@ -304,6 +304,8 @@ exist as a PHY in VPP (ie. `HundredGigabitEthernet12/0/0`) or as a specified `Bo
target interface.
* ***state***: An optional string that configures the link admin state, either `up` or `down`.
If it is not specified, the link is considered admin 'up'.
* ***device-type***: An optional interface type in VPP. Currently the only supported vlaue is
`dpdk`, and it is used to generate correct mock interfaces if the `--novpp` flag is used.
Further, top-level interfaces, that is to say those that do not have an encapsulation, are permitted
to have any number of sub-interfaces specified by `subid`, an integer between [0,2G), which further
@ -324,6 +326,7 @@ Examples:
```
interfaces:
HundredGigabitEthernet12/0/0:
device-type: dpdk
lcp: "ice0"
mtu: 9000
addresses: [ 192.0.2.1/30, 2001:db8:1::1/64 ]

3
docs/user-guide.md
View File

@ -271,6 +271,9 @@ with `head.vpp` (think of things like custom logging, plugin defaults, DPDK affi
then letting `vppcfg` do its part, and finally leaving the ability to also program the dataplane
with things that `vppcfg` does not (yet) support in `tail.vpp`.
***NOTE***: For MTU values to be generated in `--novpp` mode, the interface device type must be
set (typically using `device-type: dpdk` in the PHY interface definition).
### vppcfg apply
Applying state is not (yet) implemented. Don't worry, it's not much work, but this is punted until