DPDK Userspace 2018

Establishing a CI system for DPDK is facing several challenges: 1) DPDK validation (build, test and benchmark) need to cover different OSes, vendors’ platforms, and vendors’ NICs. 2) Need to do CI test for DPDK patches in “before merge” and “after merge” timely (in a short time).  

The proposal is that DPDK open lab + DPDK CI system. In open lab, standard testbeds are designed by each vendor, and all testbeds are managed centralized. Based on standard testbeds, a unified test suite can be well defined to cover OSes, platforms, NICs and their combination. With standard testbeds and a unified test suite, execution time is fined controlled and consistent quality indicator can be provided to all users. Meanwhile, CI system is designed to monitor patches in community, to trigger build test on each OS, and to dispatch tests to testbeds in open lab. Finally, the validation results are showed in CI dashboard. Furthermore, CI system includes a database in the back-end to support to track quality and performance data.