Open-Source Operable SONiC | OCP Dublin 2025

Recorded live at the OCP Regional Summit Dublin 2025, this candid session features Matthias Haag (Founder & CEO, UhuruTec) sharing what it really looks like to deploy Community SONiC for a production cloud platform — from the perspective of a network user, not a network admin.Matthias walks through the promise of vendor-neutral networking (a “Linux-like” hardware abstraction for switches) — and the friction points he hit when trying to operationalize Community SONiC: slow and flaky build pipelines, unclear failures and unpinned dependencies, missing release tagging/versioning, feature gaps like EVPN multihoming, and day-2 reliability issues such as SNMP container crashes and unexpected restarts.He then contrasts Community SONiC with commercial/enterprise SONiC distributions (including Broadcom’s), and ends with a clear call to action: a truly open, enterprise-ready SONiC with proper CI/CD, reproducible builds, platform testing, sane releases/tags, and more upstream collaboration — with fewer “politics” slowing down key contributions.00:00 Music / opening00:11 Intro: who Matthias is and the perspective he brings (user vs. admin)00:36 Project context: why NOS/switching choices matter for a cloud platform00:46 Why SONiC and why starting with Community SONiC03:43 Hardware bring-up + setting up a custom build approach04:18 Build realities: long runtimes, caching effort, failure loops04:59 Versioning challenges: build identification, consistency, missing tags/releases05:56 Pipeline reliability concerns: “rerun works” and dependency/pinning issues06:50 Design goals: target fabric architecture + connectivity requirements07:12 Feature gaps: key capabilities missing or delayed upstream07:32 Operational stability: monitoring/service reliability pain points08:06 Boot/bring-up issues: unexpected states and disruptive fixes08:18 Hardware visibility: intermittent missing interface/transceiver info08:43 Port configuration: workarounds and manual adjustments09:06 Config errors: “applied but errors” situations that reduce confidence09:33 Unexpected restarts after configuration changes10:06 Day-2 usability: split tools for different layers and admin workflow friction10:34 Production readiness: where it’s okay today vs. where it’s still risky11:23 Enterprise/commercial comparison: features, stability, QA, polish12:04 The “server-world” analogy: openness vs. ecosystem constraints/lock-in risk13:13 Call to action: truly open “enterprise” SONiC (releases, CI/CD, testing, UX)18:06 Q&A: bringing issues upstream; tags existed before, then stopped19:25 Vendor discussion: shifting toward stronger community participation21:23 Community feedback: upstream-first collaboration vs. fragmented forks📬 Questions or support:[email protected] | www.stordis.comLet’s get social💻 Blog: stordis.com/blog/📘 Facebook: facebook.com/people/STORDIS-GmbH/100057058555819/📸 Instagram: instagram.com/stordis_open_networking/👥 LinkedIn: linkedin.com/company/stordis/🐦 X: twitter.com/STORDIS_GmbH/