oxidecomputer / oxidecomputer/crucible
Deal with reboots during region create
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
The reconciliation logic handles being interrupted at any time, but region / extent create does not. Follow up with the comments on https://github.com/oxidecomputer/crucible/pull/306 regarding reboot safety, and additionally think about other areas of the code that are not reboot safe.
Contributor guide
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 reading the comments on pull request 306 and the existing reconciliation logic, then compare them with region and extent creation. Identify the reboot-safety gaps and review other code areas for the same concern. Done means region and extent creation, along with any related areas found, safely handle interruption and reboot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100