Community
Participate
Working Groups
It should be possible to submit one interactive job to the PBS queue and one should then be able to launch several parallel applications as long as the interactive job is running. Reason: Often when debugging or testing, it is required to run the application several times right after one another. Having to wait on the queue for each launch is very inconvenient and time consuming, and thus usually the interactive queue is used when doing the debugging/testing outside of Eclipse/PTP. Thus we should add the possibility to: - Launch an interactive job on n nodes for m minutes - Show the remaining time and the available nodes somewhere in the runtime perspective - As long as the interactive job is running it should be possible to launch a parallel application. One should be able to specify on how many CPUs - It should be possible to terminate the interactive job before the time is over. For the runtime perspective it might be best visualized by having either a temporary RM or a temporary machine under the normal PBS RM to show the nodes and jobs which run within the interactive job.
Roland, You mentioned that Mayur would like to work on this. Most of this seems to be proxy-end, but there will need to be some option expressed on the UI side. Shall I take care of that small part? Let me know what you think that should look like. Al
(In reply to comment #1) > You mentioned that Mayur would like to work on this. Most of this seems to be > proxy-end, but there will need to be some option expressed on the UI side. > Shall I take care of that small part? Let me know what you think that should > look like. I advised Mayur to first work on some of the other issues because this one might be a little bit tricky as a 2nd issue to work on. Also we haven't decided yet whether we want to create a temporary machine or a temporary RM (or some 3rd option) for the time the interactive job is running. Also we could may be use the OpenMPI/Mpich RM as an RM running within the interactive job. Thus I think as a first step we do some thinking to find the best approaches before we start implementing one of the options. Please go ahead and write whether you see further possible options and what you see as advantages/disadvantages of the options.
Sounds good to me. I think that forking a separate process to handle -I submissions is a good idea. Re-using the MPI RMs also sounds like a good idea on the face of it. If anything else occurs to me in this regard I'll post it.
If interactive job support is added, then it would be nice to add debug support as well.
Now part of the JAXB framework.
This is included in 5.0.
