490c294014
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.
70 lines
1.3 KiB
YAML
70 lines
1.3 KiB
YAML
bondethernets:
|
|
BondEthernet0:
|
|
interfaces: [ GigabitEthernet3/0/0, GigabitEthernet3/0/1 ]
|
|
|
|
interfaces:
|
|
GigabitEthernet3/0/0:
|
|
device-type: "dpdk"
|
|
mtu: 9000
|
|
description: "LAG #1"
|
|
GigabitEthernet3/0/1:
|
|
device-type: "dpdk"
|
|
mtu: 9000
|
|
description: "LAG #2"
|
|
|
|
HundredGigabitEthernet13/0/0:
|
|
device-type: "dpdk"
|
|
mtu: 1500
|
|
description: "bridged with tap"
|
|
|
|
HundredGigabitEthernet13/0/1:
|
|
device-type: "dpdk"
|
|
description: Not Used
|
|
|
|
BondEthernet0:
|
|
mtu: 9000
|
|
lcp: "be0"
|
|
sub-interfaces:
|
|
200:
|
|
mtu: 2500
|
|
l2xc: BondEthernet0.100
|
|
encapsulation:
|
|
dot1q: 100
|
|
exact-match: False
|
|
100:
|
|
mtu: 2500
|
|
l2xc: BondEthernet0.200
|
|
encapsulation:
|
|
dot1q: 200
|
|
exact-match: False
|
|
501:
|
|
mtu: 2000
|
|
encapsulation:
|
|
dot1ad: 500
|
|
exact-match: False
|
|
500:
|
|
mtu: 2000
|
|
encapsulation:
|
|
dot1ad: 501
|
|
exact-match: False
|
|
tap100:
|
|
mtu: 1500
|
|
|
|
loopbacks:
|
|
loop100:
|
|
lcp: "bvi100"
|
|
addresses: [ 10.1.2.1/24 ]
|
|
|
|
bridgedomains:
|
|
bd100:
|
|
description: "Bridge Domain 100"
|
|
mtu: 1500
|
|
bvi: loop100
|
|
interfaces: [ HundredGigabitEthernet13/0/0, tap100 ]
|
|
|
|
taps:
|
|
tap100:
|
|
host:
|
|
name: vpp-tap100
|
|
mtu: 1500
|