Changes between Version 47 and Version 48 of qcg-directives
- Timestamp:
- 08/26/13 14:03:46 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
qcg-directives
v47 v48 38 38 39 39 = environment = 40 '''environment''' - environment variable. The syntax is ''key'' -> ''value''. Every variable has be be specified in separate line.40 '''environment''' - environment variable. The syntax is ''key'' -> ''value''. Every variable has be be specified in separate directive. 41 41 42 42 {{{ … … 46 46 47 47 = error = 48 '''error''' - location where the system has to stage-out the file containing output of the standard error stream. If the location is not the gsiftp:// url it is assumed that it is relative to the directory from which the task was submitted.48 '''error''' - location where the system is requested to stage out the file containing output of the standard error stream. If the location is not the gsiftp:// url it is assumed that it is relative to the directory from which the task was submitted. 49 49 50 50 {{{ … … 55 55 56 56 = executable = 57 '''executable''' - location of the executable file. The location can be gsiftp:// url or the path to the file. In the second case the location is relative to the directory from which the task was submitted. Optionally it is possible to specify the target name of the file.57 '''executable''' - location of the executable file. The location can be the gsiftp:// url or the path to the file. In the second case the location is relative to the directory from which the task was submitted. Optionally it is possible to specify the target name of the file. 58 58 {{{ 59 59 #QCG executable=gsiftp://qcg.man.poznan.pl//home/plgrid/plgpiontek/reef/executables/exec1 … … 77 77 78 78 = input = 79 '''input''' - location of the file which content will be passed to standard input stream. If the location is not the gsiftp:// url it is assumed that it is relative to the directory from which the task was submitted.79 '''input''' - location of the file which content will be passed to the standard input stream. If the location is not the gsiftp:// url it is assumed that it is relative to the directory from which the task was submitted. 80 80 81 81 {{{ … … 83 83 #QCG input=input.txt 84 84 }}} 85 85 86 = memory = 86 87 '''memory''' - declaration of the maximal amount of memory that can be allocated by the application (in MB). … … 91 92 92 93 = memory-per-slot = 93 '''memory-per-slot''' - declared maximal amount of the memory per slot (core). The total memory requirement is the product of this value and number odslots (cores) used by the application.94 '''memory-per-slot''' - declared maximal amount of the memory per slot (core). The total memory requirement is the product of this value and the number of slots (cores) used by the application. 94 95 95 96 {{{ 96 97 #QCG memory-per-slot=512 97 98 }}} 99 98 100 = module = 99 101 '''module''' - name with optional version of the requested software module. This directive is taken into consideration by the broker in the process of choosing the optimal resource which the task can be executed on. Every module has to be specified in separate directive. … … 103 105 #QCG module=namd 104 106 }}} 107 105 108 = monitor = 106 109 '''monitor''' - task monitoring script executed together with the main application. The script can be used for example to monitor output of the application or to do perform any additional action. … … 124 127 #QCG native=-r n 125 128 }}} 129 126 130 = nodes = 127 '''nodes''' - requested topology of the parallel application. The directive allows to specify requested number of nodes and slots per node. Optionally it is possible to specify number of processes to be executed on every node. If it is not specifyelse the number of processes on every node is equal to the number of slots.131 '''nodes''' - requested topology of the parallel application. The directive allows to specify requested number of nodes and slots per node. Optionally it is possible to specify number of processes to be started on every node. If it is not specified else the number of processes on every node is equal to the number of slots. 128 132 The syntax is: number_of_nodes:number_of_slots[:number_of_processes] 129 133 … … 132 136 #QCG nodes=12:12 133 137 }}} 138 134 139 = not-after = 135 '''not-after''' - directive allowing to specify that the task or reservation has to be executed/reserved "not-later-then". The value of this directive is date with optional time. The directive requires to be specified together with the ''walltime'' one and cannot be used with the ''reservation''. 140 '''not-after''' - directive allowing to specify that the task or reservation has to be executed/reserved "not-later-then". The value of this directive is date with optional time. The directive requires to be specified together with the ''walltime'' one and cannot be used with the ''reservation'' one. 141 136 142 {{{ 137 143 #QCG not-after=2012.08.25 138 144 #QCG walltime=PT2H 139 145 }}} 146 140 147 {{{ 141 148 #QCG not-after=2012.08.25 13:20 142 149 #QCG walltime=PT2H 143 150 }}} 151 144 152 = not-before = 145 not-before - directive allowing to specify that the task or reservation has to be executed/reserved "not-earlier-then". The value of this directive is the date with optional time. The directive requires to be specified together with the ''walltime'' one and cannot be used with the ''reservation'' .153 not-before - directive allowing to specify that the task or reservation has to be executed/reserved "not-earlier-then". The value of this directive is the date with optional time. The directive requires to be specified together with the ''walltime'' one and cannot be used with the ''reservation'' one. 146 154 147 155 {{{ … … 162 170 163 171 = notify = 164 '''notify''' - notify about changes of task status. The directive allows to define the protocol and address which the notification about the change of the status should be sent to. Supported protocols are mail and xmpp/jabber messages.172 '''notify''' - notify about changes of task status. The directive allows to define the protocol and address to which the notification about the change of the status should be sent. Supported protocols are mail and xmpp/jabber messages. 165 173 166 174 {{{ … … 170 178 171 179 To allow receiving xmpp/jabber messages it can be necessary to add the qcg-notification@plgrid.pl sender address to contacts. 180 172 181 = output = 173 '''output''' - location where the file containing the standard output should be transfered. The location can be the gsiftp:// url or the path relative to the directory which the task was submitted from.182 '''output''' - location where the file containing the standard output should be transfered. The location can be the gsiftp:// url or the path relative to the directory from which the task was submitted. 174 183 175 184 {{{ … … 177 186 #QCG output=output.txt 178 187 }}} 188 179 189 = persistent = 180 '''persistent''' - do not remove the working directory.190 '''persistent''' - the directive informing the system to not remove the working directory. 181 191 182 192 '''IMPORTANT:''' the directive should be used only for testing as it causes that the working directory is left and consumes storage resource. The working directory can be later cleaned by the '''qcg-clean''' command. … … 228 238 229 239 = reservation = 230 '''reservation''' - reservation identifier. The identifier can be of the '''local''' type when the reservation was made directly in the queueing system or of '''qcg''' one (default) when the reservation was created by the qcg-reserve command. The directive requires to be used together with the '''host''' one to ensure that the task will be submitted to the host where the reservation was done.240 '''reservation''' - reservation identifier. The identifier can be of the '''local''' type when the reservation was made directly in the queueing system or of the '''qcg''' one (default) when the reservation was created by the qcg-reserve command. The directive requires to be used together with the '''host''' one to ensure that the task will be submitted to the host where the reservation was done. 231 241 232 242 {{{ … … 234 244 #QCG reservation=R1366398248299__4039 235 245 }}} 246 236 247 {{{ 237 248 #QCG host=reef.man.poznan.pl 238 249 #QCG reservation=piontek.0 local 239 250 }}} 251 240 252 = stage-in-dir = 241 '''stage-in-dir''' - input directory. The location of the input directory which can be either gsiftp:// url or the path to the directory relative to the directory which the task was submitted from. The syntax is "location" -> "target name". If the "target name" is not present the directory is stored under its original name.253 '''stage-in-dir''' - input directory. The location of the input directory which can be either the gsiftp:// url or the path to the directory relative to the directory from which the task was submitted. The syntax is "location" -> "target name". If the "target name" is not present the directory is stored under its original name. 242 254 243 255 {{{ … … 255 267 #QCG stage-in-dir=. -> input 256 268 }}} 269 257 270 = stage-in-file = 258 '''stage-in-file''' - input file. The location of the input file which can be either gsiftp:// url or the path to the directory relative to the directory which the task was submitted from. The syntax is "location" -> "target name". If the "target name" is not present the file is stored under its original name.271 '''stage-in-file''' - input file. The location of the input file which can be either the gsiftp:// url or the path to the directory relative to the directory which the task was submitted from. The syntax is "location" -> "target name". If the "target name" is not present the file is stored under its original name. 259 272 260 273 {{{ … … 264 277 #QCG stage-in-file=input_file.txt 265 278 }}} 279 266 280 = stage-out-dir = 267 281 '''stage-out-dir''' - output directory. The location of the output directory which can be either the gsiftp:// url or the path to the directory relative to the directory which the task was submitted from. The syntax is "location" -> "target name". If the "target name" is not present the directory is stored under its original name. … … 274 288 }}} 275 289 276 To transfer the whole working directory ple sease specify the location as "." (dot).290 To transfer the whole working directory please specify the location as "." (dot). 277 291 278 292 {{{ … … 293 307 #QCG stage-out-file=result.txt 294 308 }}} 309 295 310 = use-reservation = 296 '''use-reservation''' - use the advance reservation mechanism. The directive allows to force the system to use advance reservation in case when directives '''not-after''', '''not-before''', '''deadline''' were not used. The directive requires to be used together with the '''walltime''' . The directive cannot be used together with the '''reservation''' one.311 '''use-reservation''' - use the advance reservation mechanism. The directive allows to force the system to use advance reservation in case when directives '''not-after''', '''not-before''', '''deadline''' were not used. The directive requires to be used together with the '''walltime''' one. The directive cannot be used together with the '''reservation''' one. 297 312 298 313 {{{ … … 301 316 }}} 302 317 = use-scratch = 303 '''use-scratch''' - use the scratch space. The directive forces system to use the scratch space if possible.318 '''use-scratch''' - use the scratch space. The directive forces the system to use the scratch space if possible. 304 319 305 320 {{{ … … 325 340 326 341 = watch-output = 327 '''watch-output''' - monitor the output and send notifications about the progress. The directive allows to monitor the output of the application and to send notifications in the requested form. The argument of the directive is the triple of parameters separated by comma :328 * ad ress where the notification will be sent to (supported protocols are mail and xmpp/jabber - see the '''notify''' directives)342 '''watch-output''' - monitor the output and send notifications about the progress. The directive allows to monitor the output of the application and to send notifications in the requested form. The argument of the directive is the triple of parameters separated by commas: 343 * address which the notification will be sent to (supported protocols are mail and xmpp/jabber - see the '''notify''' directives for details) 329 344 * number of seconds between next notifications 330 345 * regular expression or path to the file to generate the content of notification. … … 337 352 #QCG watch-output=mailto:piontek@man.poznan.pl,30,ntf_expr_file 338 353 }}} 354 339 355 = variable = 340 356 '''variable''' - description variable (replaced only in values of QCG directives)