The Opensource Protocol for Managing Multi-Vendor Servers...
summary
If needing concrete payoff: Redfish is a vendor‑neutral REST API that is on by default in nearly every modern server (only one major vendor lacks it), the spec updates every few months, and Swordfish extends Redfish for NVMe/SAN though adoption is still limited. There are Docker mockups and emulators to test implementations and a community PowerShell swordfish toolkit with cross‑vendor test outputs, examples and many GETs implemented but incomplete PUT/POSTs — suitable for inventory, event‑log collection, Prometheus/Grafana feeding, and automations like secure erase.
AI-written summary · about
chapters (13)
- 0:00Multi-vendor server management standards
- 3:20Legacy protocols SNMP and IPMI limits
- 5:26Need for lightweight cross-vendor protocol
- 8:16Redfish protocol and adoption
- 10:43Redfish API mockups and structure
- 14:18Redfish specification
- 16:06Swordfish for enterprise storage
- 19:17Swordfish API and extensions
- 23:17Redfish and Swordfish tools
- 29:52Redfish automation use cases
- 35:27Why vendors support Redfish
- 37:57Community and future of protocol
- 39:22Q&A
related talks
26mUnify Data and Storage Management with SODA ODF
11mFOSS @ ElasticRun
33mSponsored Session: Open Source Cloud Native Storage Solutions for Stateful Applications from ...
22mRedis Alternatives Compared
36mStorage Wars
11mLightning Talk: A Supply Chain Security View of OpenSearch
16mOpenZFS
23mAn Open Source Architecture for Modernizing Market Risk Management