oxidecomputer / oxidecomputer/omicron
Want to expose maximum amount of provisionable memory per sled to operator
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Currently we show 1011.98GB of memory (or the equivalent for 2TiB gimlets) in the inventory UI/API. This is the raw capacity but not the amount usable for provisioning instances. The actual usable memory is bound by the size of the reservoir. Some customers were confused on why they couldn't use up to 1011GiB. The same issue applies to usable storage capacity which has system reservation subtracted from the raw capacity. Such information should be made more transparent to operators in the system hardware query responses.
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 tracing the inventory UI/API and the system hardware query responses that report sled memory and storage capacity. Identify where raw capacity is assembled and how reservoir or system reservations are represented. Done means operators can see the maximum provisionable memory and usable storage in those responses, with behavior covered by the relevant tests if they exist.
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
- 42/100