oxidecomputer / oxidecomputer/crucible
Capacity management (allocation vs used vs free space)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
We talked at some point about this, maybe looking at the zfs dataset and free space, not the same as the space inventory that Nexus and or Sled Agent keeps.
[jmc] there are at least two areas to consider here: reservations (managed in Nexus based on a nominal capacity), and actual usage/capacity (measured in Crucible and/or the Sled Agent)
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
The issue names no files, tests, or entry points. Start by clarifying the separate requirements for reservations, nominal allocation, actual usage, and free space across Nexus, Crucible, the Sled Agent, and ZFS; done should be a documented design with an agreed measurement source and behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100