OCP's Rack Manager Controller Subproject (OpenRMC)

Transcription

HardwareManagementProjectOCP's Rack Manager Controllersubproject (OpenRMC)John Leung, Principle EngineerIntel CorporationAlfie Lew, Sr. Solutions ArchitectInspur

Motivation for OpenRMC1. System Firmware (BIOS)In-band OCP System Firmware projectSWAgent2. BMC Firmware OpenBMC governed by Linux FoundationBIOS3. Rack Manager Software/Firmware1 OCP OpenRMCBMC FW3RMCServiceRack MgrControllerOSOut-of-band(Redfish)CPUNICNC-SIBMC2 With OpenBMC, the industry unified thevarious repositories in 2018 With rack manager, OCP will provide asource repository and prevent splinteringdeviceotherdeviceServer

The rack manager controller can be hosted in variouslocationsOpenRACKEIA, OpenRACKOlympus(within power shelf)(within switch)(standalone)SwitchRMC FWPower Shelf w/ RMC FWServerServerServerServerServerServerSwitch w/ RMC ServerServerServerServerServer

The OpenRMC CharterSpecify the Rack Manager Controller servicearchitecture Northbound interface to datacenter manager (spec) Southbound interface to OCP platforms in the rack(requirements)Deliver a Rack Manager implementation Available as open sourceOutside of charter The hardware designs will be within the charter ofthe other OCP platform projectsto DCmanagerRMC ClientRedfish CommandLineNorthbound InterfaceRack ManagerControllerServiceSouthbound InterfaceI2C IPMIRedfishto OCPplatforms

Logistics OpenRMC is a subproject of the Hardware Managementproject Interim co-chairs: John Leung (Intel) and Alfie Lew (Inspur) Wiki Participation ARM, Microsoft, Facebook, Huawei, Inspur, Nokia, Intel, etc

StatusRegular meetings since Nov 2018 Facebook, Inspur and Microsoft have presented their RMC architectures Comparison of interfaces D88hxbSAxp5jCLKInitial draft of Northbound API (Redfish) 5FR71qc77e8-KRDMicrosoft submitted their Olympus RMC source The submittal will be updated with latest source changes https://github.com/opencomputeproject/Rack-Manager

Northbound API SpecificationRedfish-based Interfaces are specified by A set of URI to the resources Contents of JSON document (i.e. resource properties) Behavior of the interaction via the APIThe Northbound API shall be specified with An OCP Profile (resources and resource properties) An interface behavior specification

Redfish Resources from Service RootTop level resources Each top level resource may havesubordinate resources Each resource is represented as aJSON document (name-value pairs)Resource Path (URI)/redfish/v1 (Service lemetryService/redfish/v1/UpdateServiceOpenRMC RSD RMM Olympusx x x ? x x ?

Rack Manager Scope Vectors Manages a single rack or multiple racks? What rack-level manageability capabilities are supported? Reboot, power usage, power limit, temperature profile,firmware update? How do RMC Clients and RMC Services interact? During primary operational manageability or during debug? Via RMC abstraction or directly accessing server?

What rack-level manageability capabilities aresupported?Rack Level (northbound) Inventory Power-on/Reboot/ShutdownDrives the Power usagesouthboundInterface Power limitrequirements Temperature (profile?) Update firmware on all servers Status/HealthNode Level (southbound) Inventory Power-on/Reboot/Shutdown Power usage Power limit Temperature (profile?) Update firmware on all devices Status/HealthThe southbound Redfish interface shouldaligned with the OCP platform profiles

How do RMC Clients and RMC Services interact?Two extrema exists for the interaction models1. The RMC Client managesthe server, via the RMCabstraction model Does not see theunderlying complexity2. Upon failure, the RMCClient accesses the serverdirectlyRMC erver1. The RMC Client managesthe server, directly2. Upon failure, the RMCClient accesses the RMCdirectService, to reboot ordiagnose the server

Call to ActionParticipate in the OpenRMC project Attend the OpenRMC meetings - Wiki1 Join the discussion - mail-list2 Help priorities the rack-level manageability needs Help develop and test the OpenRMC rdware Management/Open RMC2https://ocp-all.groups.io/g/OpenRMC

Management Project. Motivation for OpenRMC 1. System Firmware (BIOS) OCP System Firmware project 2. BMC Firmware . (Redfish) BMC OS NIC NC-SI BIOS CPU BMC FW SW Agent In-band device device RMC Service other Rack Mgr Controller With OpenB