-
Notifications
You must be signed in to change notification settings - Fork 0
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
Slurm scheduler #16
Slurm scheduler #16
Conversation
Just a heads up that I successfully managed to execute the instructions in the top post. I'm still trying to grasp more fully how this works, but that also requires looking at #15. |
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.
Tested and pair-reviewed!
def close(self) -> None: | ||
"""Close SSH connection.""" | ||
if self.conn: | ||
self.conn.close() |
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.
Now, once open it stays open. Would it make sense to close the connection after each transfer?
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.
Postponed to #35
Co-authored-by: Peter Kalverla <peter@kalversweep.nl>
Co-authored-by: Peter Kalverla <peter@kalversweep.nl>
Adds Slurm scheduler support.
Also adds
To test spin up a Slurm container with
To submit a job in a Python REPL (
python -m asyncio
oripython
)After download should have stderr.txt, stdout.txt, returncode files in /tmp/jobs/myjob.
As similar job submission is done at https://github.com/i-VRESSE/bartender/blob/slurm-scheduler/bartender/tests/schedulers/test_slurm.py#L60
Don't forget to
docker rm -f <slurm container name or id>
when you are done.