Editing RAS API Workstream
Jump to navigation
Jump to search
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 4: | Line 4: | ||
:Welcome to the OCP '''RAS API''' workstream. This is a CLA workstream of the [https://www.opencompute.org/projects/hardware-management OCP Hardware Management Project] | :Welcome to the OCP '''RAS API''' workstream. This is a CLA workstream of the [https://www.opencompute.org/projects/hardware-management OCP Hardware Management Project] | ||
:This workstream is under CLA so in order to participate we need to sign | :This workstream is under CLA so in order to participate we need to sign an CLA [link]. | ||
:'''Disclaimer''': Please do not submit any confidential information to the Project Community. <br />All presentation materials, proposals, meeting minutes and/or supporting documents can be utilize for the upcoming RAS API specification. <br /> If you have any questions please contact OCP. | :'''Disclaimer''': Please do not submit any confidential information to the Project Community. <br />All presentation materials, proposals, meeting minutes and/or supporting documents can be utilize for the upcoming RAS API specification. <br /> If you have any questions please contact OCP. | ||
Line 15: | Line 15: | ||
Having no industry standard for RAS management makes each HW vendor solution specific and resource intensive; while delaying RAS feature adoption. <br /> | Having no industry standard for RAS management makes each HW vendor solution specific and resource intensive; while delaying RAS feature adoption. <br /> | ||
When creating a specification to solve the standardization problem some major pain points need to be considered: | 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'''. | * 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 | * Connectivity for RAS management should allow '''co-existence''' of In Band and Out of Band methods | ||
Line 25: | Line 23: | ||
===Methodology=== | ===Methodology=== | ||
The current baseline is [https:// | The current baseline is [https://drive.google.com/drive/folders/ 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== | ==Workstream Leadership== | ||
:- [mailto:acwalton@google.com Drew Walton] (Google), [mailto:antonio.j.hasbun.marin@intel.com Antonio Hasbun] (Intel) | |||
==Get Involved== | ==Get Involved== | ||
We are setting up the time to meet, so please as you join and start the singing process for the CLA contact the leads of this workstream to let them know of your preferred schedule for meeting. | |||
===Workstream Meets every TBD === | |||
: - [https://global.gotomeeting.com/join/ Link to the Meeting] | |||
: - You can also dial in using your phone : US (Toll Free): 1 877 309 2073 / US: +1 (646) 749-3129 - (Access Code: ) | |||
===Mailing List === | ===Mailing List === | ||
Participate in the discussion, mailing list: OCP- @OCP-All.groups.io [https://ocp-all.groups.io/g/OCP- / Mailing List Info] | |||
==Links to Documents== | ==Links to Documents== | ||
===[https://drive.google.com/drive/folders/ Work in Progress Documents Folder]:=== | |||
===Presentations & Other Documents=== | ===Presentations & Other Documents=== | ||
OCP Presentation Template - please contact [mailto:michael@opencompute.org Michael Schill] or [mailto:archna@opencompute.org Archna Haylock] for a copy | |||
==Past Meeting Recordings== |