Dear all, I know Galaxy is independent of the underlying queuing system but is it possible to display the status of the queue to users via the Galaxy interface? I understand that the jobs are submitted under the name of the owner of the Galaxy process. And that there is a way to fix this [1], but I think I'm fine with leaving it as-is. I guess it would be nice if users can see how long the queue is. The naive way that I'm thinking about is to have a cronjob that runs "squeue" (we are using SLURM) periodically. Its output is cleaned up by a script and a "static" HTML file is generated for Galaxy to display. I don't know if there is a more sensible way that fits within the framework of Galaxy. Is this approach acceptable or is there a better / easier way that I've completely missed? Thank you! Ray [1] https://wiki.galaxyproject.org/Admin/Config/Performance/Cluster#Submitting_J...
Hi Ray Are you running the reports tool? https://wiki.galaxyproject.org/Admin/UsageReports you can inform your user about this page, and then, they can check the "All unfinished jobs" page. This is probably the easiest way - though you need to consider, that all users can see each other jobs (i.e the executed command line) on that extra web site Regards, Hans-Rudolf On 04/15/2016 09:22 AM, Raymond Wan wrote:
Dear all,
I know Galaxy is independent of the underlying queuing system but is it possible to display the status of the queue to users via the Galaxy interface?
I understand that the jobs are submitted under the name of the owner of the Galaxy process. And that there is a way to fix this [1], but I think I'm fine with leaving it as-is. I guess it would be nice if users can see how long the queue is.
The naive way that I'm thinking about is to have a cronjob that runs "squeue" (we are using SLURM) periodically. Its output is cleaned up by a script and a "static" HTML file is generated for Galaxy to display.
I don't know if there is a more sensible way that fits within the framework of Galaxy. Is this approach acceptable or is there a better / easier way that I've completely missed?
Thank you!
Ray
[1] https://wiki.galaxyproject.org/Admin/Config/Performance/Cluster#Submitting_J... ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Hi Hans-Rudolf, Thanks a lot for your reply! No, I wasn't aware of the reporting tool; thanks a lot for telling me about it! I did find "reports_wsgi.ini.sample". Actually, it isn't exactly what I want. I would like users to have an idea how long the queue is, but I don't think I'd like them to know who the other users are and what they are running. Perhaps because it's all work-related, maybe there is no harm, but I guess I need to think about it (and discuss with management). I'll set it up and see if it fits our needs -- thanks a lot for your help! Ray On Fri, Apr 15, 2016 at 4:42 PM, Hans-Rudolf Hotz <hrh@fmi.ch> wrote:
Hi Ray
Are you running the reports tool?
https://wiki.galaxyproject.org/Admin/UsageReports
you can inform your user about this page, and then, they can check the "All unfinished jobs" page.
This is probably the easiest way - though you need to consider, that all users can see each other jobs (i.e the executed command line) on that extra web site
Regards, Hans-Rudolf
On 04/15/2016 09:22 AM, Raymond Wan wrote:
Dear all,
I know Galaxy is independent of the underlying queuing system but is it possible to display the status of the queue to users via the Galaxy interface?
I understand that the jobs are submitted under the name of the owner of the Galaxy process. And that there is a way to fix this [1], but I think I'm fine with leaving it as-is. I guess it would be nice if users can see how long the queue is.
The naive way that I'm thinking about is to have a cronjob that runs "squeue" (we are using SLURM) periodically. Its output is cleaned up by a script and a "static" HTML file is generated for Galaxy to display.
I don't know if there is a more sensible way that fits within the framework of Galaxy. Is this approach acceptable or is there a better / easier way that I've completely missed?
Thank you!
Ray
[1] https://wiki.galaxyproject.org/Admin/Config/Performance/Cluster#Submitting_J... ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
participants (2)
-
Hans-Rudolf Hotz -
Raymond Wan