add support to enflame DTO
Open
Nobody has claimed this yet.
- #5139 by @beingj — closed without merging
1.5 candidate
C-EnFlame
raised by customer
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 554
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 14
Description
Track tasks to add support to enflame DTU
Copied from #5138
- deploy script: pre checks / installation items for each machine model
- exporter: additional exporters for machine models besides nvidia gpu / cpu machine.
- rest-server: When generating pod spec, rest-server should be aware of environmental variables used by other device in addition to NVIDIA_VISIBLE_DEVICES and PAI_AMD_VISIBLE_DEVICES.
- scheduler: health report for computing device. This is not mandatory since node-level health check is provided by k8s already.
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 the deploy script, exporter, rest-server pod-spec generation, and scheduler health-report paths named in the checklist, along with the related closed pull request #5139. Determine the existing NVIDIA and AMD device-handling flows and the Enflame machine models they must cover. Done means the checklist items are implemented and their relevant deployment, export, REST, and scheduling checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100