Editing Hardware Management/SpecsAndDesigns

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 5: Line 5:
=== OCP Redfish Profile ===
=== OCP Redfish Profile ===


Profiles can be found at [https://github.com/opencomputeproject/HWMgmt-OCP-Profiles OCP Profile repository]. The [https://drive.google.com/file/d/1R05H0LaqG9DmTDJdMGhKkLckpwIfeONT/view?usp=sharing Redfish Interop Validator] will test conformance against a profile.
==== '''Baseline and Server profile''' ====
 
Specs under review ''(announced at [http://www.opencompute.org/ocp-u.s.-summit-2018/ OCP Summit 2018])''
{| class="wikitable"
|+ style="text-align: left" | Approved documents
|-
! Document
! Version
! Date
! Description
! License
|-
| [https://www.opencompute.org/documents/usage-guide-for-baseline-hw-mgmt-api-v1-0-1-final-pdf Usage Guide for Baseline Profile]
| v1.0.1
| 2021
| Usage Guide for the Baseline Hardware Management API v1.0.1
| CC
|-
|-
| [https://www.opencompute.org/documents/openrmc-1-0-0-usageguide-final-b-1-pdf Usage Guide for OpenRMC Northbound Profile]
| v1.0.0
| 2021
| Usage Guide for the OpenRMC Northbound API v1.0.0
| 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
|}


{| class="wikitable"
{| class="wikitable"
|+ style="text-align: left" | Specs under review
|+ style="text-align: left" | Specs under review
|-
|-
! Document
! Specification
! Version
! Version
! Date
! Date
Line 45: Line 17:
! License
! License
|-
|-
| none
| [http://files.opencompute.org/oc/public.php?service=files&t=966a86fe9a44c36f9f7669e732622901 Comments 20180417.pdf]
| -
| v2
| -
| -
| Comments received during review period; specifically HW Management meeting April 17, 2018
| -
| -
|-
|-
| [http://files.opencompute.org/oc/public.php?service=files&t=1c8c2ee9d04ef0eed7a683291c9e3506 Baseline Profile] - [http://files.opencompute.org/oc/public.php?service=files&t=4edfc8cbc3b183f46f7fef5b45b59fa4 (JSON)]
| Spec:v1.0, JSON:v1.0
| April 18, 2018
| OCP Redfish Profile - Baseline Hardware Management specification, and JSON schema
| OWFa 1.0
|-
| [http://files.opencompute.org/oc/public.php?service=files&t=77f9924b9573113bf6274fa4d7e72787 Server Profile] - [http://files.opencompute.org/oc/public.php?service=files&t=83137cf9df08e7b5c82c520827baab16 (JSON)]
| Spec:v0.2.1, JSON:v0.2.3
| April 18, 2018
| OCP Redfish Profile - Server Hardware Management extensions, and JSON schema
| OWFa 1.0
|}
|}


{| class="wikitable"
{| class="wikitable"
|+ style="text-align: left" | Related documents
|+ style="text-align: left" | Related documents
|-
|-
! Document
! Specification
! Version
! Version
! Date
! Date
Line 73: Line 58:
| -
| -
|-
|-
| [http://files.opencompute.org/oc/public.php?service=files&t=e60b2f8bbcf6ebb615d19551f278345a Redfish OCP Profile]
| [http://files.opencompute.org/oc/public.php?service=files&t=e60b2f8bbcf6ebb615d19551f278345a Redfish OCP Profile (PDF Presentation)]
| v1
| v1
| Feb 21, 2017
| Feb 21, 2017
| Presentation to the HW Management group meeting
| Presentation to the HW Management group meeting Feb 21, 2017
| -
|-
|-
| [https://drive.google.com/file/d/1R05H0LaqG9DmTDJdMGhKkLckpwIfeONT/view?usp=sharing Redfish Conformance Test Suite]
| -
| 2021
| The Redfish Forum's Guidance for a Conformance Test Suite
| -
| -
|-
|-
| [http://files.opencompute.org/oc/public.php?service=files&t=c745936fcddec29ce2a08c6bf69ff75f OpenBMC]
| [http://files.opencompute.org/oc/public.php?service=files&t=c745936fcddec29ce2a08c6bf69ff75f OpenBMC (PDF Presentation)]
| -
| -
| Nov 17, 2016
| Nov 17, 2016
| Presentation to the HW Management group meeting
| Presentation to the HW Management group meeting Feb 21, 2017
| -
| -
|}
|}


----


===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
[http://files.opencompute.org/oc/public.php?service=files&t=c3ee8db5c9e64c1ddecc71fe084afaf0 Firmware Update Requirements version 0.2b PDF]
----
----


===Cloud Server Multi Node System Specification===
===DRAFT Hardware Management Specifications for IPMI===
 
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.
 
[http://files.opencompute.org/oc/public.php?service=files&t=1eb58f54e79a48f0007de6b7379a093f Cloud Server Multi Node System Specification version V0.7.5, Date August 19,2015  PDF]
 
----
===Presentations===
* [https://146a55aca6f00848c565-a7635525d40ac1c70300198708936b4e.ssl.cf1.rackcdn.com/images/94f8a3478db56eef7e8868159d193633c0116938.pdf OCP Profiles for Hardware Management] - presented by Hemal Shah and John Leung, OCP Global Summit 2019.
* [https://146a55aca6f00848c565-a7635525d40ac1c70300198708936b4e.ssl.cf1.rackcdn.com/images/efcddf341fa55a63177c0180152f6d59ed23449e.pdf PMCI Standards for Hardware Management] - presented by Hemal Shah and Patrick Caporale, OCP Global Summit 2019.
* [https://drive.google.com/file/d/1qnUHIevSUUe3Bszg85EJiCTPar484wOm/edit Common Profile Updates] -Process & Status, August 6, 2020
 
----
 
===Links to Open Source Projects===
* [https://en.wikipedia.org/wiki/OpenBMC Link to OpenBMC]
 
----
 
===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.
Proposed specifications for the IPMI implementation on any device using IPMI. This includes PDUs, Servers, Switches and Storage devices.
Line 173: Line 116:
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.
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.
----
----
===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
[http://files.opencompute.org/oc/public.php?service=files&t=c3ee8db5c9e64c1ddecc71fe084afaf0 Firmware Update Requirements version 0.2b PDF]
----
===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.
[http://files.opencompute.org/oc/public.php?service=files&t=1eb58f54e79a48f0007de6b7379a093f Cloud Server Multi Node System Specification version V0.7.5, Date August 19,2015  PDF]
===Miscellaneous Files===
* [http://files.opencompute.org/oc/public.php?service=files&t=64189159f78d34e4da0a9165d2a18ee0 PLDM for FW Updates PPTX] - presented by Yuval Itkin, Sept 19 mtg.
===Links to Open Source Projects===
* [https://en.wikipedia.org/wiki/OpenBMC Link to OpenBMC]
Please note that all contributions to OpenCompute may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see OpenCompute:Copyrights for details). Do not submit copyrighted work without permission!
Cancel Editing help (opens in new window)
Retrieved from "https://www.opencompute.org/w/index.php?title=Hardware_Management/SpecsAndDesigns"