-
Notifications
You must be signed in to change notification settings - Fork 662
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 accelerator optimized VMs in Google Cloud #5372
Comments
PRs are welcome, even if you can only get part of the way |
Also clean up some old logic for container options when using GPUs. These are now automatically handled by Google Cloud. Fixes nextflow-io#5372. Signed-off-by: Siddhartha Bagaria <[email protected]>
Hi @zihhuafang, what you are trying to do can be achieved by setting the machineType to be |
Hi @siddharthab, |
Hi @siddharthab,
So. it would also need the |
@zihhuafang the machine type can not have GPU specs like how you have specified them. You can first try to create the machine using the gcloud command line (in the web console, you can click on
So you have to specify the accelerator field separately. But I think this is not supported by Google Batch. You can try creating a job with these specs directly using the gcloud command like this:
And this will give the error:
Your best hope is to reach out to Google Cloud reps if you want this feature supported in Batch. |
New feature
Usage scenario
Google Cloud Batch has accelerator optimized VMs, that need to be configured a little differently. They don't need to specify the accelerator type and count, but would still need the
installGpuDrivers
set to true. See Google documentation.Suggest implementation
For this line, we also need to check if the task's machine type is
g2-*
,a2-*
ora3-*
even if accelerator type and count were not set. I think this should be enough. Happy to send a PR.The text was updated successfully, but these errors were encountered: