-
Notifications
You must be signed in to change notification settings - Fork 638
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
In Google Batch, support user specified boot images #5268
Conversation
✅ Deploy Preview for nextflow-docs-staging canceled.
|
The default boot image is batch-cos, but it may not be desired in all situations. In particular, there is an ongoing issue in which the batch-cos image does not retry pulling a docker image if there was a network issue. The user may also have some some other configuration pre-configured in their custom boot image. Signed-off-by: Siddhartha Bagaria <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this PR. It would be useful to add some unit tests to validate the changes
Signed-off-by: Siddhartha Bagaria <[email protected]>
Added a very basic unit test; tested with |
Signed-off-by: Paolo Di Tommaso <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all fine. thanks for this contribution
@siddharthab do you know if the boot image can be specified in an instance template? if so, we should add a warning that the boot image option you added will be overridden by the instance template if one is used: nextflow/plugins/nf-google/src/main/nextflow/cloud/google/batch/GoogleBatchTaskHandler.groovy Lines 299 to 318 in bf0cd32
|
You are right. I missed the warnings section. Will send another PR. |
… [ci fast] When both boot disk image and instance template are specified, the instance template gets priority, as with many other options covered by instance templates. Warn the user in this case. This was missed in #5268. Signed-off-by: Siddhartha Bagaria <[email protected]>
The default boot image is batch-cos, but it may not be desired in all situations. In particular, there is an ongoing issue in which the batch-cos image does not retry pulling a docker image if there was a network issue. The user may also have some some other configuration pre-configured in their custom boot image. This commit adds the ability to specify a custom boot disk image by using the configuration option ``` google.batch.bootDiskImage = '<NAME>' ``` Signed-off-by: Siddhartha Bagaria <[email protected]> Signed-off-by: Paolo Di Tommaso <[email protected]> Co-authored-by: Paolo Di Tommaso <[email protected]>
The default boot image is batch-cos, but it may not be desired in all
situations. In particular, there is an ongoing issue in which the
batch-cos image does not retry pulling a docker image if there was a
network issue. The user may also have some some other configuration
pre-configured in their custom boot image.
Signed-off-by: Siddhartha Bagaria [email protected]