oxidecomputer / oxidecomputer/console
Dynamic quotas / allocation priorities
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
- Quotas to this point are soft boundaries that prevent users from manually creating resources that pass the quota but does not respond to system allocation changes
- Operators and users should be able to signify importance or priorities of specific services. When the system's resources are reduced (a sled pulled for instance), and services that previously had plenty of capacity are now over capacity, we should be able to dynamically spin down lower priority services and tighten the quotas for higher priority services to ensure we don’t exhaust the rack resources further.
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 how operators and users express service priorities, how reduced rack capacity is detected, and what spinning down services and tightening quotas should mean; define acceptance criteria before locating the relevant implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100