-
Notifications
You must be signed in to change notification settings - Fork 661
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
Adding support for Sarus container engine #3470
Adding support for Sarus container engine #3470
Conversation
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
test fixes to SarusBuilder.groovy and SarusBuilderTest.groovy one more test fix in SarusBuilderTest.groovy tiny test fix in SarusBuilderTest.groovy adding engineOptions to SarusBuilder.groovy Revert "adding engineOptions to SarusBuilder.groovy" This reverts commit 77f1294. more test fixes in SarusBuilderTest.groovy more test fixes in SarusBuilder and SarusBuilderTest more SarusBuilderTest Revert "more SarusBuilderTest" This reverts commit 88f50c1. one more fix to SarusBuilderTest one moooooooore fix to SarusBuilderTest yet another fix to SarusBuilderTest Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Alexander Toenges <21218078+ATpoint@users.noreply.github.com> Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com> Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
1. Adds the projectId to BatchLogging's LoggingOptions so the logs will be fetched from the correct project. Previously I got a lot of "that resource might not exist" responses from the log read requests. I'm not sure if there's something special about my environment that causes me to need the projectId in the options, but I think it couldn't hurt to have the projectId in general. 2. Removes the old parseOutput function, which relied on the STDERR and STDOUT prefixes in the payload of the log entries. Batch no longer adds prefixes so that parsing doesn't work. Now we can distinguish stderr from stdout by looking at the logEntry's severity. 3. Catches any exception thrown by the log reading code. It could be a permissions issue like I was seeing, or a thread pool issuee as in nextflow-io#3166. Either way, something going wrong while trying to read task logs should probably not stop the whole workflow. With these changes, the nf-core/methylseq workflow can be run with the google-batch executor. Signed-off-by: Aaron Golden <aegolden@google.com> Signed-off-by: Aaron Golden <aegolden@google.com> Co-authored-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com> Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Quoting will allow special characters, in particular ":", to be parsed. This should prevent the unparseable filter exception in nextflow-io#3353. Signed-off-by: Aaron Golden <aegolden@google.com> Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com> Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
… [ci skip] Signed-off-by: Nathan Thorpe <nathan@techstormpc.com> Co-authored-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com> Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com> Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com> Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com> Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
10a65e6
to
722fea2
Compare
note: the commit list looks a bit weird to me, compared to PRs I usually open. |
modules/nextflow/src/main/groovy/nextflow/container/SarusBuilder.groovy
Outdated
Show resolved
Hide resolved
modules/nextflow/src/main/groovy/nextflow/executor/BashWrapperBuilder.groovy
Outdated
Show resolved
Hide resolved
Can Sarun pull the image on-the-fly as it can be done with |
Unfortunately, at the moment automatic pull is not support in Sarus (see eth-cscs/sarus#6) |
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
a5e1028
to
06cfa2b
Compare
Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
If the automatic pull then this mention in the docs looks inconsistent to me or am I wrong? |
Hi @marcodelapierre @pditommaso, thanks for your interest in Sarus and for this development! One of the motivations for not including an automatic image pull in Since Sarus 1.5.0, |
Hi @Madeeks thanks for the heads up! this is indeed very interesting. I think adding the pull before the runs would make the experience more consistent with the expectation of nextflow users. What do you think @marcodelapierre? |
Thanks @Madeeks and @pditommaso for your feedback! :-) Indeed, I am already pre-pulling images to be consistent with the Nextflow user experience: https://github.com/marcodelapierre/nextflow/blob/add/sarus_containers/modules/nextflow/src/main/groovy/nextflow/container/SarusBuilder.groovy#L84-L92 |
Signed-off-by: Marco De La Pierre <marco.delapierre@gmail.com>
Hi @pditommaso @evanfloden ,
I hope this feature can be useful for part of the community.
Sarus is a container engine developed and in use at CSCS in Switzerland, see https://sarus.readthedocs.io.
I have successfully run
make test
locally with this branch.I have also successfully tested the branch in action with the
nextflow-io/hello
workflow (both plain workflow, and some modifications, to test all options for the new feature).@Madeeks , @lichinka ,
pinging you, so that you are aware of this new interface to Sarus being proposed for the Nextflow workflow engine, and also in case you have any feedback for this PR.