Slurm Viewer
Introduction
Using a single terminal command, slurm-viewer allows you to view the status of your SLURM cluster (i.e., nodes and jobs). This command combines information from SLURM commands like sinfo, scontrol, squeue and sacct in a tabular and customizable view.
This command line application can be run on the cluster itself or any computer that can ssh into the cluster.
Features
- Single command: The
slurm-viewercommand allows you to view the status of nodes and jobs in your SLURM cluster.- Multiple Clusters: View multiple clusters in a single interface.
- SSH Tunneling: Connect to the cluster using a jumphost/gateway.
- Intuitive Interface:
slurm-viewerpresents all node/job information in a tabular format. - Customizable Interface: Filter and sort nodes and jobs based on various criteria like partitions and GPU availability
- Resource Utilization Plots: View the GPU memory/utilization used over the last 4 weeks.
Installation
pip install slurm-viewer
or
uvx slurm-viewer
Usage
- Run
slurm-viewerto start the UI. - Upon the first run, a default settings file will be created in
~/.config/slurm-viewer/settings.toml. Edit this file to reflect your setup.
Settings
The settings.toml config file allows for defining which clusters you want to connect to and also user preferences on which columns to display.
The location of the used settings file can be found in the help window.
The primary tags are ui and clusters.
UI
In the ui section you can define which columns to display for nodes (node_columns), queue (queue_columns) and priority (priority_columns) views. The columns are defined as a list of strings.
Although the UI allows the reordering of columns it is easier to edit the settings.toml and reload the config using F3. That way the order is preserved for the next time.
Clusters
In the clusters section you can define the clusters you want to connect to. Each cluster has the following tags:
name: A user-defined name of the cluster.partitions: A list of partitions you are interested to view in the cluster.tabs: A list of tabs to display in the UI. The options arenodes,jobs,gpuandstatus.node_name_ignore_prefix: A list of prefixes to ignore in the node names.- For e.g. if the node names are
node-1,node-2,node-3, you can ignore thenode-prefix by settingnode_name_ignore_prefix = ["node"]
- For e.g. if the node names are
servers: A list of servers to connect to the cluster itself. A cluster can have multiple servers defined, they will be tried in order and the first server that connects will be used.- If you have a jumphost/gateway, use the
~/.ssh/configto set up the connections and use theHostname as the server.status
- If you have a jumphost/gateway, use the
[ui]
node_columns = ["node_name", "state", "gpu_tot", "gpu_alloc", "gpu_avail", "gpu_type", "gpu_mem", "cpu_tot", "cpu_alloc", "cpu_avail", "mem_tot", "mem_alloc", "mem_avail", "cpu_gpu", "mem_gpu", "cpuload", "partitions", "active_features"]
queue_columns = ["user", "job_id", "reason", "exec_host", "start_delay", "run_time", "time_limit", "command"]
priority_columns = ["user_name", "job_id", "job_priority_n", "age_n", "fair_share_n", "partition_name"]
refresh_interval = 10 # Interval in seconds when auto refresh is enabled
auto_refresh = "False" # Automatically refresh 'nodes' and 'queue' tabs at the given interval
user_only = "False" # Start with data for the user only or all users of the cluster
[[clusters]]
name = "cluster_1"
partitions = ["partition-cpu", "partition-gpu"]
tabs=["nodes", "jobs", "gpu", "status"]
node_name_ignore_prefix = [""]
servers = ["cluster_1_logon_node_1", "cluster_1_logon_node_2"]
[[clusters]]
name = "cluster_2"
partitions = ["cpu-short", "cpu-medium", "cpu-long", "gpu-short", "gpu-medium", "gpu-long"]
node_name_ignore_prefix = ["node"]
server = "gateway_1"
If you need to connect using a jumphost/gateway use the ~/.ssh/config to setup the connections and use the Host name as
the server.
Example of an ssh config:
Host gateway_1
User my_user_name
HostName gateway.somewhere
Host cluster_1_logon_node_1
User my_user_name
HostName logonnode.somewhere
ProxyCommand ssh -W %h:%p gateway_1
Advanced
# Run from testpypi
uvx --index https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple --index-strategy unsafe-best-match slurm-viewer==<specific version>
Metadata
Release files for slurm-viewer 1.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| slurm_viewer-1.0.5-py3-none-any.whl | Python 3 | none | any | Details for slurm_viewer-1.0.5-py3-none-any.whl |
Release files / slurm_viewer-1.0.5-py3-none-any.whl
| Download URL | slurm_viewer-1.0.5-py3-none-any.whl |
|---|---|
| Size | 4.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1a1659b398a32bcca7ff684b7b3d6424e23908e9b6c61c9e6229b5a6e3077e34
|
|
BLAKE2b-256 checksum How to use checksums |
79201d2777757e67aada143bb64dc6e060e805ea63f78128f2481337ebfe918c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for slurm-viewer 1.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.