Cluster: job to User identification
Hi, I am looking to add galaxy to our local cluster. One of the conditions of use is that I have to ensure that any job submitted to the cluster can be traced back to an individual user. What is the easiest means to achieve this? I assume that I have to force user logins (this can be done via the universe_wsgi.ini I think). However my local install running on a single machine does not appear to list user information in the paster.log file, just the ip address. Any help much appreciated. Alastair -- Alastair Kerr, Ph.D., Bioinformatician, Wellcome Trust Centre for Cell Biology, 2.21, Michael Swann Building, Kings buildings, The University of Edinburgh, Edinburgh, EH9 3JR, UK Tel: 44-(0)131-650-7527 http://bifx1.bio.ed.ac.uk/ The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
Hello Alastair, Alastair Kerr wrote:
Hi, I am looking to add galaxy to our local cluster. One of the conditions of use is that I have to ensure that any job submitted to the cluster can be traced back to an individual user. What is the easiest means to achieve this?
I assume that I have to force user logins (this can be done via the universe_wsgi.ini I think).
Yes, the config setting to force login in available in universe_wsgi.ini: # Force everyone to log in (disable anonymous access) require_login = True
However my local install running on a single machine does not appear to list user information in the paster.log file, just the ip address.
Every job is associated with a Galaxy Session via the job.galaxy_session mapper ( the job table includes a session_id column ), and every galaxy_session is associated with a user ( when forcing login ), via the galaxy_session.user mapper.
Any help much appreciated.
Alastair
Greg Von Kuster Galaxy Development Team
participants (2)
-
Alastair Kerr
-
Greg Von Kuster