[Moabusers] Limiting access to a class by GID

[Michael Santos]

Hi Jenett,

	Notionally, in moab I think you could try something like

CLASSCFG[queue1] MAXJOB[GROUP:group2]=0
CLASSCFG[queue2] MAXJOB[GROUP:group1]=0

in moab.cfg, to keep group2 from running on queue1 and group1 from  
running on queue2.  This sort of policy is documented in Moab Admin's  
Guide Section 6.2.1.2.

	I have not actually tried this out, so I don't know if it will  
work.  However, the manual gives an example (in that section) of a  
CLASSCFG[] MAXJOB[GROUP] policy, which is an encouraging sign.

	For the resource manager Torque, I think it is quite straightforward  
to implement this policy (see Torque v2.0 Admin Manual Section 4.1).   
I don't know if LoadLeveler has similar options.

	Good luck!

Best regards,
Michael Santos
Space Telescope Science Institute

On Jul 30, 2007, at 5:38 PM, Jenett Tillotson wrote:

>
> I was wondering if there was anyway to limit access to a class by  
> GID.  We have the need to segregate our cluster into two user  
> groups each with their own set of queues.  I would like to be able  
> to use moab (or the resource manager LoadLeveler) to limit access  
> to each queue dependent on unix group membership.  This could  
> potentially be a large-ish number of users (around 300) so using a  
> unix group would be preferable.
>
> Is anyone doing something like this?  Does anyone have any  
> suggestions?  I have poured over the manual looking for anything  
> that says "group", but I don't see where it is documented.
>
> Thanks in advance,
>
> Jenett Tillotson
> System Administrator
> Indiana University
>
> _______________________________________________
> moabusers mailing list
> moabusers at supercluster.org
> http://www.supercluster.org/mailman/listinfo/moabusers