oxidecomputer / oxidecomputer/propolis
Tell Nexus repair progress for crucible regions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
Originally posted by @pfmooney in https://github.com/oxidecomputer/propolis/issues/471#issuecomment-1644619204
If crucible starts up and has to repair inconsistent downstairs, it may take several minutes (depending on volume size and repair work) before the upstairs will become ready for
IO from the guest.
We need a way for propolis to get this info from crucible, and pass it up to Nexus so Nexus can display some sort of progress to the user.
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
Start by tracing how Propolis learns that Crucible repair has completed and how status could be passed to Nexus; no files or tests are identified in the issue. Define the progress information needed during repair and verify that Nexus can present it before guest I/O becomes ready.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100