Hi Gordon,
Does your plan involve having DRMAA handle the multiuser capability itself? I was under the impression that DRMAA cannot do it:
http://gridengine.sunsource.net/issues/show_bug.cgi?id=2507
I've likewise started coding this myself. We run LSF, but I'm hoping there won't be anything cluster-specific about it -- so far I'm just doing (e)uid/(e)gid switching plus plain DRMAA. It's not done yet, though -- jobs are submitted as the appropriate user but galaxy is losing track of them.
It would of course be even better if DRMAA did this itself, but I expect there will also be many changes to galaxy required, especially regarding dataset management where the actual files are owned by different cluster users.
Nate, do you think this will just be a few relatively minor tweaks to the galaxy code or a big project?
Thanks,
John
On Wed, 28 Jul 2010, Nate Coraor wrote:
Assaf Gordon wrote:
May I ask 'how soon' ? I'm working on a patch to allow SGE jobs to run under different users with DRMAA_Python. If you're going to change the runners framework, I'd better wait until you have the new DRMAA code ready.
It looks like it's committable now, so I'm writing the documentation for it first. Should be in this afternoon.
The code is very similar to the SGE code, so you may not have to change anything.
--nate
Thanks, -gordon _______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev
galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev