Arm Server Manageability and OpenBMC
summary
Arm is developing a concrete manageability spec called SBMG server base manageability guide with subteams defining remote debug via BMC, platform monitoring, and error (RES) interfaces; a 43-company group already governs changes and meets monthly. IPMI remains required for years while Redfish adoption grows slowly. An open compliance test suite (ACS) is published and OpenBMC 2.7 is targeted as the SBMG reference implementation with firmware update, power/thermal control and virtual media support. Participation is requested.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:11Why do we need a standards-based approach?
- 4:03What is the Arm standards-based approach to servers
- 5:09Arm Server Advisory Committee
- 6:28SBBR: Server Base Boot Requirements
- 9:09SBMG Server Base Manageability Guide
- 12:55How is SBMG developed?
- 13:28Tracking spec changes
- 14:39Development process
- 15:42Why SBMG Server Management is a critical function for the servers
- 17:01So what's in the SBMG?
- 17:55Remote Debug Subteam
- 18:38Platform Monitoring Subteam
- 20:54IPMI vs Redfish
- 22:19OpenBMC
- 25:42RunBMC Benefits
- 26:30Call to Action
related talks
24mIntroduction to the LibreBMC project
33mIPMI is Dead, Long Live Redfish
52mMaking Pi ServerReady: time for cheap Arm infrastructure be standards-compliant
47mBoF: Mender, Current and Future Status of the Open Source Project
22mStandards-based Approach for cloud, edge and client
16mSoftware-driven Hardware in the Data Center: LibreBMC, Renode, RowHammer...
33mOpenPOWER in Enterprise: Gaps & Challenges
37mBoF: Automotive Grade Linux Developer Community