-
Notifications
You must be signed in to change notification settings - Fork 1
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
Behavior of preempted jobs? #5
Comments
Hi James, you are referring to a very old presentation and in such slides we shown |
Is there a name for that project? I am highly interested in this scheduler (or something like it). I would be happy to contribute to this effort if it has begun work. Or, should we make contributions to this repository? Thanks, |
Thanks for the update! This is a critical feature for us and I can spare programmers to help get it up and running. How can I contribute to this effort? |
Hi Edwin, thanks a lot for your interest on our work. Thanks a lot. |
Hi James, we are planing to open a position for developers and if you or someone |
Hi, I stumbled upon this repository while searching for queuing solutions in Openstack. In the presentation found here, https://agenda.infn.it/getFile.py/access?contribId=17&sessionId=3&resId=0&materialId=slides&confId=7915, it says that when resources aren't available, older instances are terminated to make room for new instances.
Where in the code does this termination occur? Is it possible to suspend the instance and add it back into the queue for later processing?
The text was updated successfully, but these errors were encountered: