How Open Hardware Access Builds the Next Generation of Infrastructure Engineers - Sam Dasilva, Red Hat#

Speakers: Sam Dasilva, Associate Software Engineer, Red Hat

• Why: Not a networking technique, but a genuinely different argument: the open-source model fixed contributor access to software decades ago, but infrastructure-acceleration work (DPUs, SuperNICs) is still gated behind vendor employment — so the contributor pipeline for the exact hardware class this whole conference is about is artificially narrow. The talk walks one full path: CS student with no STEM background → Red Hat intern on DPU/SmartNIC work → OPI LFX mentee who upstreamed the DPU Operator.
• What: The technical substance of the handoff: decoupling the DPU Operator from OpenShift-specific dependencies, making it work on vanilla Kubernetes, validating across Fedora/CentOS Stream/AlmaLinux via bootable containers, and standing up multi-vendor community CI for DPU hardware. Plus the argument that open hardware labs plus mentorship produce both working code and working engineers. (from abstract only)
• How: Concretely: dependency decoupling for k8s portability, bootable-container-based OS validation matrices, and community CI across multiple DPU vendors — the same engineering patterns (portability, CI, upstreaming) applied to the hardware-access problem itself.
• Where applicable: Relevant to anyone building or depending on open infrastructure projects facing hardware access as the bottleneck (DPU/IPU, SmartNIC, accelerator ecosystems). The multi-vendor CI story also matters operationally if you consume the DPU Operator: it describes what is actually validated, and on what.