Hi Marcin, Could you describe the use case for preventing access when the lustre license isn't specified? That might help me offer a better solution.
Off the top of my head I could see using prolog/epilog scripts to mount and unmount lustre as required however this only works if your nodes are job-exclusive (one job per node). Another option would be to use a chroot environment for each job and only bind-mount required filesystems. This approach has a lot of overhead, though and I'm not entirely sure of the implementation details. You could also try the cgroup namespace subsystem. I did some reading this morning and can't find documentation for this but I had some vague recollection that you could control which filesystems are accessible to each namespace. Sent from my iPhone On Dec 16, 2012, at 10:12 AM, Marcin Stolarek <[email protected]> wrote: > Hi all, > > I'm thinking about describing lustre as a licence in our slurm installation. > Do you know any possibility of preventing job from writing on/reading from a > specified file system if user haven't specified appropriate licence string? > > thanks, > marcin
