Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support MIG Instances #175

Closed
tunahanertekin opened this issue Sep 7, 2023 · 0 comments · Fixed by #176
Closed

Support MIG Instances #175

tunahanertekin opened this issue Sep 7, 2023 · 0 comments · Fixed by #176
Assignees
Labels
enhancement New feature or request robot-dev Development process of robot

Comments

@tunahanertekin
Copy link
Member

What would you like to be added?

In current setup, VDI, IDE and LaunchManager workloads can use GPU using the resource label nvidia.com/gpu. GPU instances are MIG-disabled by default. Robots should support MIG-enabled GPUs and different MIG instances. It can be done via labels like robolaunch.io/vdi-gpu-mig-instance.

Why is this needed?

It's needed to schedule computational and graphical processes to different GPU instances.

@tunahanertekin tunahanertekin added enhancement New feature or request robot-dev Development process of robot labels Sep 7, 2023
@tunahanertekin tunahanertekin self-assigned this Sep 7, 2023
@tunahanertekin tunahanertekin linked a pull request Sep 7, 2023 that will close this issue
1 task
@github-project-automation github-project-automation bot moved this from In Progress to Done in Kubernetes Operator Development Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request robot-dev Development process of robot
Projects
Development

Successfully merging a pull request may close this issue.

1 participant