Re: [Condor-users] Help Confuse : Condor-G and Globus Job Type

[Jan Ploski <Jan.Ploski@xxxxxxxx>]

condor-users-bounces@xxxxxxxxxxx schrieb am 05/08/2008 05:27:43 AM:

> I Read from globus manual that job type that accepted by globus job
> manager are single|multiple|mpi|condor. But i didn't get a lot of
> information about those jobs in the manual.

single - allocate a single slot on a single cluster node, run the job 
executable there
multiple - allocate n slots, possibly on multiple cluster nodes, run an 
instance of the job executable in each slot
mpi - like multiple, but the job executable is started with mpirun/mpiexec 
rather than directly
condor - (I don't know, haven't used it myself)

> I Found information at
> http://bugzilla.globus.org/globus/show_bug.cgi?id=3384
> that those job's are treated differently in Local Scheduler ( like
> Condor,SGE,PBS,or LSF).
> 
> and it make me confused about several things :
> 
> 1. is Condor really support single and multiple job ? and what is the
> different between them in Condor.

I don't know whether the Condor adapter (aka "job manager") on the Globus 
(server) side implements these job types correctly. The best way to find 
out would be probably to inspect and debug the Perl module implementing 
this adapter, installed in 
$GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/condor.pm.

I suspect that the Condor adapter is not maintained as well as the PBS 
adapter and may have some limitations.

> 2. How can i submit condor job (vanilla,java,mpi,parallel) via Condor-G
> because i have Condor as Local Scheduler under Globus. Is that supported
> by Condor-G ?

Basically, Condor-G acts as a WS-GRAM client and submits an XML document 
with the Globus job description. This XML document is interpreted on the 
Globus side by a "job manager", which is an adapter implemented in Perl, 
responsible for submitting the local job to the local scheduler and 
monitoring its progress afterwards. On the Condor-G side, you can specify 
an arbitrary fragment of XML to be appended to the XML job description 
(see below). It could be that the Condor job manager interprets some such 
extensions to map to Condor job types. The answer is in the condor.pm file 
where you can see how the local Condor job description is pieced together.

> 3. when i try to submit with job type mpi like following submission file 
:

> 
##########################################################################
> executable= test2
> universe=grid
> globusrsl= (jobtype=mpi)(count=4)

I'm not sure whether the globusrsl attribute is supported for GT4 hosts. 
You should use the globus_xml attribute, for example:
globus_xml = <count>4</count><jobType>mpi</jobType>

I've written up some explanations at 
https://bi.offis.de/wisent/tiki-index.php?page_ref_id=96

Also, you might wish to test things out without MyProxy first. If you 
don't have the newest version of Condor-G, you will likely run into 
trouble with MyProxy (there were bugs, and some minor bugs are still 
remaining - specifically, condor_preen erroneously removing the password 
files).

Regards,
Jan Ploski