[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] feasable policy?


> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx 
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Andy Roosen
> Sent: Thursday, 11 May 2006 10:11 a.m.
> To: condor-users@xxxxxxxxxxx
> Subject: [Condor-users] feasable policy?
> I'm trying to work out if the following set of policy requirements can
> be met using Condor 6.6. 
> We have a bunch of machines that are dedicated to doing computation.
> Some of the machines "GM" have been bought by a group "G". An 
> ideal policy
> would be the following:
> Jobs submitted by people in G:
> 	1) Prefer to run on machines in GM if available.
> 	2) otherwise, if any machine is available, run it there
> 	3) otherwise, preempt a job running on GM owned by 
> someone not in G
> Jobs submitted by people not in G:
> 	4) If a machine not in GM is available, run there
> 	5) otherwise, run on GM
> I believe I know how to implement 1,2,4,5. I'm having trouble 
> with 3; I
> get the impression that it involves PREEMPTION_REQUIREMENTS, but can't
> see how that can be used to distinguish between machines. 
May I recommend you have a read about the Bologna Batch System
(http://www.cs.wisc.edu/~pfc/bologna_batch_system.html).  I'm not sure
it will do what you need AS-IS but it might give you some ideas as to
how to proceed.

Attention: The information contained in this message and/or attachments
from AgResearch Limited is intended only for the persons or entities
to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipients is prohibited by AgResearch
Limited. If you have received this message in error, please notify the
sender immediately.