Towards a Community Build of SONiC
summary
SONiC builds currently take 2–3 hours and pull from many vendor-controlled hosts (Microsoft trafficmanager.net dominates), producing flaky CI with intermittent, non-deterministic failures and about ~1000 open PRs. Running images shows missing features like EVPN multihoming and container crashes (SNMP drops when a power cord is pulled). The proposed pipeline builds per-platform images, hosts artifacts and registries under ALASCA, pushes results to a heterogeneous testbed, and targets a community-maintained, hardened release (ideas include NixOS-based builds).
AI-written summary · about
chapters (6)
- 0:00Introduction to SONiC
- 1:14Community SONiC challenges
- 3:21Building SONiC issues
- 5:09Current build dependencies
- 7:35Proposed community build approach
- 9:22Next steps and future plans
related talks
14mSONiC – open than ever
56mA Practical Look at NetDevOps
30mBringing Continuous Delivery to Open Source
51mA Community Approach to OSS Distribution
47mPrepping your Open Source Project for Multi-Platform
17mBuilding Secure Open Source Communities From the Ground Up
26mDeep Dive: CNCF CI
48mBuilding Community Mesh Networks