Channels
datahub-flyte
scipy-2023-workshop
flyte-school
flyte-build
flyte-users-berlin
scipy-2023-sprint
auth
flyte-bazel
large-language-models
contribute
great-content
in-flyte-conversations
flyte-on-gcp
show-and-tell
flyte-github
linkedin-flyte
random
deployment
feature-discussions
flytelab
flytekit-java
integrations
ray-on-flyte
conference-talks
release
flyte-ui-ux
workflow-building-ui-proj
writing-w-sfloris
jobs
hacktoberfest-2022
torch-elastic
flyte-console
engineeringlabs
helsing-flyte
flyte-documentation
konan-integration
databricks-integration
ray-integration
wg-gpu-types
flytekit
ecosystem-unionml
scipy-2022-sprint
announcements
ask-the-community
flyte-deployment
introductions
events
Powered by
#wg-gpu-types
y
Yee
06/27/2023, 7:12 PM
set the channel topic: Working group for custom GPU types
y
Yee
06/27/2023, 7:12 PM
set the channel description:
https://github.com/flyteorg/flyte/discussions/3796
y
Yee
06/27/2023, 7:13 PM
@Ketan (kumare3)
for naming suggestions - thinking about adding this field. okay?
https://github.com/flyteorg/flyteidl/pull/419/files#diff-8bd2613bf781125f77247c29a2f5502658c63cccf2b597a9ec3695ef1e7b2ca9R37
y
Yee
06/27/2023, 7:14 PM
background - the reason for adding an additional field rather than a custom resource enum, is that we are thinking the UX on the front-end will look something like
Copy code
@task def t(requests=Resources(gpu="1", gpu_type="A100")): ...
or something like that.
y
Yee
06/27/2023, 10:51 PM
cc
@Andrew Dye