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'''
* [http://files.opencompute.org/oc/public.php?service=files&t=a91f71f1bc0d72e8ce55a745d82b3379 OCP Hardware Mgmt Baseline v0.1.0.doc]
* [http://files.opencompute.org/oc/public.php?service=files&t=907f90acbc0d9384aa6418e5270363e3 OCPManagedDevicev1_0.json]
: ''(we plan to announce approved specs by [http://www.opencompute.org/ocp-u.s.-summit-2018/ OCP Summit 2018])''


{| class="wikitable"
'''Related documents [https://www.dmtf.org/standards/wip DMTF Work In Progress]''':
|+ style="text-align: left" | Approved documents
* [https://www.dmtf.org/sites/default/files/standards/documents/DSP2049_0.2.2b.pdf DSP2049 OCP Hardware Management with Redfish v0.2.2b 30 May 2017 (PDF)]
|-
* [http://files.opencompute.org/oc/public.php?service=files&t=bb5d7c90ec35fa97759e065c5dbf5c38 Redfish OCP Profile xls]
! Document
* [http://files.opencompute.org/oc/public.php?service=files&t=c745936fcddec29ce2a08c6bf69ff75f OpenBMC Presentation]
! Version
* [http://files.opencompute.org/oc/public.php?service=files&t=e60b2f8bbcf6ebb615d19551f278345a Redfish OCP Profile pdf] ** Presented in mtg, Feb 21.
! 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"
----
|+ style="text-align: left" | Specs under review
|-
! Document
! Version
! Date
! Description
! License
|-
| none
| -
| -
| -
|-
|}


{| class="wikitable"
===LAVA LMP===
|+ style="text-align: left" | Related documents
|-
! Document
! Version
! Date
! Description
! License
|-
| [https://www.dmtf.org/standards/wip DMTF WIP] and [https://www.dmtf.org/standards/redfish DMTF Redfish]
| -
| -
| Collection of DMTF work in progress, and the official DMTF Redfish Forum repository
| -
|-
| [http://files.opencompute.org/oc/public.php?service=files&t=bb5d7c90ec35fa97759e065c5dbf5c38 Redfish OCP Profile (XLS)]
| v0.5
| June 1, 2016
| Mapping Redfish properties to OCP requirements (initial worksheet)
| -
|-
| [http://files.opencompute.org/oc/public.php?service=files&t=e60b2f8bbcf6ebb615d19551f278345a Redfish OCP Profile]
| v1
| Feb 21, 2017
| Presentation to the HW Management group meeting
| -
|-
|-
| [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]
| -
| Nov 17, 2016
| Presentation to the HW Management group meeting
| -
|}


----
More information about LAVA LMP can be found at:


===DRAFT Requirements for Firmware Update===
* https://github.com/opencomputeproject/lava-lmp-firmware/subscription
* https://github.com/opencomputeproject/lava-lmp-lmpd/subscription


The draft specification identifies the firmware update requirements that all OCP compliant platforms and devices must adhere to.
===DRAFT of the Open Hardware Machine Management Specifications v1.01 (PDF)===
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]
OCP Hardware Management Specification: Remote Machine Management v1.01 Draft: 02-25-2014
----


===Cloud Server Multi Node System Specification===
* http://files.opencompute.org/oc/public.php?service=files&t=125cdfa0c090cb2106d8546f08561f6d


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.
=== Charter for the Open Hardware Management Track (PDF)===


The Node requirements include a subset of the IPMI 2.0 commands. The Spine BMC may have a Serial Console session to each Node.
Charter for Open Hardware Management Track Draft: 12-28-2011


[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]
* http://files.opencompute.org/oc/public.php?service=files&t=ad23158efca9a37e704046e3cbfdc209


----
----
===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


----
===DRAFT Charter for Open Hardware Management Track w/Japanese Translation (PDF)===
 
Proposed track for Open Hardware Management


===Links to Open Source Projects===
* http://files.opencompute.org/oc/public.php?service=files&t=537a0c1930f02319509930768b23c6c3
* [https://en.wikipedia.org/wiki/OpenBMC Link to OpenBMC]


----
----


===DRAFT Hardware Management Specifications for IPMI (Legacy)===
===DRAFT Hardware Management Specifications for IPMI===


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 90:
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.
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"