Files
vppcfg/vppcfg/intest/hippo8.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

72 lines
1.4 KiB
YAML

interfaces:
GigabitEthernet3/0/0:
device-type: "dpdk"
mtu: 9216
sub-interfaces:
100:
mtu: 2000
l2xc: vxlan_tunnel10
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
sub-interfaces:
100:
l2xc: HundredGigabitEthernet13/0/1.101
101:
l2xc: HundredGigabitEthernet13/0/1.100
vxlan_tunnel10:
mtu: 2000
l2xc: GigabitEthernet3/0/0.100
vxlan_tunnel11:
mtu: 3000
sub-interfaces:
100:
mtu: 1500
101:
mtu: 1500
encapsulation:
dot1q: 100
inner-dot1q: 200
exact-match: True
loopbacks:
loop11:
mtu: 3000
mac: de:ad:00:be:ef:11
lcp: "bvi11"
addresses: [ 2001:db8:1::1/64, 192.0.2.1/30 ]
bridgedomains:
bd11:
description: "Bridge Domain 11"
mtu: 3000
interfaces: [ HundredGigabitEthernet13/0/0.101, GigabitEthernet3/0/0.101, vxlan_tunnel11 ]
bvi: loop11
vxlan_tunnels:
vxlan_tunnel10:
local: 10.0.0.1
remote: 10.0.0.3
vni: 100
vxlan_tunnel11:
local: 192.0.2.1
remote: 192.0.2.2
vni: 101