[Condor-users] Better control over negotiator?

[Steffen Grunewald <steffen.grunewald@xxxxxxxxxx>]

Hi,

I've got a bunch of (theoretically) identical machines (dual core ones), 
and have set aside a few of them which only advertise a single slot, to
allow for bigger jobs.
I have also defined

NEGOTIATOR_PRE_JOB_RANK = ( -1 * TARGET.Memory )

to discourage usage of these machines by "small" jobs.
Unfortunately, there seems to be another ranking in effect which is based
on other characteristics (for historical reasons, some users still have
a RANK=MIPS in their submit files). Sometimes, when the pool is almost
idle, the "big" slots are taken nevertheless. (seen with 6.9.5, confirmed
with 7.0.0)

I can also see (now, with 7.0.0) that slots are matched in pairs: if one
slot of the dual-slot machines is taken, the other one would be, too.
I suppose this is due to the rank value being identical for slots on the
same machine?

Is there a (simple but consistent) way to handle the small slots the same,
(by rounding MIPS and KFLOPS values ? 
while reserving the big ones for big jobs as long as possible?

Is it possible, in an almost idle pool, to claim slots "in alphabetical 
order"?

Is there a way to read out the actual value of NEGOTIATOR_PRE_JOB_RANK
from an individual slot?

Cheers,
 Steffen

-- 
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html