[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Condor-users] Temporary disable a virtual machine
- Date: Tue, 20 May 2008 10:51:58 +0800
- From: "Tung-Han Hsieh" <tunghan.hsieh@xxxxxxxxx>
- Subject: [Condor-users] Temporary disable a virtual machine
Hello,
I am running condor-6.7 on several SMP machines. Each CPU of each
node is equally treated as a virtual machine. For example, when I run
condor_status
it shows
vm1@w28 LINUX X86_64 Claimed Busy 0.000 4014 0+14:31:51
vm2@w28 LINUX X86_64 Claimed Busy 0.000 4014 0+14:31:52
vm3@w28 LINUX X86_64 Claimed Busy 0.000 4014 0+14:31:53
vm4@w28 LINUX X86_64 Claimed Busy 4.000 4014 0+14:31:54
vm1@w29 LINUX X86_64 Claimed Busy 1.000 4014 0+17:20:11
vm2@w29 LINUX X86_64 Claimed Busy 1.000 4014 6+19:27:31
vm3@w29 LINUX X86_64 Claimed Busy 0.000 4014 4+17:26:16
vm4@w29 LINUX X86_64 Unclaimed Idle 1.000 4014 0+00:05:08
Now if I have to temporary disable the idling virtual machine, vm4@w29,
such that the newly submitted job will not go into it, and without affecting
the running jobs in the other virtual machines of the node w29. How can
I do that ?
Thanks very much for your suggestions in advance. :)
T.H.Hsieh