[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Unix group membeship & condor pool selection?
- Date: Fri, 26 Aug 2005 10:25:08 -0700
- From: Lee Damon <nomad@xxxxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Unix group membeship & condor pool selection?
I was thinking about doing that but realized that the users here are the
type who would very quickly figure out they could run on other hosts if
they bypass the wrapper... and the type that would find a way to bypass
it no matter what I do.
Can I create multiple Condor pools on one Condor master? Maybe that way
I can at lest limit jobs to run on the same pool the submit host is in.
Jaime Frey wrote:
On Aug 25, 2005, at 12:46 PM, Lee Damon wrote:
I am in the process of setting up condor for multiple labs in the same
I would like to set it up so people in Unix group "acme" run their
jobs on the "acme" pool, people in "cad" run on the "cad" pool, etc.
I would like to do this with one master so that people in both 'acme'
and 'cad' can run in both pools.
Before I bash my brains against the documentation I would like to know:
Is this is even possible?
I don't believe there's a way to have Condor directly consider unix
groups for scheduling. What you can do is wrap condor_submit with a
script that determines what groups the user is in and adds
corresponding attributes to the job ad. The syntax to condor_submit
would work like this:
condor_submit -a '+InAcme=True' -a '+InCad=False' "$@"
Then, the startds can be configured to require one of these attributes
to be true in ads of jobs they will run.