You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: