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.
39 lines
722 B
YAML
39 lines
722 B
YAML
interfaces:
|
|
GigabitEthernet3/0/0:
|
|
device-type: "dpdk"
|
|
mtu: 9000
|
|
state: up
|
|
sub-interfaces:
|
|
100:
|
|
mtu: 9000
|
|
l2xc: tap100
|
|
GigabitEthernet3/0/1:
|
|
device-type: "dpdk"
|
|
mtu: 1500
|
|
mac: 00:25:90:0c:05:01
|
|
state: down
|
|
description: Not Used
|
|
HundredGigabitEthernet13/0/0:
|
|
device-type: "dpdk"
|
|
mtu: 1500
|
|
mac: b4:96:91:b3:b1:10
|
|
state: down
|
|
description: Not Used
|
|
HundredGigabitEthernet13/0/1:
|
|
device-type: "dpdk"
|
|
mtu: 1500
|
|
mac: b4:96:91:b3:b1:11
|
|
state: down
|
|
description: Not Used
|
|
|
|
tap100:
|
|
mtu: 9000
|
|
l2xc: GigabitEthernet3/0/0.100
|
|
|
|
taps:
|
|
tap100:
|
|
host:
|
|
name: vpp-tap100
|
|
mac: 02:01:be:ef:ca:fe
|
|
mtu: 9000
|