Terminal
Terminal/Skill
Sets up GPU clusters on Together AI with Kubernetes or Slurm, shared storage, and credentials, for teams needing multi node compute.
By Together AI
Works with
npx skills add togethercomputer/skills --skill together-gpu-clustersUse Together AI GPU clusters when the user needs infrastructure control instead of a managed inference product.
Typical fits:
together-dedicated-model-inference for managed single-model hostingtogether-dedicated-containers for containerized inference without owning the full clustertogether-sandboxes for short-lived remote Python executiontogether-fine-tuning for managed training jobs instead of raw cluster operationstogether>=2.0.0). If the user is on an older version, they must upgrade first: uv pip install --upgrade "together>=2.0.0".shared_volume over creating a volume separately and attaching via volume_id. Separately created volumes may land in a different datacenter partition than the cluster, causing a "does not exist in the datacenter" error even when the volume shows as available.list_regions() first and be prepared to try multiple regions.ON_DEMAND has no one-hour duration flag. For a one-hour plan, omit
--duration-days, create the cluster only when authorized, then delete it
after the intended runtime. If the user requests a command without
provisioning, print it but do not run it.cuda_version and nvidia_driver_version as separate fields in addition to the combined driver_version string. Pass them via extra_body in the Python SDK.slurm.conf) are Slinky v1.0 only. A non-zero exit from a worker prolog or epilog drains the node, and calling Slurm commands (squeue, scontrol, sacctmgr) inside any prolog/epilog can deadlock the scheduler.