oxidecomputer / oxidecomputer/propolis
Consider adding support for NVMe OCP Error Injection
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
While many of the other features of the OCP datacenter specification don't really apply to our emulated devices, I think it'd be nice if we had support for this. Whether this takes the form of us pretending to be another device or us just adding support for it as a first class thing, I think it'd be useful to help with end-to-end testing. There's probably only a subset of these that make sense for us, depending on how far we want to go down the emulation path, but something for us to figure out and think about.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the NVMe OCP Error Injection specification and the project's emulated-device architecture, then identify which error-injection subset supports end-to-end testing. Done means agreeing on the emulation approach and implementing the selected support with coverage for the relevant testing scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100