oxidecomputer / oxidecomputer/omicron
Dataset accounting: VMM zone filesystems should be explicitly requested
Open
Nobody has claimed this yet.
nexus
Sled Agent
storage
- 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 instances:
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/instance.rs at the linked instance provisioning code, then trace how the zone filesystem location is selected and how Nexus receives provisioning information. The work is done when Nexus can explicitly account for the zone filesystem allocation instead of the sled agent choosing a random U.2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100