-
Notifications
You must be signed in to change notification settings - Fork 149
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
Add accelerator table #1373
Comments
UX Needed (not a blocking UX request)the mocks still show that the accelerator table in the admin panel should have labels for Nvidia GPUs and HBUs. However i recall a conversation where we said that we dont want to hard code a relationships between accelerator and display label. What are your thoughts on this. Pic for ref |
@Gkrumbach07 Since we are planning to support toleration, it can be an opportunity to add the Group feature to allow the admin naming the labels as I proposed before: https://www.sketch.com/s/d8550d2f-fae4-44fd-82df-9f400563d459/a/L4bvgpy . |
There will be no hardcoding of anything in the UI now that we have Accelerator Profiles. Only hardcoded scenario is our migration script to move them into AcceleratorProfiles with Nvidia GPU. As for "supporting versions of cards" -- I think we still need to figure out some stuff. See my req comment where I ask @Xaenalt what our options here are. IMO though, groups in themselves can be part of this effort, we have the runway to do it right as we want it. I do imagine this is optional for the user though. |
@andrewballantyne @Gkrumbach07 Please help to review the design for Tolerations and Groups: https://www.sketch.com/s/d8550d2f-fae4-44fd-82df-9f400563d459/a/JAW7zxr |
@dpanshug Here is the latest design of the Accelerator profiles table fyi. |
Goal
Create a table to list available accelerator devices including the device indicator, display name, descriptions, enablement, and last modified date
Dependency issue
Itemized goals
Aspects continued elsewhere
Mocks
https://www.sketch.com/s/d8550d2f-fae4-44fd-82df-9f400563d459/a/P1R0eVL
The text was updated successfully, but these errors were encountered: