This shows you the differences between two versions of the page.
| Next revision | Previous revision |
| technical:slurm:templates:start [2019-06-15 08:19] – created frey | technical:slurm:templates:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 |
|---|
| ====== Caviness Slurm Job Script Templates ====== | |
| |
| On both Mills and Farber, example job scripts were made available under the ''/opt/templates/gridengine'' directory. Each template contained extensive Bash code to sense and setup the job environment. Since the script templates were thus self-contained, they had no external dependencies. | |
| |
| One major problem with this paradigm comes when changes must be made to templates. Since users must make copies of the template, they are responsible for merging any ongoing change into their copies. In practice, this simply does not happen: a working job script is reused over and over again without modification. | |
| |
| On Caviness, the job script templates have been modularized. Most of the environment sense and setup code has been shifted out of the job script templates and into external fragments that are sourced (executed) by the job script. What remains in the job script templates is setting of variables that influence those external fragments' execute and the sourcing of them. Now, when IT must change the behavior of job scripts, the external fragments are modified and the change is effected for all job scripts deriving from the templates. | |