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

Intel GPU not in default GPU vendor list in Jupyter Notebook server #7541

Closed
yshashix opened this issue Apr 9, 2024 · 3 comments · Fixed by #7635
Closed

Intel GPU not in default GPU vendor list in Jupyter Notebook server #7541

yshashix opened this issue Apr 9, 2024 · 3 comments · Fixed by #7635
Labels
Milestone

Comments

@yshashix
Copy link

yshashix commented Apr 9, 2024

/kind question
/kind feature
/area jupyter

Hello,

I use Kubeflow v1.8.0.
It seems that Intel GPU is not listed in default "GPU Vendor" in Jupyter Notebook server webui (when creating a notebook).
May I know when will it be added? I can see that one method is by editing configmap of jupyter web-app.

Thank you.

@yshashix
Copy link
Author

yshashix commented Apr 12, 2024

I have enabled in my Juypter Notebook server by editing jupyter web-app with following line:


    vendors:
            - limitsKey: "nvidia.com/gpu"
              uiName: "NVIDIA"
            - limitsKey: "amd.com/gpu"
              uiName: "AMD"
            - limitsKey: "gpu.intel.com/i915"
              uiName: "INTEL"

@thesuperzapper
Copy link
Member

thesuperzapper commented May 24, 2024

@yshashix is this an official request from Intel?

If so, let's have a discussion, please join the slack and message me and @kimwnasptd (the other lead) so we can discuss.

@thesuperzapper thesuperzapper added this to the v1.9.1 milestone May 24, 2024
@yshashix
Copy link
Author

@thesuperzapper , Intel colleagues who are working with Kubeflow will bring it soon. @tkatila
Thanks for adding in v1.9.1 milestone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Closed
Development

Successfully merging a pull request may close this issue.

2 participants