oxidecomputer / oxidecomputer/omicron
Dataset accounting: Probe zone filesystems should be explicitly requested
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Currently, the sled agent picks a random U.2 to hold the zone filesystem for probes
This, unfortunately, leaves nexus out-of-the-loop regarding space allocation within the zone dataset.
Nexus should be aware of where instances are provisioned to manage accounting explicitly.
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 in sled-agent/src/probe_manager.rs at the linked lines where a random U.2 is selected for the probe zone filesystem. Trace how Nexus currently learns about instance placement and how space is allocated within the zone dataset. Done means probe zone filesystem placement is explicitly requested or accounted for through Nexus rather than selected silently by the sled agent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100