DPDK 2024 Community Lab Work Planning

	A	B	D	E	F	G	H	I	J	K	L	M	N	O	Q	R
1	Work Item		Average Rating (incl. non-voters)		Tech Board Priority Input Please rate High (5) to Low (1), or No Vote (0)
2	Work Item	Difficulty (H / M / L)	Average Rating (incl. non-voters)	Tech Board Average Rating	Aaron Conole	Bruce Richardson	Hemant Agrawal	Honnappa Nagarahalli	Jerin Jacob	Kevin Traynor	Konstantin Ananyev	Maxime Coquelin	Stephen Hemminger	Thomas Monjalon	David Marchand (just fyi, vote does not count)	Morten (just fyi, vote does not count)
3	DTS Improvement
4	Add additional resource to the lab staff for DTS coding	N/A	4.4	4.3	4	5	4	5	0	4	0	0	0	4	4	5
5	Continue to migrate all DTS testsuites currently running in the lab CI to run from DTS within the DPDK main repo.	H	4.8	5.0	5	5	5	5	0	5	0	0	0	5	5	3
6	Clean up and improvement of testpmd logging, that is used by DTS to determine measurement and test results. This is specifically for how the new DTS framework will consume testpmd logs.	M	4.0	4.0	3	0	0	5	0	0	0	0	0	0	0	0
7	Extend test coverage of ethdev features within DTS.	H	3.8	3.8	3	4	4	3	0	4	0	0	0	5	3	4
8
9	Test Coverage
10	Deploy compressions performance testing, based on the sample application dpdk-compress-perf tool. Finalizing deployment of the QAT card will rely on this for testing in the ARM platform.	M	1.1	1.2	1	2	1	0	0	1	0	0	0	1	1	1
11	Deploy testing to match Intel lab coverage, providing redundancy. This can include functional tests within DTS, as well as extending our compile testing matrix.	H	2.6	2.8	4	2	3	3	0	3	0	0	0	2	3	1
12	Investigate and expand to "public cloud testing" where it is possible. Areas to cover could be: performance, multi core forwarding, sample apps, unit testing	H	2.9	2.8	3	3		2	0	3	0	0	0	3	2	4
13	Testing for private on premesis cloud: Hyper-V		#DIV/0!	#DIV/0!											0	0
14	Testing for private on premesis cloud: Proxmox VE		#DIV/0!	#DIV/0!											0	0
15	VMWare private on-premesis cloud testing	M	#DIV/0!	#DIV/0!											0	0
16	Testing on cloud Kubernetes deployments	H	#DIV/0!	#DIV/0!											0	0
17	Investigate SPDK compilation	L	2.6	2.6	4	2	2	0	0	4	0	0	0	1	4	1
18	OVS Compilation	M	3.0	3.0	4	3	3	0	0	4	0	0	0	1	4	2
19	LCOV / GCOV reporting for unit testing and reporting via a badge on patchworks.	M	2.4	2.3	4	1	2	3	0	3	0	0	0	1	2	3
20
21	Lab Improvements
22	Patch "Depends-on" Support in Apply Patch	M	4.3	4.3	5	5	5	4	0	2	0	0	0	5	5	3
23	Update our reporting process to show current status of all test coverage for a patch series (what is pending, did something not report due to an infra failure, etc)	H	3.5	3.7	4	4	4	4	0	3	0	0	0	3	3	3
24	Add "staging" branches for next-* branches, like is currently used for 21.11-staging and 22.11-staging	L	3.5	3.3	5	2	2	2	0	5	0	0	0	4	5	3
25	improve quality of logs delivery both via Community Lab dashboard website (currently you have to download zip folders) and for patchwork reports (we should capture only the salient log lines)	L	3.1	3.2	2	4	3	2	0	3	0	0	0	5	4	2
26
27	Lab Hardware Expansion
28	Migrate to a more common server / platform in the lab, compared to the current unique server per vendor / NIC (i.e. what vendors shipped to the lab)	M	1.9	1.6	2	2	2	0	0	1	0	0	0	1	2	3
29	New hardware types, such as GPU or other accelerator cards (compression, encryption, etc.)	M	1.4	1.6	1	2	2	0	0	2	0	0	0	1	1	1
30	Dedicated (hardware based) traffic generator or alternate software traffic generators for performance testing.	H	1.8	1.8	2	3	2	2	0	1	0	0	0	1	2	1
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100