Не просто OpenBMC: как мы сделали свой BMC
Привет, Хабр! Летом мы рассказывали о сложном, но очень интересном пути в создании UEFI-загрузчика для серверных продуктов компании OpenYard. Теперь хочется перейти к его постоянному спутнику ― BMC, без которого сегодня трудно представить полноценную серверную платформу.
https://habr.com/ru/companies/openyard/articles/1024534/
#OpenYard #системное_программирование #openbmc #серверы #серверное_администрирование
@dexter well this is nice to see again, home sweet home in the Talos II bootloader - with a FreeBSD ISO installer ...
Left: OpenBMC interface w/ iKVM
Right: standard term via SSH to BMC and "obmc-console-client"
14.2 is installing now, no surprises. tomorrow, more fun!
Even #NVIDIA Has Jumped Big On The #OpenSource #OpenBMC Train
Next is "OpenBMC - The state of multi-host platform support" by Oliver Brewka
Multi-host in this context means having a single BMC managing multiple host nodes.
First multi-host system Yosemite appeared in 2015; the platform support was maintained in Meta-OpenBMC, and for the latest version it migrated to LF-OpenBMC.
One of the challenges was to go from a static to a dynamic design: the 1<->1 relation is broken, and the number of hosts might change (empty node slot). Changing the design in OpenBMC without breaking the many single-host platforms was the hard part.
As of lately, multi-host has been getting more attention in OpenBMC; Aspeed announced new multi-host capabilities for their next BMC SoC, for example.
Oliver says that multi-host in OpenBMC will improve the design, getting rid of much hard-coding, and getting closer the Redfish specification.
Tom takes over to talk about the firmware update side of the AMC with OpenBMC.
At NVIDIA, they have strong KPIs for firmware update performance and reliability, while still using standard, PLDM type 5 firmware update with Redfish.
Habr
Andrew Jeffery
Eva Winterschön
Marcin Cieślak
ricardo 
Anisse
yopp
지지 ᚠᚱᛖᛃᚨ Daniel 黄法官 CyReVolt
