Slurm compatibility mode — future consideration

[seilk]

Context

opensmi is currently scoped as a standalone alternative to Slurm, not a supplement.

Running opensmi alongside Slurm causes fundamental conflicts:

• CUDA_VISIBLE_DEVICES: Slurm uses 0-based GPU remapping; opensmi uses physical indices
• Process lifecycle: opensmi tmux sessions run outside Slurm cgroups, bypassing Slurm's resource accounting

This is documented in README (commit b4bc937).

Future scope

If Slurm compatibility is ever added, it would require:

• Slurm environment detection ($SLURM_JOB_ID check)
• CUDA_VISIBLE_DEVICES delegation (respect Slurm remapping, don't override)
• cgroup-aware process lifecycle management

Current status

Not planned. Tracking for future consideration only.