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

Create a setup for running client/server jobs #12

Open
orting opened this issue Apr 22, 2020 · 4 comments
Open

Create a setup for running client/server jobs #12

orting opened this issue Apr 22, 2020 · 4 comments

Comments

@orting
Copy link
Collaborator

orting commented Apr 22, 2020

We should have a standardized way of running for example jupyter notebooks that use the cluster as backend. This would also be nice for things like interactive segmentation tools that are being developed at DIKU.

First step is to have a documented way of doing this.Then it would be nice with some easy to use scripts.

@orting
Copy link
Collaborator Author

orting commented May 6, 2020

Abe is using a simple approach with communication over files. The server is just started with slurm and the client is run locally with communication over sshfs mounting the relevant directory from the cluster locally. See https://github.com/Abe404/root_painter

@Ulfgard
Copy link
Collaborator

Ulfgard commented May 6, 2020

shouldn't we just be able to start a notebook on the node and use an ssh-tunnel to the root?

so just normal port-forwarding.

the problem is of course to ensure that the tunnel is working and that ports are free etc.

@Ulfgard
Copy link
Collaborator

Ulfgard commented May 6, 2020

here is a wordy guide describing how someone else did this:

https://alexanderlabwhoi.github.io/post/2019-03-08_jpn-slurm/

@orting
Copy link
Collaborator Author

orting commented May 6, 2020

Jupyter is one thing, and is pretty straightforward, except that you cant have fixed ports. We should have a documented way of doing this.
The more general case, client/server architecture with server running on the cluster can be solved in different ways. The benefit of using the file approach is that yo dont need to fiddle with ports, you just need access to a shared directory. I think it is much easier for people to do this.

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

2 participants