RAS API Workstream: Difference between revisions

From OpenCompute
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 54: Line 54:


OCP Presentation Template - please contact [mailto:michael@opencompute.org Michael Schill] for a copy
OCP Presentation Template - please contact [mailto:michael@opencompute.org Michael Schill] for a copy
==Past Meeting Recordings==
* [https://www.youtube.com/watch?v=L5dc4_LNbSo January 30, 2024]
* [https://www.youtube.com/watch?v=16AWcXf2AJM January 16, 2024]
* [https://www.youtube.com/watch?v=khnzPrdT988 December 19, 2023]
* [https://www.youtube.com/watch?v=hv1GImUmA-g December 12, 2023]
* [https://www.youtube.com/watch?v=NBvBHovR-Qg December 05, 2023]
* [https://www.youtube.com/watch?v=PcQVw3pq09M November 28, 2023]
* [https://www.youtube.com/watch?v=uplsaLtRlAQ November 14, 2023]
* [https://www.youtube.com/watch?v=Y9FTmDnJ4TM October 31, 2023]
* [https://www.youtube.com/watch?v=lYJ4P8St4W8 October 03, 2023]
* [https://www.youtube.com/watch?v=mlZn_WIMRkE September 05, 2023]
* [https://www.youtube.com/watch?v=XfAlKfK4nCA August 22, 2023]
* [https://www.youtube.com/watch?v=JAtnh-i9dyk August 21, 2023]
* [https://www.youtube.com/watch?v=wfbO8C7nhi4 August 08, 2023]

Latest revision as of 22:37, 1 May 2024

OCP-Open-compute-hardware-fault-management-icon-3x-v1-1a.png

Welcome[edit]

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 .
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[edit]

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

Problem Statement[edit]

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.

Methodology[edit]

The current baseline is Revision 0.8. We plan to meet with companies that agree with this objective in order to draft a complete specification that solves the problem statement.

Workstream Leadership[edit]

Get Involved[edit]

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.[edit]

Mailing List[edit]

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

Links to Documents[edit]

Presentations & Other Documents[edit]

OCP Presentation Template - please contact Michael Schill for a copy