Hardware Management/SpecsAndDesigns: Difference between revisions

From OpenCompute
Jump to navigation Jump to search
mNo edit summary
 
(44 intermediate revisions by 4 users not shown)
Line 5: Line 5:
=== OCP Redfish Profile ===
=== OCP Redfish Profile ===


'''Baseline and Server profile specs under review'''
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.
* [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])''


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


===LAVA LMP===
{| class="wikitable"
|+ 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:
----


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


===DRAFT of the Open Hardware Machine Management Specifications v1.01 (PDF)===
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


OCP Hardware Management Specification: Remote Machine Management v1.01 Draft: 02-25-2014
[http://files.opencompute.org/oc/public.php?service=files&t=c3ee8db5c9e64c1ddecc71fe084afaf0 Firmware Update Requirements version 0.2b PDF]
----


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


=== Charter for the Open Hardware Management Track (PDF)===
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 Open Hardware Management Track Draft: 12-28-2011
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=ad23158efca9a37e704046e3cbfdc209
[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


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


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


----
----


===DRAFT Hardware Management Specifications for IPMI===
===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 90: Line 173:
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.

Latest revision as of 20:08, 15 August 2022

Specs and Designs[edit]

This page contains links to the Specs ad Designs for the OCP Hardware Management Project

OCP Redfish Profile[edit]

Profiles can be found at OCP Profile repository. The Redfish Interop Validator will test conformance against a profile.

Approved documents
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
Specs under review
Document Version Date Description License
none - - -
Related documents
Document Version Date Description License
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[edit]

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:

  1. General: general firmware update requirements
  2. Security: requirements related to the integrity and authenticity of the image
  3. Control: requirements related to how firmware updates are controlled
  4. Status: requirements related to how/what status is available

Firmware Update Requirements version 0.2b PDF

Cloud Server Multi Node System Specification[edit]

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.

Cloud Server Multi Node System Specification version V0.7.5, Date August 19,2015 PDF

Presentations[edit]

Links to Open Source Projects[edit]

DRAFT Hardware Management Specifications for IPMI (Legacy)[edit]

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 Specifications for IPMI
Specification Version Date Description License
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.

Retrieved from "https://staging2.opencompute.org/w/index.php?title=Hardware_Management/SpecsAndDesigns&oldid=12373"