Different SKU support within one VC
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 554
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 14
Description
What would you like to be added:
Different SKU configuration support within one virtual cluster
Why is this needed:
Different training/inference task may have different GPU/CPU/MEMORY requirement. Maybe it is flexible to have different SKU within one cluster.
Without this feature, how does the current module work:
Only one SKU unit for one cluster. It works but it might not the best usage.
Components that may involve changes:
rest-server, hivedscheduler
Contributor guide
No contributing guide indexed for this repository
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 reading the current one-SKU behavior in the rest-server and hivedscheduler components, then trace how a virtual cluster's SKU is configured and consumed. Done means one virtual cluster can support different SKUs for tasks with different GPU, CPU, or memory requirements, with scheduling behavior covering those configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100