I am setting up a PoC for using OpenOnDemand in our cluster and one thing I noticed is that the basedirectory seems to be fixed, yes I can change it by setting OOD_DATAROOT in various env files but:
We use per research group/lab folders and some users may be part of multiple labs and need to run their jobs for the correct lab, how would I handle that scenario?
ie. Alice is part of labA and labB and thus needs to run different jobs under any of the following paths:
/sharedfs/labs/labA/alice
/sharedfs/labs/labB/alice
I read these threads but they don’t cover this usecase:
I kind of thought that this would be a common usage pattern and thus that this would be supported out of the box but I haven’t found any reference to this way of using things.
I don’t think you can achieve this today with the job composer. However, we are currently developing it’s replacement which will be able to solve this issue. The project manager - the replacement for the job composer - let’s you choose the directory to work out of. So alice will be able to create different projects in different directories and be able to work out of those project/directories directly without an administrators intervention.
There’s a beta version of it in 4.0, but it’s disabled by default because it is very much still in progress.