Configure Galaxy to be able to access the secondary HTCondor cluster #981
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a runner and TPV destinations for the secondary HTCondor cluster. Sending jobs to the secondary cluster is controlled via the
condor-secondary
TPV scheduling tag.TPV destinations are automatically duplicated by Jinja. It creates extra destinations whose name is prefixed with
secondary_
, makes them inherit from the original destination, replaces the runner, and makes them require thecondor-secondary
scheduling tag.job_conf.yml.j2
was also modified so that concurrency limits affecting condor destinations also get cloned.This commit also lets the Galaxy user invoke the appropriate
condor_*
commands usingsystemd-run
.