Skip to main content

​
Cluster Management

TensorPool makes it easy to deploy and manage GPU clusters of any size, from single GPUs to large multi-node configurations.

​
Core Commands

​
Cluster Management

  • tp cluster create - Deploy a new GPU cluster
  • tp cluster list - View all your clusters
  • tp cluster info <cluster_id> - Get detailed information about a cluster
  • tp cluster edit <cluster_id> - Edit cluster settings
  • tp cluster destroy <cluster_id> - Terminate a cluster

​
Creating Clusters

Deploy GPU clusters with simple commands. You can create single-node clusters with various GPU configurations, or multi-node clusters for distributed training.

​
Single Node Examples

# Single H100
tp cluster create -i ~/.ssh/id_ed25519.pub -t 1xH100

# Single node with 8x H200
tp cluster create -i ~/.ssh/id_ed25519.pub -t 8xH200

# Single node with 8x B200
tp cluster create -i ~/.ssh/id_ed25519.pub -t 8xB200

# Single node MI300X
tp cluster create -i ~/.ssh/id_ed25519.pub -t 1xMI300X

​
Multi-Node Clusters

For distributed training workloads, create multi-node clusters: 
# 2-node cluster with 8xH200 each (16 GPUs)
tp cluster create -i ~/.ssh/id_ed25519.pub -t 8xH200 -n 2

# 4-node cluster with 8xB200 each (32 GPUs)
tp cluster create -i ~/.ssh/id_ed25519.pub -t 8xB200 -n 4
Multi-node support is currently available for 8xH200 and 8xB200 instance types.

​
Accessing Your Cluster

Once your cluster is ready, use the TensorPool CLI to connect to the instances within the cluster: 
# List all instances in Cluster
tp cluster info <cluster_id>

# SSH into an instance
tp ssh <instance_id>

​
Cluster and Instance Statuses

A cluster’s status is derived from the statuses of its individual instances. Each instance within a cluster progresses through its own lifecycle, and the cluster’s displayed status reflects the highest-priority status among all its instances.

​
Instance Status Lifecycle

Each instance in a cluster follows this lifecycle:

​
Status Definitions

StatusDescription
PENDINGInstance creation request has been submitted and is being queued for provisioning.
PROVISIONINGInstance has been allocated and is being provisioned.
CONFIGURINGInstance is being configured with software, drivers, networking, and storage.
RUNNINGInstance is ready for use.
DESTROYINGInstance shutdown in progress, resources are being deallocated.
DESTROYEDInstance has been successfully terminated.
FAILEDSystem-level problem (e.g., hardware failure, no capacity).

​
Cluster Status Priority

A cluster’s status is determined by the highest-priority status among its instances. Priority order (highest to lowest):
  1. FAILED - Any failed instance causes the cluster to show as failed
  2. DESTROYING - Cluster is being torn down
  3. PENDING - Instances are waiting to be provisioned
  4. PROVISIONING - Instances are being provisioned
  5. CONFIGURING - Instances are being configured
  6. RUNNING - All instances are running
  7. DESTROYED - All instances have been terminated
For example, if a cluster has 3 instances where 2 are RUNNING and 1 is CONFIGURING, the cluster status will show as CONFIGURING.

​
Next Steps