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

Fix multi-user running #10

Open
LourensVeen opened this issue Oct 31, 2018 · 2 comments
Open

Fix multi-user running #10

LourensVeen opened this issue Oct 31, 2018 · 2 comments

Comments

@LourensVeen
Copy link
Member

The lie_md service should keep multiple Cerise dockers running, and keep track of which users owns which container, and route requests appropriately.

@felipeZ
Copy link
Contributor

felipeZ commented Nov 13, 2018

With the new async interface #13 Different containers can be handle (as long as different ports are requested). Containers are only shutdown if not jobs are running at all. This allows to have multiple containers and route the requests in a client-server interface using the unique metadata of a given job to properly handle the communication.

@LourensVeen
Copy link
Member Author

That sounds like it would work. If it helps, you can actually shut down a Cerise container while jobs are running. You just have to make sure to not delete it (a new container wouldn't know about existing jobs) and to start it up again before submitting more jobs, or requesting the status of runnning jobs (otherwise you'll get no response from the REST API, since the server behind it is not running).

A stopped Cerise container doesn't do any staging though, so keeping them running means that result downloads will start as soon as the results are available. That will probably make our users happy.

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