Re: [Condor-users] Using Condor-C grid universe

[Matthew Farrellee <matt@xxxxxxxxxx>]

There's no catalog.

http://condor-git.cs.wisc.edu/?p=condor.git;a=blob;f=src/src/condor_submit.V6/submit.cpp;h=74131b54c7d62f131692625ea765d6510d166b71;hb=HEAD

This file has a list of the condor_submit commands at the top, searching for condor_param will find uses and alternatives. Aalmost all commands, e.g. executable, can show up in a submit file as either the command or the attribute, e.g. executable or cmd.

Of course in submit.cpp the alternatives (the actual job ad attr) show up as ATTR_BLAH, which needs to be looked up in,

http://condor-git.cs.wisc.edu/?p=condor.git;a=blob;f=src/src/condor_c%2B%2B_util/condor_attributes.cpp;h=cf9edd1d57fcdb791089c42be4a425a724a735a2;hb=HEAD

There's no hard and fast rule for mapping command to attribute, e.g. executable -> cmd. And some commands change condor-submit behavior and have no attribute mapping at all.

Best,


matt

https://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=557

On 05/19/2010 01:56 AM, Greg.Hitchen@xxxxxxxx wrote:
> OK, I think I may have answered my own question with help from Mr.
> Google and
> from RTFMing! :)
>  
> The +remote_whatever in the submit file inserts DIRECTLY into the Job's
> ClassAd.
>  
> 
> *Note*: attributes set with '+' are inserted directly into the job's
> ClassAd. Specify attributes as they must appear in the job's ClassAd,
> not the job submission file.
> 
> i.e. in the submit file it might be
> 
> When_To_Transfer_Output
> 
> but in the Job ClassAd it appears as
> 
> WhenToTransferOutput
> 
> Is there a list of submit file command "attributes" to job classad
> conversions?
> Or is just basically removing the underscores? This would appear to be
> the case looking
> at any condor_q -l output.
>  
> Thanks.
>  
> Cheers
>  
> Greg
>  
> 
> Dr. Greg Hitchen
> Physical Scientist | Electron Beam Laboratory
> Earth Sciences and Resource Engineering
> CSIRO
> 
> Phone: +61 8 6436 8663 | Fax: +61 8 6436 8555 | Mobile: 0407 952 748 
> greg.hitchen@xxxxxxxx <mailto:greg.hitchen@xxxxxxxx> | www.csiro.au
> <http://www.csiro.au/> | www.csiro.au/org/CESRE
> <http://www.csiro.au/org/CESRE>
> 
> Address: 26 Dick Perry Avenue, Kensington WA 6151
> 
> *PLEASE NOTE*
> The information contained in this email may be confidential or
> privileged. Any unauthorised use or disclosure is prohibited. If you
> have received this email in error, please delete it immediately and
> notify the sender by return email. Thank you. To the extent permitted by
> law, CSIRO does not represent, warrant and/or guarantee that the
> integrity of this communication has been maintained or that the
> communication is free of errors, virus, interception or interference.
> 
> Please consider the environment before printing this email.
> 
>  
> 
> ------------------------------------------------------------------------
> *From:* condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx] *On Behalf Of
> *Greg.Hitchen@xxxxxxxx
> *Sent:* Wednesday, 19 May 2010 12:11 PM
> *To:* condor-users@xxxxxxxxxxx
> *Subject:* [ExternalEmail] [Condor-users] Using Condor-C grid universe
> 
> We have also been playing with submitting jobs using Condor-C.
>  
> These are jobs submitted from a windows PC to a condor grid resource.
>  
> The remote schedd and cm is running on a linux machine.
>  
> This seems to mostly work OK, however the transfer of input files does
> not seem
> to be occurring. I'm slightly? confused by the documentation in section
> 5.3.1
> where it refers to using +remote_whatever so that the remote machine
> understands
> the attributes of the job.
>  
> The examples given include:
>  
> ****************************************************************************************************
> As an example, a submit description file would ordinarily contain
>  
> when_to_transfer_output = ON_EXIT
>  
> This must appear in the Condor-C job submit description file as
> +remote_WhenToTransferOutput = "ON_EXIT"
>  
> AND
>  
> For the given example, the job is to be run as a vanilla universe job at
> the remote pool.
> The (remote pool's) condor_schedd daemon is likely to place its job
> queue data on a local
> disk and execute the job on another machine within the pool of machines.
> This implies that
> the file systems for the resulting submit machine (the machine specified
> by remote_schedd)
> and the execute machine (the machine that runs the job) will not be
> shared. Thus, the two
> inserted ClassAds
>  
> +remote_ShouldTransferFiles = "YES"
> +remote_WhenToTransferOutput = "ON_EXIT"
>  
> are used to invoke Condor's file transfer mechanism.
>  
> *******************************************************************************************************
> 
> Notice the different syntaxes, i.e. the lack of underscores in the
> +remote commands
> compared with the "standard" syntax as they would normally appear in a
> submit file.
>  
> A condor_q -l for the job on the remote schedd shows these appearing
> exactly as in
> the original submit file, with the +remote stripped off.
>  
> Anyway, I've tried both ways and still can't seem to get input files across.
>  
> Submit file currently looks like:
>  
> 
> universe = grid
> 
> grid_resource = condor condor-per.vm.csiro.au condor-per.vm.csiro.au
> 
> executable = cpubound.exe
> 
> output = cpubound_$(Cluster)_$(Process).out
> 
> error = cpubound_$(Cluster)_$(Process).err
> 
> log = cpubound_$(Cluster)_$(Process).log
> 
> +remote_requirements = (OpSys == "WINNT51")
> 
> +remote_Shortjob = "True"
> 
> +remote_rank = "ConsoleIdle"
> 
> +remote_arguments = "10"
> 
> +remote_transfer_input_files = "D7EG9AB.egs,auto_design7.pegsdat,egs.exe"
> 
> +remote_transfer_files = "ALWAYS"
> 
> +remote_jobuniverse = 5
> 
> +remote_Should_Transfer_Files = "YES"
> 
> +remote_When_To_Transfer_Output = "ON_EXIT"
> 
> #+remote_ShouldTransferFiles = "YES"
> 
> #+remote_WhenToTransferOutput = "ON_EXIT"
> 
> queue 1
> 
>  
>  
> Thanks for any help.
>  
> Cheers
>  
> Greg
>  
> 
> Dr. Greg Hitchen
> Physical Scientist | Electron Beam Laboratory
> Earth Sciences and Resource Engineering
> CSIRO
> 
> Phone: +61 8 6436 8663 | Fax: +61 8 6436 8555 | Mobile: 0407 952 748 
> greg.hitchen@xxxxxxxx <mailto:greg.hitchen@xxxxxxxx> | www.csiro.au
> <http://www.csiro.au/> | www.csiro.au/org/CESRE
> <http://www.csiro.au/org/CESRE>
> 
> Address: 26 Dick Perry Avenue, Kensington WA 6151
> 
> *PLEASE NOTE*
> The information contained in this email may be confidential or
> privileged. Any unauthorised use or disclosure is prohibited. If you
> have received this email in error, please delete it immediately and
> notify the sender by return email. Thank you. To the extent permitted by
> law, CSIRO does not represent, warrant and/or guarantee that the
> integrity of this communication has been maintained or that the
> communication is free of errors, virus, interception or interference.
> 
> Please consider the environment before printing this email.
> 
>  
> 
> 
> 
> _______________________________________________
> 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/