oxidecomputer / oxidecomputer/omicron
Let Nexus decide how to deal with old partitions on new U.2s
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
This will be necessary to resolve issues like https://github.com/oxidecomputer/omicron/issues/5128
Blocked by #5150 and #5151
When Nexus chooses to adopt a new physical disk into the control plane, it will have an opportunity to make a decision about "what to do with old partitions on this device". As we've seen in #5128 , not all U.2s will have uniform decisions, and it may make sense to overwrite them or ask an operator for additional input before proceeding.
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 #5128 and the blocking issues #5150 and #5151, then trace Nexus's decision point when adopting a physical disk. Define how old partitions on new U.2s should be handled, including when to overwrite them or request operator input; done means non-uniform devices have an explicit outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100