oxidecomputer / oxidecomputer/crucible
Set a quota on the overall crucible dataset, not just the region
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
We set a quota and a reservation at the region level for crucible regions.
We should also set a quota (and a reservation, maybe?) on the entire crucible dataset, to prevent
crucible from taking storage resources away from other zones that we may be sharing with.
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 existing region-level quota and reservation implementation in the Crucible codebase. Determine how the overall crucible dataset is represented and define completion as enforcing a dataset-wide quota; whether a corresponding reservation is required remains unspecified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100