Changes between Version 9 and Version 10 of JobTemplates

Timestamp:

Jan 12, 2017, 12:35:35 AM (7 years ago)

Author:

davea

Comment:

--

JobTemplates

@@ -6 +6 @@
 Typically the same templates are used for many jobs.
 
+A given app usually has one input and output template.
+However, apps that can have varying numbers of files would need multiple templates,
+one per file "signature".
+
 == Input templates ==
 
 An input template file describes the job's input files, resource requirements, and scheduling parameters.
-It has the form
+
+Input files are of two types:
+
+ * '''Variable files''' can vary between jobs.
+   The job submission interfaces such as [JobSubmission#creatework-tool create_work()]
+   supply the physical names of the input files for that job.
+
+ * '''Constant files''' are the same across multiple jobs.
+   The physical name of the file is given in the input template;
+   it is not passed to the job-submission interfaces.
+   This might be used, for the files that make up a Docker image.
+   
 {{{
-
 <input_template>
     <file_info>
         <number>0</number>
+          [ <name>...</name> ]
         [ <gzip/> ]
         [ <sticky/> ]
@@ -52 +67 @@
 
  '''<number>''':: use 0, 1, ...
+ '''<name>''':: specified only for constant files.
+   The physical name of the file.
+   The file must be staged before jobs are created with the template.
  '''<gzip/>''':: transfer the file in gzipped (compressed) format to reduce network usage.
    You must [JobStage stage the file with the --gzip option].
@@ -96 +114 @@
 This is enough for about 200 input files,
 fewer if you use long file names or multiple download URLs.
-If this isn't enough, you can use [FileCompression BOINC file compression] to zip several files into a single file reference for download,
+If this isn't enough, you can use [FileCompression BOINC file compression]
+to zip several files into a single file reference for download,
 and expanding them prior to running on the client machine.
 
@@ -142 +161 @@
    and moved to the project directory after the job has finished.
    Use this for [WrapperApp legacy applications].
-   '''Important''': If the slot directory and the project directory are on the same filesystem, the file is moved instead of copied!
+   '''Important''': If the slot directory and the project directory are on the same filesystem,
+   the file is moved instead of copied!
  '''<generated_locally/>''':: always include this for output files.
  '''<max_nbytes>''':: maximum file size.