Yeah, PrivateData does not really help here. Would be useful to see in the future such PrivateData options like 'group' or 'account'.
Best regards, Taras On Tue, Nov 1, 2016 at 5:08 PM, Nathan Harper <[email protected]> wrote: > Unfortunately those don't give quite the level of control that I was > after. It's possible to make it so that a user can see nothing but their > own jobs, but not their jobs, their colleagues jobs (in the same account) > but no others. > > The only way to fudge it is to make every user with access to an account > also a coordinator of that account. > > > -- > *Nathan Harper* // IT Systems Lead > > *e: * [email protected] // *t: * 0117 906 1104 // *m: * 07875 > 510891 // *w: * www.cfms.org.uk <http://www.cfms.org.uk%22> // [image: > Linkedin grey icon scaled] > <http://uk.linkedin.com/pub/nathan-harper/21/696/b81> > CFMS Services Ltd // Bristol & Bath Science Park // Dirac Crescent // Emersons > Green // Bristol // BS16 7FR > > CFMS Services Ltd is registered in England and Wales No 05742022 - a > subsidiary of CFMS Ltd > CFMS Services Ltd registered office // Victoria House // 51 Victoria > Street // Bristol // BS1 6AD > > On 1 November 2016 at 13:52, Paul Edmon <[email protected]> wrote: > >> For slurmdbd you can set this: >> *PrivateData* This controls what type of information is hidden from >> regular users. By default, all information is visible to all users. User >> *SlurmUser*, *root*, and users with AdminLevel=Admin can always view all >> information. Multiple values may be specified with a comma separator. >> Acceptable values include: >> *accounts* prevents users from viewing any account definitions unless >> they are coordinators of them. *jobs* prevents users from viewing job >> records belonging to other users unless they are coordinators of the >> association running the job when using sacct. *reservations* restricts >> getting reservation information to users with operator status and above. >> *usage* prevents users from viewing usage of any other user. This applys >> to sreport. *users* prevents users from viewing information of any user >> other than themselves, this also makes it so users can only see >> associations they deal with. Coordinators can see associations of all users >> they are coordinator of, but can only see themselves when listing users >> >> http://slurm.schedmd.com/slurmdbd.conf.html >> >> For the slurm.conf you can do the same: >> *PrivateData* This controls what type of information is hidden from >> regular users. By default, all information is visible to all users. User >> *SlurmUser* and *root* can always view all information. Multiple values >> may be specified with a comma separator. Acceptable values include: >> *accounts* (NON-SlurmDBD ACCOUNTING ONLY) Prevents users from viewing >> any account definitions unless they are coordinators of them. *cloud* Powered >> down nodes in the cloud are visible. *jobs* Prevents users from viewing >> jobs or job steps belonging to other users. (NON-SlurmDBD ACCOUNTING ONLY) >> Prevents users from viewing job records belonging to other users unless >> they are coordinators of the association running the job when using sacct. >> *nodes* Prevents users from viewing node state information. *partitions* >> Prevents >> users from viewing partition state information. *reservations* Prevents >> regular users from viewing reservations which they can not use. *usage* >> Prevents >> users from viewing usage of any other user, this applies to sshare. >> (NON-SlurmDBD ACCOUNTING ONLY) Prevents users from viewing usage of any >> other user, this applies to sreport. *users* (NON-SlurmDBD ACCOUNTING >> ONLY) Prevents users from viewing information of any user other than >> themselves, this also makes it so users can only see associations they deal >> with. Coordinators can see associations of all users they are coordinator >> of, but can only see themselves when listing users. >> http://slurm.schedmd.com/slurm.conf.html >> That should do what you want. >> >> -Paul Edmon- >> >> >> On 11/01/2016 07:53 AM, Nathan Harper wrote: >> >> Hi, >> >> No solution, but a 'me too'. >> >> >> -- >> *Nathan Harper* // IT Systems Lead >> >> *e: * [email protected] // *t: * 0117 906 1104 // *m: * 07875 >> 510891 // *w: * www.cfms.org.uk <http://www.cfms.org.uk%22> // [image: >> Linkedin grey icon scaled] >> <http://uk.linkedin.com/pub/nathan-harper/21/696/b81> >> CFMS Services Ltd // Bristol & Bath Science Park // Dirac Crescent // >> Emersons >> Green // Bristol // BS16 7FR >> >> CFMS Services Ltd is registered in England and Wales No 05742022 - a >> subsidiary of CFMS Ltd >> CFMS Services Ltd registered office // Victoria House // 51 Victoria >> Street // Bristol // BS1 6AD >> >> On 1 November 2016 at 11:49, Taras Shapovalov < >> [email protected]> wrote: >> >>> Hey guys, >>> >>> Could you tell me how I can configure slurm that users will only be able >>> to see the jobs submitted by members of their own user group? Similar >>> restriction by partition or by account is also would work for me. I cannot >>> find a solution anywhere. >>> >>> Best regards, >>> >>> Taras >>> >>> >>> >> >> >
