Listing Nodes

The Nodes page displays all compute nodes with their cluster affiliation, resource totals, and running job counts. When connected to a Federate cluster, a Cluster column identifies which underlying Orchestrate cluster each node belongs to.

Use the Health filter to narrow the list to nodes in a given health state – most often Degraded, to see just the nodes that need attention. The filter is carried in the page URL, so a filtered view can be shared. Sorting by Score ascending puts the worst hardware first; nodes that have not been scored yet sort to the end in either direction, so they never displace the failing hardware at the top of the list.

Click a node to open its details, which include the conditions and score breakdown behind its health – see Node Details.

List all compute nodes in the cluster:

$ fuzzball node list

ID               | CLUSTER  | HOSTNAME        | STATUS | HEALTH   | SCORE | JOBS
node-worker-01     fb-aws    worker-01.local   Ready    Healthy    100     1
node-worker-02     fb-aws    worker-02.local   Ready    Degraded   55      0
node-worker-03     fb-aws    worker-03.local   Ready    Unknown    -       2

The output shows:

• ID: Unique identifier for the node
• CLUSTER: Resolved cluster name
• HOSTNAME: Network hostname
• STATUS: Scheduling status – Ready, Not Ready, Offline or Cordoned
• HEALTH: Health state – Healthy, Degraded, or Unknown when a node’s telemetry has gone stale
• SCORE: Reliability score out of 100, or - for a node that has not been scored yet
• JOBS: Number of jobs currently running on this node

See Node Health Monitoring for what the health state and score mean and how they are configured.

For the full record (CPU type, total/allocated/available cores and memory, device summaries, the running fuzzball-substrate version, etc.) use -o yaml or -o json. When connected to a Federate cluster, the CLUSTER column distinguishes which underlying Orchestrate cluster each node is part of.

Each node record reports the running Substrate version (as reported by substrate itself) – shown as substrate_version in -o yaml output and substrateVersion in -o json output. It is not a column in the default table; use -o yaml/-o json or fuzzball node show to see it. In -o yaml the field is omitted for nodes running a substrate version that does not report it; in -o json it renders as an empty string.

Use the --available flag to compute the per-node available cores, memory, and devices alongside the totals (visible in JSON / YAML output):

$ fuzzball node list --available -o yaml

For programmatic access or scripting, use the -o json flag:

$ fuzzball node list -o json

This returns node information in JSON format suitable for parsing with tools like jq:

$ fuzzball node list -o json | jq '.[] | select(.running_jobs > 0)'