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

Enhancing dsub for Google Batch with Additional Configuration Options #286

Closed
amircs opened this issue Mar 22, 2024 · 2 comments
Closed

Comments

@amircs
Copy link

amircs commented Mar 22, 2024

Hello dsub maintainers and community,

I've been working with dsub to launch tasks on Google Batch and it's been a great experience overall. However, I encountered a scenario where I needed to specify additional VM configuration options that are crucial for my workflows, such as --machine-type, --boot-disk-size, and --disk-size. Specifically, I was looking to use configurations like:
--machine-type n1-standard-4
--boot-disk-size 100
--disk-size 400

From my current understanding and attempts, it seems these parameters might not be passed to Google Batch through dsub. Example command for reference:

dsub \ --provider google-batch \ --project PROJECT_ID \ --logging gs://BUCKET_NAME/WORK_DIRECTORY/logs \ --input BAM=gs://genomics-public-data/1000-genomes/bam/HG00114.mapped.ILLUMINA.bwa.GBR.low_coverage.20120522.bam \ --output BAI=gs://BUCKET_NAME/WORK_DIRECTORY/HG00114.mapped.ILLUMINA.bwa.GBR.low_coverage.20120522.bam.bai \ --image quay.io/cancercollaboratory/dockstore-tool-samtools-index \ --command 'samtools index ${BAM} ${BAI}' \ --machine-type n1-standard-4 \ --boot-disk-size 100 \ --disk-size 400 --wait
I'm reaching out to ask if there's a way to include these VM configuration options for tasks submitted to Google Batch, or if there might be a workaround I haven't discovered. Additionally, if this functionality is not currently supported, could it be considered for future updates? I believe it would enhance the flexibility and usability of dsub for a variety of use cases.

I understand there might be complexities I'm not fully aware of, so I'm completely open to learning more about the technical considerations or alternative approaches recommended by the community and the developers.

Thank you for your continuous efforts in developing and maintaining dsub. Looking forward to your thoughts and suggestions.

@wnojopra
Copy link
Contributor

wnojopra commented May 6, 2024

Hi @amircs :

We just put out release 0.4.11, which includes:

  • Extend batch support for network, subnetwork, private IP, accelerator, min cpu, min ram, boot disk, and machine type.

When you get the chance, can you verify if it resolves your issues?

@amircs
Copy link
Author

amircs commented May 6, 2024

Awesome! Thanks so much for your help and support!

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

No branches or pull requests

2 participants