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

Use Galaxy Pulsar for all jobs regardless of destination #4

Open
innovate-invent opened this issue Nov 12, 2020 · 2 comments
Open

Use Galaxy Pulsar for all jobs regardless of destination #4

innovate-invent opened this issue Nov 12, 2020 · 2 comments

Comments

@innovate-invent
Copy link
Collaborator

Example for k8s: galaxyproject/pulsar@f892f71

@innovate-invent
Copy link
Collaborator Author

innovate-invent commented May 19, 2021

It may be better to replace pulsar with two scripts added to the galaxy repository.
The scripts would provide CLI access to the logic within galaxy that stages, prepares, and cleans up galaxy jobs.
This can then be used to schedule jobs where there is no required filesystem.
Pulsar has already done much of this work and the logic largely needs to be just ripped out of it.

The k8s runner can then be rewritten to use a job spec template, and that template can specify init containers that execute these scripts. See #8

The scripts should be able to operate with and without direct access to the Galaxy backend database.

@innovate-invent
Copy link
Collaborator Author

See #19

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

1 participant