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.
56 lines
1.2 KiB
YAML
56 lines
1.2 KiB
YAML
bondethernets:
|
|
BondEthernet1:
|
|
mac: 02:b0:b0:00:00:02
|
|
interfaces: [ GigabitEthernet3/0/0, GigabitEthernet3/0/1 ]
|
|
mode: round-robin
|
|
|
|
interfaces:
|
|
GigabitEthernet3/0/0:
|
|
device-type: "dpdk"
|
|
mtu: 9000
|
|
description: LAG
|
|
GigabitEthernet3/0/1:
|
|
device-type: "dpdk"
|
|
mtu: 9000
|
|
description: LAG
|
|
HundredGigabitEthernet13/0/0:
|
|
device-type: "dpdk"
|
|
mtu: 2500
|
|
HundredGigabitEthernet13/0/1:
|
|
device-type: "dpdk"
|
|
description: Not Used
|
|
|
|
BondEthernet1:
|
|
lcp: "bond1"
|
|
mtu: 9000
|
|
sub-interfaces:
|
|
200:
|
|
lcp: "bond1.1000"
|
|
encapsulation:
|
|
dot1q: 1000
|
|
exact-match: True
|
|
addresses: [ 192.168.0.1/24 ]
|
|
201:
|
|
mtu: 3000
|
|
encapsulation:
|
|
dot1ad: 1000
|
|
202:
|
|
lcp: "bond1.1000.1234"
|
|
encapsulation:
|
|
dot1q: 1000
|
|
inner-dot1q: 1234
|
|
exact-match: True
|
|
addresses: [ 192.168.1.1/24 ]
|
|
203:
|
|
mtu: 2500
|
|
encapsulation:
|
|
dot1ad: 1000
|
|
inner-dot1q: 1000
|
|
|
|
bridgedomains:
|
|
bd10:
|
|
description: "Bridge Domain 10"
|
|
mtu: 2500
|
|
interfaces: [ BondEthernet1.203, HundredGigabitEthernet13/0/0 ]
|
|
|