TULPAR

Unified Cluster Dashboard

The Whole Cluster on One Screen

Node health, workload, resource consumption and open alerts converge on a single board — it refreshes itself over WebSocket, so you never have to go looking for a problem.

A board that refreshes itself

Metrics and states stream in live; no page reloads, no stale numbers.

Problems surface first

Nodes with failing health checks and firing alerts are collected at the top of the board.

TULPAR / Unified Cluster Dashboard
Unified Cluster Dashboard
Current TULPAR interface in Turkish · Sample test data

What's Inside

Status at a Glance, Depth on a Click

The dashboard doesn't just summarize — every card is a door into the management screen behind it.

01

Cluster Status

Node status distribution — ready, installing, down and needs-attention — summarized in one chart.

02

Live Time Series

CPU, memory and load curves; pick a node to drill into a single machine's resource profile.

03

Workload Summary

Running, pending and completed job counts read live from Slurm.

04

Open Alerts

Firing alerts and failing health checks are listed with a link straight to the node concerned.

05

Quick Access

One-click cards into inventory, provisioning, monitoring, Slurm and alerting.

06

Role-Aware View

RBAC scope applies to the dashboard too — everyone sees only the data they are entitled to.

TULPAR / Unified Cluster Dashboard

The Data Path Behind the Board

Every number on the board has a known origin; this is a mirror of the live system, not a showcase.

Live streaming over WebSocket
Dashboard data streams over WebSocket rather than periodic polling; if the connection is blocked it falls back to HTTP polling automatically.
One board, many systems
Slurm (slurmrestd), Prometheus metrics, inventory and the alerting engine converge on the same screen — no tab-switching between systems.
Cluster health screen
Health checks are broken down per node; which machine failed, when and why is on the record.
Event stream
Cluster events collect into a central timeline; findings from the nightly audits are written here too.
Unified Cluster Dashboard
The Data Path Behind the Board
Current TULPAR interface in Turkish · Sample test data

GOOD TO KNOW

Frequently Asked Questions

Got questions? Everything you need to know about installation, licensing and scaling is here.

How is TULPAR licensed?
TULPAR is an enterprise product offered under a commercial license. Licensing is annual, based on your cluster scale and the support coverage you need; every license includes the full feature set — there is no feature gating. Contact us through the contact page for a quote.
How long does installation take and what do I need?
An EL9-based head server is enough. tulpar-preflight.sh prepares the prerequisites, install.sh brings up the whole stack; you then enter the admin password, NTP, LDAP and SLURM settings in the web wizard. A typical installation completes in minutes.
Does it work with my existing Slurm cluster?
TULPAR talks to Slurm over the slurmrestd REST API and falls back to the CLI automatically, providing a stable, version-independent interface. Head Slurm components run natively on the host (dnf/systemd) and share the same repository and version as the compute nodes.
Can it be installed in an air-gapped environment without internet access?
Yes. RPM repositories travel with the product, the Slurm package repository can be imported as a GPG-signed offline bundle, and container images are loaded with docker load. Every component works on a closed network, including node installation, monitoring and central logging.

READY FOR YOUR NEXT COMPUTATION

Unleash your
infrastructure’s potential.

Let’s explore what TULPAR can do for your cluster.

Request a demo