redhat-developer / redhat-developer/mapt
[Task] Review GPU Compute Request params
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
This is a following for #408 during that PR there was a heavy refactor on the spot module,and based on comments from the issue currently the way to ask for GPU machines is directly using machine types(which was implemented within that PR)
Still getting machines base on GPU params is desirable and actually something missing as ATM those values are totally dismissed (although they are offered its values are not taking into account for compute type selection)
It is required to implement its usage
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 reviewing issue #408 and the spot module refactor described there, then trace how GPU request parameters reach compute type selection. Done means the supplied GPU parameters are used to select GPU-capable machines instead of being dismissed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100