<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div dir="auto" id="mail-editor-reference-message-container">Hi David,</div>
<div dir="auto" id="mail-editor-reference-message-container"><br>
</div>
<div dir="auto" id="mail-editor-reference-message-container">I would recommend using one of the many workflow management systems (WMS) that can define job dependencies programmatically rather than fuss with base Slurm commands. Some examples I have used or
have been recommended to me:<span></span></div>
<div dir="auto" id="mail-editor-reference-message-container"><br>
</div>
<div dir="auto" id="mail-editor-reference-message-container">- <a href="https://pegasus.isi.edu/">https://pegasus.isi.edu/</a></div>
<div dir="auto" id="mail-editor-reference-message-container">- <a href="https://cylc.github.io/" style="font-size: 12pt;">https://cylc.github.io/</a></div>
<div dir="auto" id="mail-editor-reference-message-container">- <a href="http://parsl-project.org/">http://parsl-project.org/</a></div>
<div dir="auto" id="mail-editor-reference-message-container">- <a href="https://airflow.apache.org/">https://airflow.apache.org/</a></div>
<div dir="auto" id="mail-editor-reference-message-container"><br>
</div>
<div dir="auto" id="mail-editor-reference-message-container">Each of these runs in production on a number of major projects and has active support from developers. Making a pipeline DAG makes managing jobs and rerunning tests so much nicer. No reason to write
from scratch what already exists.</div>
<div dir="auto" id="mail-editor-reference-message-container"><br>
</div>
<div dir="auto" id="mail-editor-reference-message-container">Cheers,</div>
<div dir="auto" id="mail-editor-reference-message-container">Matt West</div>
<div dir="auto" id="mail-editor-reference-message-container"><br>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" style="font-size: 11pt;" dir="auto"><strong>From:</strong> slurm-users <slurm-users-bounces@lists.schedmd.com> on behalf of David Henkemeyer <david.henkemeyer@gmail.com><br>
<strong>Sent:</strong> Monday, May 9, 2022, 22:59<br>
<strong>To:</strong> Slurm User Community List <slurm-users@lists.schedmd.com><br>
<strong>Subject:</strong> [slurm-users] How to run a job at the end of a set of jobs<br>
</div>
<br>
<div style="background-color:#FFEB9C; width:100%; border-style:solid; border-color:#9C6500; border-width:1pt; padding:2pt; font-size:10pt; line-height:12pt; font-family:'Calibri'; color:Black; text-align:left" dir="auto">
<span style="color:#9C6500; font-weight:bold">CAUTION:</span> This email originated from outside of the organisation. Do not click links or open attachments unless you recognise the sender and know the content is safe.</div>
<br>
<div dir="auto">
<div dir="ltr">Prologue is a feature whereby I can run something after a single job. Is there a best practice for running a job after a set of jobs?<br>
<br>
We submit a bunch of jobs to a bunch of nodes, and after all the jobs are done, we would like to submit a "utility job" on each node, but it has to be the last job. What would be the various ways to achieve this?
<div><br>
</div>
<div>Thanks</div>
<div>David</div>
</div>
</div>
<br>
</div>
</body>
</html>