Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Testing a Condor Windows pool from a unix host
- Date: Thu, 29 Jan 2009 07:58:30 -0000
- From: "Kewley, J (John)" <john.kewley@xxxxxxxxxx>
- Subject: Re: [Condor-users] Testing a Condor Windows pool from a unix host
Note,
Even if you submit to a requirements with a named host,
it will not go there unless you also specify the Arch and OpSys
as Ian describes:
requirements = Arch == "INTEL" && OpSys == "WINNT52"
Make sure you specify that and you should be OK
JK
-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx on behalf of Ian D. Alderman
Sent: Thu 29/01/2009 04:53
To: Condor-Users Mail List
Subject: Re: [Condor-users] Testing a Condor Windows pool from a unix host
On Jan 28, 2009, at 10:34 PM, Matt Weatherford wrote:
>
> Hi,
>
> Ive got a condor server on Debian set up, and a bunch of Windows
> machines set up with the condor client. They are on different
> subnets,
> and im not sure I have all the firewalling set up right... so I want
> to
> do a test.
>
> What is a good way to submit a test job from this UNIX box that will
> be
> executed on the Windows machines?
Matt,
Take a look at this section of the Condor manual:
http://www.cs.wisc.edu/condor/manual/v7.2/2_5Submitting_Job.html#SECTION00356000000000000000
Try submitting a simple job with requirements set like this:
requirements = Arch == "INTEL" && OpSys == "WINNT52"
For example, suppose you had an windows executable called "foo.exe";
your submit file would look like this:
Universe = vanilla
Requirements = Arch == "INTEL" && OpSys == "WINNT52"
Executable = foo.exe
Log = foo.log
output = foo.out
error = foo.err
arguments = bar
notification = Never
should_transfer_files = IF_NEEDED
when_to_transfer_output = ON_EXIT
Queue 1
-Ian
>
> If I run condor_status on the unix (condor submit host & condor
> server,
> v705) I can see all the windows machines:
>
> condor:~# condor_status
>
> Name OpSys Arch State Activity LoadAv Mem
> ActvtyTime
>
> slot1@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+02:55:05
>
> ...
> ...
> ... omitted many many more similar lines
> ...
> ...
>
> slot7@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+10:55:30
> slot8@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+10:50:23
> slot1@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+04:55:11
> slot2@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+00:55:05
> slot3@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+04:55:13
> slot4@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+04:55:14
> slot5@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.020 2047
> 0+04:55:15
> slot6@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+04:55:16
> slot7@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+04:55:17
> slot8@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+04:55:10
> slot1@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 1+04:30:52
> slot2@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 1+04:30:52
> slot3@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 1+04:30:53
> slot4@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 1+04:30:55
> slot5@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+02:25:10
> slot6@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 1+04:30:57
> slot7@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 1+04:30:58
> slot8@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 1+04:30:51
> slot1@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+02:25:09
> slot2@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.050 2047
> 0+02:25:10
> slot3@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+01:55:06
> slot4@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+02:25:12
> slot5@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+02:25:13
> slot6@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+02:25:14
> slot7@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+02:25:15
> slot8@xxxxxxxxxxxx WINNT52 INTEL Unclaimed Idle 0.000 2047
> 0+02:25:08
>
> Total Owner Claimed Unclaimed Matched Preempting
> Backfill
>
> INTEL/WINNT52 120 0 0 120 0 0
> 0
>
> Total 120 0 0 120 0 0
> 0
>
>
> condor:~#
> condor:~# condor restart
>
> 1/28 20:36:46 Sent SIGTERM to COLLECTOR (pid 2057)
> 1/28 20:36:46 Sent SIGTERM to NEGOTIATOR (pid 2189)
> 1/28 20:36:46 Sent SIGTERM to SCHEDD (pid 2190)
> 1/28 20:36:46 The COLLECTOR (pid 2057) exited with status 0
> 1/28 20:36:47 The NEGOTIATOR (pid 2189) exited with status 0
> 1/28 20:36:47 The SCHEDD (pid 2190) exited with status 0
> 1/28 20:36:47 All daemons are gone. Restarting.
> 1/28 20:36:47 Restarting master right away.
> 1/28 20:36:47 Doing exec( "/usr/local/condor/sbin/condor_master" )
> 1/28 20:36:47 ******************************************************
> 1/28 20:36:47 ** condor_master (CONDOR_MASTER) STARTING UP
> 1/28 20:36:47 ** /usr/local/condor/sbin/condor_master
> 1/28 20:36:47 ** $CondorVersion: 7.0.5 Sep 20 2008 BuildID: 105846 $
> 1/28 20:36:47 ** $CondorPlatform: I386-LINUX_DEBIAN40 $
> 1/28 20:36:47 ** PID = 2022
> 1/28 20:36:47 ** Log last touched 1/28 20:36:47
> 1/28 20:36:47 ******************************************************
> 1/28 20:36:47 Using config source: /etc/condor/condor_config
> 1/28 20:36:47 Using local config sources:
> 1/28 20:36:47 /scratch/condor/condor_config.local
> 1/28 20:36:47 DaemonCore: Command Socket at <128.208.105.9:34537>
> 1/28 20:36:47 Started DaemonCore process
> "/usr/local/condor/sbin/condor_collector", pid and pgroup = 20381
> 1/28 20:36:50 Started DaemonCore process
> "/usr/local/condor/sbin/condor_negotiator", pid and pgroup = 20382
> 1/28 20:36:50 Started DaemonCore process
> "/usr/local/condor/sbin/condor_schedd", pid and pgroup = 20383
> condor:~#
> condor:~#
>
> Also, if I submit a job on this UNIX host, since this host is the
> condor
> master, and the submit host, but not a job-runner, will it sit in the
> queue forever? Since I only have windows condor job hosts?
>
> Thanks,
>
> Matt
>
>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx
> with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
--
===================================
Ian D. Alderman
office: 608.554.4605
cell: 608.217.9959
main: 888.292.5320
Cycle Computing, LLC
Leader in Condor Grid Solutions
Enterprise Condor Support and Management Tools
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/