oxidecomputer / oxidecomputer/omicron
Track image storage usage
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Storage resource usage is currently tracked for disks and snapshots in the virtual_provisioning_resource and virtual_provisioning_collection database tables. When an image is made from a snapshot, it shares the same backend (a crucible read-only region) so we do not count images towards resource usage. However, a snapshot can be deleted while the image created from it lives on. When that happens, we decrement the snapshot usage from the database table. The image resource usage is "leaked" in this case. We'll need a way to account for image usage when their snapshot origins are deleted.
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 how snapshot deletion updates the virtual_provisioning_resource and virtual_provisioning_collection tables, then examine how images retain their snapshot origins. Define how image usage should be accounted for after an origin is deleted. Done means image-backed usage remains represented accurately instead of being leaked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100