19.02.2026

# ALASCA SONiC Community Build - SCOMB

Attendees: Andreas Köpsel, Bastian Heitmann, Carola Klessen, Christian Lammers, Frank Benke, Heidi Lin, Marcel Sowiak, Martin Hayes, Matthias Haag, Moore Lee, Robert Volkmann, Rankan Sen, Helena Ott

### Presentation of previously done work 

→ Work done by Rankan Sen (Cloud&Heat Technologies)

- The current SONiC community build pipeline contains several upstream inconsistencies that cause intermittent build failures (dependency mismatches, Docker image issues, and platform-specific makefile errors).
- A fully successful build has now been completed for Broadcom (BCM) ASIC-based switch platforms using the `sonic-buildimage` framework.
- Build stabilization included:

  1\. Resolving Docker container version conflicts  
  2. Fixing missing or incompatible Debian package dependencies  
  3. Addressing Broadcom platform-specific build target inconsistencies  
  4. Ensuring correct platform module linkage and image packaging
- A complete end-to-end build documentation has been created and published in the SCOMB repository.
- The documentation covers:

  1\. Host environment prerequisites (Linux version, RAM/CPU requirements, disk space)  
  2. Required packages and dependency installation  
  3. Repository cloning and branch selection  
  4. Build target configuration for Broadcom platforms  
  5. Image compilation workflow  
  6. Artifact validation and image verification steps
- Basic post-installation setup steps are also included:

  1\. Initial login and password configuration  
  2. Management interface (eth0) IP configuration  
  3. Enabling SSH access  
  4. Saving configuration persistently  
  5. Verifying platform, ASIC, and service status
- The documentation is structured to support reproducibility and future CI/CD integration.
- Upcoming work:  
  1. Testing and documenting advanced feature sets (ACL, VLAN, PortChannel, BGP, VRF, telemetry, etc.)  
  2. Validating feature behavior across multiple Broadcom SKUs  
  3. Adding troubleshooting sections for common deployment and runtime issues  
  4. Improving build reliability and contributing fixes upstream where applicable

It was agreed upon that the CI/CD pipeline will run in the ALASCA GitLab. 

### Topics to be discussed:

- Where will SCOMB be hosted for other people to download
  - we need some file space for the images 
  - needs to be public 
- image tag schema: uhuruTec already has something in place 

###