Skip to main content

View a SLURM cluster and inspect nodes and jobs.

Project description

Slurm Viewer

PyPI - Python Version Gitlab Pipeline Status GitLab Last Commit GitLab Issues PyPI - License PyPI - Status PyPI - Version Pepy Total Downloads

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-viewer command 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-viewer presents 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.

slurm-viewer nodes

Slurmviewer Queue

Slurmviewer SPU

Installation

pip install slurm-viewer

or

uvx slurm-viewer

Usage

  • Run slurm-viewer to 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 are nodes, jobs, gpu and status.
  • 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 the node- prefix by setting node_name_ignore_prefix = ["node"]
  • 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/config to set up the connections and use the Host name as the server. status
[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>

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

slurm_viewer-1.0.5-py3-none-any.whl (4.4 MB view details)

Uploaded Python 3

File details

Details for the file slurm_viewer-1.0.5-py3-none-any.whl.

File metadata

  • Download URL: slurm_viewer-1.0.5-py3-none-any.whl
  • Upload date:
  • Size: 4.4 MB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.5

File hashes

Hashes for slurm_viewer-1.0.5-py3-none-any.whl
Algorithm Hash digest
SHA256 1a1659b398a32bcca7ff684b7b3d6424e23908e9b6c61c9e6229b5a6e3077e34
MD5 0d196f36834d58799129094fafaf13e1
BLAKE2b-256 79201d2777757e67aada143bb64dc6e060e805ea63f78128f2481337ebfe918c

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page