[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] vm1 info in vm2 ClassAd?
- Date: Mon, 31 Aug 2009 15:22:22 -0400
- From: Ian Chesal <ICHESAL@xxxxxxxxxx>
- Subject: Re: [Condor-users] vm1 info in vm2 ClassAd?
> I am working on a cluster made up of many SMP machines.
> For a given node which contains multiple virtual machines,
> is it possible to include in the status ("claimed" or "unclaimed")
> of vm1 in the ClassAd of vm2, and vice versa?
> Basically I want to be able to decide if my job gets submitted to
> vmX based on whether or not vmY is claimed or unclaimed.
> # condor_version
> $CondorVersion: 6.8.4 Feb 1 2007 $
> $CondorPlatform: X86_64-LINUX_RHEL3 $
And for an example of how to use this:
# Advertise slot 1 as an "isolated" slot, meaning that when a
# "sensitive" job runs on it, the other slots of the machine will
# be emptied to provide an isolated execution environment for
# the timing-sensitive job.
vm1_AlteraIsIsolatedJobSlot = TRUE
STARTD_EXPRS = $(STARTD_EXPRS), AlteraIsIsolatedJobSlot
# If slot 1 is running a sensitive job, it should advertise a
# special classad. This classad will be referred to in the config below.
STARTD_JOB_EXPRS = $(STARTD_JOB_EXPRS), AlteraJobAttributeIsSensitive
STARTD_VM_EXPRS = $(STARTD_VM_EXPRS), AlteraJobAttributeIsSensitive
# To reduce inefficiency due to preemption, we always prefer sensitive
# jobs so that they don't get preempted after killing all non-sensitive
# jobs running on this machine.
# Note that sensitive jobs still compete for resources using the normal
# group/priority/fifo scheme among themselves.
ALTERA_GODLIKE_RANK = 1000
RANK = ( \
(((TARGET.AlteraJobAttributeIsSensitive =?= TRUE) ||
("godlike" =?= TARGET.AlteraGroup)) * $(ALTERA_GODLIKE_RANK)) + \
((("$(AlteraPreferredGroup1)" != "") &&
("$(AlteraPreferredGroup1)" =?= TARGET.AlteraGroup)) *
$(AlteraPreferredGroupRank1)) + \
((("$(AlteraPreferredGroup2)" != "") &&
("$(AlteraPreferredGroup2)" =?= TARGET.AlteraGroup)) *
$(AlteraPreferredGroupRank2)) + \
((("$(AlteraPreferredGroup3)" != "") &&
("$(AlteraPreferredGroup3)" =?= TARGET.AlteraGroup)) *
$(AlteraPreferredGroupRank3)) + \
((("$(AlteraPreferredGroup4)" != "") &&
("$(AlteraPreferredGroup4)" =?= TARGET.AlteraGroup)) *
$(AlteraPreferredGroupRank4)) + \
((("$(AlteraPreferredGroup5)" != "") &&
("$(AlteraPreferredGroup5)" =?= TARGET.AlteraGroup)) *
$(AlteraPreferredGroupRank5)) + \
((("$(AlteraPreferredGroup6)" != "") &&
("$(AlteraPreferredGroup6)" =?= TARGET.AlteraGroup)) *
# Make sure that slot 1 can execute any jobs, and other slots can only
# a job if slot one is unclaimed or is not running a sensitive job
START = \
($(START)) && \
(VirtualMachineID == 1) || \
VirtualMachineID != 1 && \
vm1_State =?= "Unclaimed" || \
vm1_AlteraJobAttributeIsSensitive =?= UNDEFINED || \
vm1_AlteraJobAttributeIsSensitive =?= FALSE \
# If a sensitive job is running in slot 1, jobs in other slots are
ALTERA_NON_SENSITIVE_SLOT_PREEMPTED_BY_SENSITIVE_JOB = \
VirtualMachineID != 1 && \
vm1_State =!= "Unclaimed" && \
vm1_AlteraJobAttributeIsSensitive =!= UNDEFINED && \
vm1_AlteraJobAttributeIsSensitive =?= TRUE \
PREEMPT = (($(PREEMPT)) ||
MaxJobRetirementTime = (($(MaxJobRetirementTime)) *
($(ALTERA_NON_SENSITIVE_SLOT_PREEMPTED_BY_SENSITIVE_JOB) =?= FALSE))
This config sets slot 1 to be a "sensitive" slot so any job that wants
to take over an entire machines targets slot 1 and preempts any other
jobs in the other slots when it starts to run. It also ensures that no
other jobs run in the other slots as long as there's a "sensitive" job
running in slot 1.
Presumably the need for crazy stuff like this should be reduced to zero
as dynamic partitioning of SMP machines ramps up. It's in 7.2.x but I
haven't had a chance to check it out yet.
This message may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution, or copying of this message, or any attachments, is strictly prohibited. If you have received this message in error, please advise the sender by reply e-mail, and delete the message and any attachments. Thank you.