-
Notifications
You must be signed in to change notification settings - Fork 13
Home
Kevin Kifer edited this page Jan 26, 2024
·
3 revisions
- Welcome to the OCP OpenRMC Subproject. This subproject specifies the northbound manageability interface for a rack manager.
- This Project is open to the public and we welcome all those who would like to be involved.
- Disclaimer: Please do not submit any confidential information to the Project Community. All presentation materials, proposals, meeting minutes and/or supporting documents are published by OCP and are open to the public in accordance to OCP's Bylaws and IP Policy. This can be found on the OCP OCP Policies page. If you have any questions please contact OCP.
- - [email protected] (Meta)
If you interested in get involved with OpenRMC:
- - Participate in the discussion, mailing list: [email protected] (Mailing List Info)
- - Attend the OpenRMC meetings
- - Provide feedback and comments to working documents
Regular meetings are held on the 2nd and 4th Tuesday of the month. For meeting logistics, see the calendar at the bottom of the Hardware Mgmt Project webpage.
- - Agenda and Consolidated Minutes
- - Recording of past calls are available at the bottom of this wiki page
- - Usage Guide and Requirements for OpenRMC Northbound API v1.0.0 (June 2021, link)
- - Profile for OpenRMC v1.0.1 (Jan 2022, link)
- - Inspur OpenRMC Hardware/Firmware bundle - Click "Available Design Collateral". (Jan 2021, https://www.opencompute.org/contributions?refinementList%5Bcontributor%5D%5B0%5D=Inspur&refinementList%5Bproject%5D%5B0%5D=Hardware%20Management%20%3E%20OpenRMC&refinementList%5Baccept_year%5D%5B0%5D=2020&configure%5BfacetFilters%5D%5B0%5D=archived%3Afalse)
- - (obsolete) OpenRMC Design Specification v1.0.0 (Oct 2020, link)
- - Usage Guide for OpenRMC API v1.1.0, draft 0.6 (May 2023, link)
- - Draft OpenRMC v1.1 profile (Mar 2022, link) File comments as Github issues against the pull request
- - "Adding Redfish to Device Manager" (OCP Global Summit 2022, link)
- - "OpenRMC Update" (OCP Global Summit, Mar 2020, link)
- - "Open Rack Management Controller Subproject" (OCP Regional Summit, Sept 2019, link)
- - "OpenRMC Subproject" (OCP Global Summmit, Mar 2019, link)
- - OpenRMC-DM Merge logistics
- - Directional Change for OpenRMC repository (Oct 2019)
- - 2019 OpenRMC project overview presentation (Jan 2019)
- - Inspur OpenRMC Hardware/Firmware bundle - Click "Available Design Collateral". (Jan 2021, https://www.opencompute.org/contributions?refinementList%5Bcontributor%5D%5B0%5D=Inspur&refinementList%5Bproject%5D%5B0%5D=Hardware%20Management%20%3E%20OpenRMC&refinementList%5Baccept_year%5D%5B0%5D=2020&configure%5BfacetFilters%5D%5B0%5D=archived%3Afalse)
- - OpenRMC Hardware (Jan 2020)
- - "Inspur RMC Solution Facilitates Datacenter Management" (Sept 2019, OCP Regional Summit)
- - Overview presentation of Inspur Rack Manager
- - Overview presentation of Inspur OpenRMC code contribution (July 2019)
- - Demo video of Inspur OpenRMC GUI (July 2019)
- - August 23th, 2022 (Usage Guide for OpenRMC 1.1)
- - March 15th, 2022 - No Call
- - February 15th, 2022
- - January 18th, 2022
- - November 16th, 2021
- - October 19th, 2021
- - September 21st, 2021
- - August 17th, 2021
- - July 20th, 2021
- - June 15th, 2021
- - May 18th, 2021
- - April 20th, 2021
- - March 16th, 2021
- - February 16th, 2021
- - January 19th, 2021
- - December 15th, 2020
- - November 17th, 2020
- - October 20th, 2020
- - September 15th, 2020
- - September 1st, 2020
- - August 18th, 2020
- - June 23rd, 2020
- - April 14th, 2020
- - February 4th, 2020
- - January 21st, 2020
- - November 26th, 2019
- - October 29th, 2019
- - October 1st, 2019
- - August 20th, 2019
- - July 2nd, 2019
- - May 28th, 2019
- - May 14th, 2019
- - April 30th, 2019
- - April 2nd, 2019
- - March 19th, 2019
- - March 5th, 2019
- - February 19th, 2019
- - February 5th, 2019
- - January 22nd, 2019
- - January 15th, 2019
- - December 11th, 2018
- - November 27th, 2018
- - November 13th, 2018
- - October 30th, 2018: first regular meeting
- - October 16th, 2018: Kickoff Call
- Github Process for repository
- Community clarifies Issue via comments. Comments can be made individually or via a meeting. Comments may include guidance for the solution.
- Community will accept/approve or reject the issue
- Issue shall be labeled as '_approved_', '_wontfix_' or '_duplicate_'. Issue may be labeled as '_bug_', '_enhancement_', '_documentation_'
- One or more 'Assignee's may self-assign (volunteer)
- Assignee(s) forks the repository
- Assignee makes a pull request and update the Issue with PR#
- When the pull request is ready to be merged, the PR shall be labeled '_Ready to Review_'
- Reviewers are assigned to verify or test the PR.
- Once verified by a reviewer, a comment will be added. Once all the verifications are complete, the PR is labeled “verified” by the reviewers.
- Community discusses and approves the pull request. TSC arbitrates any disputes. Once approved, the PR shall be label '_Approved to Merge_'
- Project leadership merges the pull request