Listing Nodes

List all compute nodes in your Fuzzball cluster

select

Please select either the web UI or CLI tab to see the appropriate instructions for your environment.

web UI

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.

CLI

List all compute nodes in the cluster:

$ fuzzball node list

NODE ID          | HOSTNAME        | CPU TYPE   | TOTAL CORES | TOTAL MEMORY (GB) | TOTAL DEVICES | RUNNING JOBS | CLUSTER
node-worker-01     worker-01.local   cpu/x86_64   8             16.0                2               1               my-cluster
node-worker-02     worker-02.local   cpu/x86_64   16            32.0                3               0               my-cluster
node-worker-03     worker-03.local   cpu/x86_64   32            64.0                4               2               my-cluster

The output shows:

NODE ID: Unique identifier for the node
HOSTNAME: Network hostname
CPU TYPE: CPU model name or architecture
TOTAL CORES: Total number of CPU cores
TOTAL MEMORY (GB): Total memory capacity in Gigabytes
TOTAL DEVICES: Total number of consumable devices
RUNNING JOBS: Number of jobs currently running on this node
CLUSTER: Resolved name of the Fuzzball cluster the node belongs to. If the cluster name cannot be resolved from the local cache or the cluster service, the cell is left blank in node list output. (fuzzball node get falls back to printing the raw cluster_id in this case; see Getting Node Details if you need the underlying ID.) When connected to a Federate cluster, this column distinguishes which underlying Orchestrate cluster each node is part of.

Available Resources

Use the --available flag to show the available resources on each node:

$ fuzzball node list --available

NODE ID         | HOSTNAME         | CPU TYPE   | AVAILABLE CORES | AVAILABLE MEMORY (GB) | AVAILABLE DEVICES | RUNNING JOBS | CLUSTER
node-worker-01    worker-01.local    cpu/x86_64   6                 12.0                    gpu/nvidia:1        1               my-cluster
node-worker-02    worker-02.local    cpu/x86_64   16                32.0                    gpu/nvidia:2        0               my-cluster
node-worker-03    worker-03.local    cpu/x86_64   28                60.0                    gpu/nvidia:4        2               my-cluster

JSON Output

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

$ fuzzball node list --json

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

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