When sonic-vpp VM is first booted, user needs to run sonic_vpp_cfg.sh to initialize data ports to the list of interfaces. This step is an overhead to bringup the system. It further complicates the test automation and adds more work to run sonic-mgmt on sonic-vpp platform.
The proposal is making use of config-setup service in sonic to generate the necessary configuration when sonic is booted the first time.
The list of interfaces which is passed via argument to sonic_vpp_cfg.sh will be constructed on demand. eth0 is reserved for management interface. Interfaces from eth1 to eth32, if they are configured when the VM is created, will be used for data ports.
yue-fred-gao
commented
1 month ago
When sonic-vpp VM is first booted, user needs to run sonic_vpp_cfg.sh to initialize data ports to the list of interfaces. This step is an overhead to bringup the system. It further complicates the test automation and adds more work to run sonic-mgmt on sonic-vpp platform.
The proposal is making use of config-setup service in sonic to generate the necessary configuration when sonic is booted the first time.
The list of interfaces which is passed via argument to sonic_vpp_cfg.sh will be constructed on demand. eth0 is reserved for management interface. Interfaces from eth1 to eth32, if they are configured when the VM is created, will be used for data ports.