https://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422017-09-26T18:56:29ZArvadosArvados - Idea #12289: Migrate to Slurm APIhttps://dev.arvados.org/issues/12289?journal_id=553742017-09-26T18:56:29ZTom Morristfmorris@veritasgenetics.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/55374/diff?detail_id=53197">diff</a>)</li></ul> Arvados - Idea #12289: Migrate to Slurm APIhttps://dev.arvados.org/issues/12289?journal_id=553792017-09-26T19:55:30ZTom Cleggtom@curii.com
<ul></ul><p>Potential benefits include better compatibility across slurm versions (less CLI-output-parsing code) and lower overhead (less shelling out to CLI).</p>
<p>However, <a class="external" href="https://github.com/PySlurm/pyslurm">https://github.com/PySlurm/pyslurm</a> says</p>
<blockquote>
<p>You will need to instruct the setup.py script where either the Slurm install root directory or where the Slurm libraries and Slurm include files are</p>
</blockquote>
<p>It sounds like this package provides an API client for a specific version of slurm, which could be just another distribution/deployment nightmare. It only makes sense if every (current+future) slurm library version is forward & backward compatible with all slurm versions. Otherwise, CLI tools are more reliable -- at least it's <em>possible</em> to accommodate versions with "if v3 then X else Y" when necessary.</p> Arvados - Idea #12289: Migrate to Slurm APIhttps://dev.arvados.org/issues/12289?journal_id=943872021-07-06T21:18:40ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Category</strong> set to <i>Git hosting</i></li></ul> Arvados - Idea #12289: Migrate to Slurm APIhttps://dev.arvados.org/issues/12289?journal_id=951012021-07-07T18:34:47ZWard Vandewegeward@curii.com
<ul><li><strong>Target version</strong> deleted (<del><i>Arvados Future Sprints</i></del>)</li></ul>