oxidecomputer / oxidecomputer/omicron
want better dev experience for cleaning up VMM reservoir allocation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
For developers running a real sled agent, by default, sled agent will provision a VMM reservoir. This will claim some amount of memory on the machine for guests, and have other system effects related to claiming more memory (such as your system likely needing a swap device to be usable).
It would be nice if we had a good way to indicate to devs that they should consider reclaiming this memory after they are done running omicron. This can be done with the rsrvrctl tool today, but we could also consider doing it automatically as a part of the omicron uninstall tool, or a similarly automated solution.
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 examining the existing rsrvrctl workflow and the omicron uninstall tool mentioned in the issue. Determine whether cleanup should remain manual or be automated, then verify that the chosen behavior reclaims the VMM reservoir memory and avoids leaving unwanted system effects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100