Specs and Designs
This page contains links to the Specs ad Designs for the OCP Hardware Management Project
OCP Redfish Profile
|Usage Guide for Baseline Profile||v1.0.1||2021||Usage Guide for the Baseline Hardware Management API v1.0.1||CC|
|Usage Guide for OpenRMC Northbound Profile||v1.0.0||2021||Usage Guide for the OpenRMC Northbound API v1.0.0||CC|
|Usage Guide for Server Profile||v1.0.0||2021||Usage Guide for the Server Hardware Management API v1.0.0||CC|
|DMTF WIP and DMTF Redfish||-||-||Collection of DMTF work in progress, and the official DMTF Redfish Forum repository||-|
|Redfish OCP Profile (XLS)||v0.5||June 1, 2016||Mapping Redfish properties to OCP requirements (initial worksheet)||-|
|Redfish OCP Profile||v1||Feb 21, 2017||Presentation to the HW Management group meeting||-|
|Redfish Conformance Test Suite||-||2021||The Redfish Forum's Guidance for a Conformance Test Suite||-|
|OpenBMC||-||Nov 17, 2016||Presentation to the HW Management group meeting||-|
DRAFT Requirements for Firmware Update
The draft specification identifies the firmware update requirements that all OCP compliant platforms and devices must adhere to. The Firmware Update solution is for the application the user interfaces and the capabilities of the embedded firmware on the servers, switches and storage devices. The requirements are broken into four sections:
- General: general firmware update requirements
- Security: requirements related to the integrity and authenticity of the image
- Control: requirements related to how firmware updates are controlled
- Status: requirements related to how/what status is available
Cloud Server Multi Node System Specification
A description and requirements of a Cloud Server which is either a server, enclosure or rack that contains other uniquely addressable and managable devices. The document's purpose is to have a single Ethernet connection to the Cloud Server and document the possible bus architectures, managment protocols and minimum expected functionality of the Nodes contained in the Cloud Server.
The Clould Server's BMC with a Ethernet connection to the outside world is the called the Spine BMC and IPMI RMCP or RESTfull protocols are allowed. Internally the Spine BMC communicates to the Node using SMBus and GPIO which determines Node presence, Node power control and ALERT signaling.
The Node requirements include a subset of the IPMI 2.0 commands. The Spine BMC may have a Serial Console session to each Node.
- OCP Profiles for Hardware Management - presented by Hemal Shah and John Leung, OCP Global Summit 2019.
- PMCI Standards for Hardware Management - presented by Hemal Shah and Patrick Caporale, OCP Global Summit 2019.
- Common Profile Updates -Process & Status, August 6, 2020
Links to Open Source Projects
DRAFT Hardware Management Specifications for IPMI (Legacy)
Proposed specifications for the IPMI implementation on any device using IPMI. This includes PDUs, Servers, Switches and Storage devices. The specifications allow a Data Center System Manager uniform remote access to the hardware in the rack. All the specifications have questions in red.
|OCP ID||0.04||June 9, 2014||Identify all OCP specifications implemented by a single IPM Controller||OWFa 1.0|
|ICAP Base||0.02||June 9, 2014||The basic functions of an OCP IPM Controller that a Data Center System Manager depends on||OWFa 1.0|
|ICAP OPTI||0.02||June 9, 2014||The identification of XFSP+/QSFP bays and protocol independent monitoring of optical links for XSFP+/QSFP modules||OWFa 1.0|
|ICAP DRAM||0.03||June 9, 2014||The identification and temperature monitoring of DDR3/DDR4 modules||OWFa 1.0|
As Data Centers raise room temperatures, potentially on a daily basis, the ICAP OPTI and ICAP DRAM provide feedback on how close the hardware is to the manufacturer define thermal limits.