Files
vppcfg/vppcfg/intest/hippo7.yaml
Pim van Pelt 490c294014 feature: add device-type to the schema
This attribute of the 'interface' schema allows the user to prompt what
type of PHY they are expecting this interface to be. It will serve an
immediate and a future purpose.

Immediate: presence of the 'dpdk' device-type in a list of interfaces
will help an upcoming vppapy.mockconfig() to generate a cache without
having to talk to the API. This is useful to generate a pre-compute a
complete vpp.exec based off of an empty VPP dataplane

Future: addition of different PHY types, notably RDMA and
VirtualEthernet types

TESTED:
- Added a unit test to ensure that only is_phy() eligable interfaces
  receive the device-type attribute.
- All unit and YAML tests pass.
2022-12-03 13:48:37 +00:00

51 lines
1023 B
YAML

interfaces:
GigabitEthernet3/0/0:
device-type: "dpdk"
mac: 02:ff:ba:03:00:00
mtu: 9216
sub-interfaces:
100:
mtu: 2000
l2xc: vxlan_tunnel0
101:
mtu: 3000
GigabitEthernet3/0/1:
device-type: "dpdk"
description: Not Used
HundredGigabitEthernet13/0/0:
device-type: "dpdk"
mtu: 9216
sub-interfaces:
100:
mtu: 3000
101:
mtu: 3000
encapsulation:
dot1q: 100
inner-dot1q: 200
exact-match: True
HundredGigabitEthernet13/0/1:
device-type: "dpdk"
mtu: 9216
vxlan_tunnel0:
mtu: 2000
l2xc: GigabitEthernet3/0/0.100
vxlan_tunnel1:
mtu: 3000
bridgedomains:
bd10:
description: "Bridge Domain 10"
mtu: 3000
interfaces: [ HundredGigabitEthernet13/0/0.101, GigabitEthernet3/0/0.101, vxlan_tunnel1 ]
vxlan_tunnels:
vxlan_tunnel0:
local: 10.0.0.1
remote: 10.0.0.3
vni: 100
vxlan_tunnel1:
local: 192.0.2.1
remote: 192.0.2.2
vni: 101