-
Notifications
You must be signed in to change notification settings - Fork 5
Home
John Leung edited this page Dec 7, 2022
·
3 revisions
Issue is Opened – initial submittal
- 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 resolves issued (Read access role)
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'
- Pull Request - ‘ready to review’(needs Admin role)
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
The DeviceMgr-PSME is derived from the Intel RackScale PSME. The following changes from the RackScale-PSME have been noted:
- The RackScale PSME consisted of a generic Redfish application and multiple “agents”, which were deployed in specific environments. The network agent was run on a switch. In the DeviceMgr-PSME has disabled all agents except for the network agent and the chassis agent, both of which were heavily modified for the current needs.
- The RackScale-PSME's network agent did not expose a System resource
- The RackScale-PSME used libmicrohttpd for HTTP, not libnghttp2