@@ -83,7 +83,7 @@ <h2 id="day1">Day 1</h2>
8383 < tr > < td > Registration / Check in</ td > < td class ="time " day ="19 " start ="420 " end ="480 "> Nov</ td > </ tr >
8484 < tr > < td > Opening Remarks</ td > < td class ="time " day ="19 " start ="480 " end ="505 "> Nov</ td > </ tr >
8585 < tr > < td > < a href ="#t1 "> Observing Open vSwitch with native prometheus metrics</ a > </ td > < td class ="time " day ="19 " start ="510 " end ="535 "> Nov</ td > </ tr >
86- < tr > < td > < a href ="#t2 "> Enhancing hardware offload insights in OVS</ a > </ td > < td class ="time " day ="19 " start ="540 " end ="550 "> Nov</ td > </ tr >
86+ < tr > < td > < a href ="#t2 "> When CI Shouts Back: LLMs in the OVS CI Pipeline </ a > </ td > < td class ="time " day ="19 " start ="540 " end ="550 "> Nov</ td > </ tr >
8787 < tr > < td > < a href ="#t3 "> AI-Powered Performance Insights: Integrating OVS/OVN automatic performance regression analysis with LLMs</ a > </ td > < td class ="time " day ="19 " start ="555 " end ="590 "> Nov</ td > </ tr >
8888 < tr > < td > Break</ td > < td class ="time " day ="19 " start ="595 " end ="610 "> Nov</ td > </ tr >
8989 < tr > < td > < a href ="#t4 "> OpenFlow Classifier: Arcane knowledge and common pitfalls</ a > </ td > < td class ="time " day ="19 " start ="615 " end ="640 "> Nov</ td > </ tr >
@@ -158,26 +158,14 @@ <h3>Speaker(s): Gaetan Rivet, NVIDIA</h3>
158158datapath.
159159</ pre >
160160
161- < h3 id ="t2 "> Enhancing hardware offload insights in OVS < a href ="#day1 "> |TOP|</ a > </ h3 >
162- < h3 > Speaker(s): Nupur Uttarwar, NVIDIA </ h3 >
161+ < h3 id ="t2 "> When CI Shouts Back: LLMs in the OVS CI Pipeline < a href ="#day1 "> |TOP|</ a > </ h3 >
162+ < h3 > Speaker(s): Eelco Chaudron, Red Hat; Aaron Conole, Red Hat </ h3 >
163163< pre >
164- In Open vSwitch, troubleshooting rule offloading often requires digging
165- through logs and cross-referencing system components, especially when
166- offload fails or is unsupported. This short talk introduces enhancements
167- to the “dpctl dump-flows” command that provide explicit per-rule failure
168- if any directly in the flow dump output. With these improvements, users
169- gain streamlined troubleshooting and clearer insight into the offloading
170- pipeline, accelerating root-cause analysis and system fine-tuning.
171-
172- This talk will cover the following:
173-
174- * Motivation for improving flow offload visibility and transparency
175- * Overview of new enhancements: error detection, propagation, and
176- exposure in the data path
177-
178- Finally, I will show the usage in practice where the offload fails and
179- how users can benefit from immediate, actionable feedback on offload
180- failures.
164+ A lightning talk exploring recent experiments in the upstream CI pipeline
165+ using CodeRabbit, Sourcery, and Claude SONNET models for assisting with
166+ code review. We'll give an overview of our experiences with these tools,
167+ some interesting analysis results, and future steps for integrating an
168+ LLM into the CI development process.
181169</ pre >
182170
183171< h3 id ="t3 "> AI-Powered Performance Insights: Integrating OVS/OVN automatic performance regression analysis with LLMs < a href ="#day1 "> |TOP|</ a > </ h3 >
0 commit comments