Hardware Management/SpecsAndDesigns: Difference between revisions
Line 28: | Line 28: | ||
| Usage Guide for the OpenRMC Northbound API v1.0.0 | | Usage Guide for the OpenRMC Northbound API v1.0.0 | ||
| CC | | CC | ||
|} | |- | ||
| [https://drive.google.com/file/d/16Z8FvsHM1aD3rqGVPpouxH14-SNF3qgj Usage Guide for Server Profile] | |||
| v1.0.0 | |||
| 2021 | |||
| Usage Guide for the Server Hardware Management API v1.0.0 | |||
| CC} | |||
Line 40: | Line 45: | ||
! License | ! License | ||
|- | |- | ||
|- | |- | ||
|} | |} |
Revision as of 19:55, 15 August 2022
Specs and Designs
This page contains links to the Specs ad Designs for the OCP Hardware Management Project
OCP Redfish Profile
Profiles can be found at OCP Profile repository
Document | Version | Date | Description | License | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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}
DRAFT Requirements for Firmware UpdateThe 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:
Firmware Update Requirements version 0.2b PDF Cloud Server Multi Node System SpecificationA 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. Cloud Server Multi Node System Specification version V0.7.5, Date August 19,2015 PDF Presentations
Links to Open Source ProjectsDRAFT 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.
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. |