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

Integrate dsub #195

Open
wants to merge 32 commits into
base: master
Choose a base branch
from

Conversation

jhiemstrawisc
Copy link
Collaborator

Opening this PR in draft mode for now while @nisthapanda work through collaborating on documentation updates and other testing.

nisthapanda and others added 30 commits September 26, 2023 11:09
Merge Reed Comp Bio SPRAS master branch
…mporary fix to use dsub as framework with oi1, change to gcloud storage cp for larger file transfers
…dsub file paths are handled in container command
@agitter
Copy link
Collaborator

agitter commented Nov 22, 2024

Some additional context: we started using dsub for All of Us

Within the Researcher Workbench, the Google Cloud Life Sciences API is the executor of dsub tasks.

However

Cloud Life Sciences is deprecated and will no longer be available on Google Cloud after July 8, 2025.

It's not yet clear what All of Us will do to support migration. I would still like to proceed with merging in this code though, but we may be okay keeping documentation light if our use case is already deprecated.

See also #130.

As Tony pointed out in the PR review, Google Cloud Life Sciences is being
deprecated, so we're not sure how much longer this will be around. Instead
of going through and giving the `dsub` framework verbose documentation, we
explicitly state it's usage is experimental and warn the user that they
should already know what they're doing if they plan to use it.
This prints a warning for the user if they select the `dsub` framework. Since
we're unsure whether we'll need to support dsub in the future (as our primary
motivation for using it is being deprecated), this warning should prevent
potential users from getting their hopes up that we have long-term plans for it.
@jhiemstrawisc jhiemstrawisc marked this pull request as ready for review December 10, 2024 15:08
@jhiemstrawisc
Copy link
Collaborator Author

@agitter, I believe @nisthapanda tested this integration with GCLS and verified that the merge didn't break anything for her. Since we're not sure what the long-term plan is for dsub integration, I left minimal documentation in config/config.py that mentions it's experimental, along with a runtime warning to that effect.

Since this isn't breaking tests in either direction, I think it's ready for a proper review.

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

Successfully merging this pull request may close these issues.

3 participants