Skip to content
drewwalton-ocp edited this page Nov 17, 2026 · 8 revisions

Table of Contents

Welcome

Welcome to the OCP RAS API workstream. This is a CLA workstream of the OCP Hardware Management Project
This workstream is under CLA so in order to participate we need to sign a RAS API CLA.
A pdf of the latest CLA can be downloaded from RAS API CLA pdf
Disclaimer: Please do not submit any confidential information to the Project Community.
All presentation materials, proposals, meeting minutes and/or supporting documents can be utilize for the upcoming RAS API specification.
If you have any questions please contact OCP.

Workstream Overview

This workstream will be working on creating the RAS API specification.

Problem Statement

Having no industry standard for RAS management makes each HW vendor solution specific and resource intensive; while delaying RAS feature adoption.

When creating a specification to solve the standardization problem some major pain points need to be considered:

  • Specification for common abstraction for RAS between software and hardware that is vendor agnostic as well as platform agnostic.
  • Connectivity for RAS management should allow co-existence of In Band and Out of Band methods
  • Logging mechanism must solve RAS unique problems (Error storms, error sampling, etc.)
  • RAS feature abstraction should be generic enough to have open source drivers that can do a reasonable job at managing RAS;
    while leaving the opportunity for hardware vendor to differentiate and keep innovating.

Contributions

Get the *latest specification release*: Revision 0.96.

Workstream Leadership

Methodology

The workstream sets the big-picture vision. We plan to meet with companies that agree with this objective in order to draft a complete specification that solves the problem statement. Industry forums are expected to standardize the protocol mapping to the relevant interfaces, e.g. Redfish or PLDM.

As industry forums map the RAS API concepts to their system management protocols, we will add links to the specification where possible.

Here is an (example Redfish mapping of the RAS API)https://github.com/opencomputeproject/OCP-HM-RAS_API/blob/main/docs/OCP-RAS-API-Redfish-Specification-v1.0.pdf that was started by Microsoft and reviewed by RAS API workstream participants. It uses Oem.OpenCompute_FaultMgmt as an OEM identifier. This mapping is expected to be superseded by a Redfish mapping from DMTF.

Get Involved

The process to join the workstream is as follows:

This is a link to the CLA that needs to be signed in order to participate in the workstream. RAS API CLA

Workstream Meetings require a signed CLA, please add yourself to the communication channels to get the invitation after signing the CLA.

Mailing List

Participate in the discussion, mailing list: OCP-RAS-API@OCP-All.groups.io Mailing List Info

Links to Documents

Presentations, WIP/prerelease Drafts & Other Documents

OCP Presentation Template - please contact michael@opencompute.org for a copy