Cloud TPU
TPU VM exposing Google's ML accelerator chips, alone or in a multi-host slice.
- Provider
- gcp
- Kind
- Virtual machine
- Category
- Compute
- Official docs
- https://cloud.google.com/tpu/docs/intro-to-tpu
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| chipsPerHost | integer | — | no | 8 | inherited |
| diskEncryption | boolean | — | no | — | ▸ true |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ false |
| memoryGib | integer | — | no | — | inherited |
| os | enum | linux | windows | aix | ibm-i | no | linux | ▸ linux |
| publicIp | boolean | — | no | — | inherited |
| sizeVcpu | integer | — | no | — | inherited |
| sliceScope | enum | single-host | multi-host | no | single-host | inherited |
| tpuVersion | enum | v4 | v5e | v5p | v6e | tpu7x | no | — | inherited |
| zoneRedundant | boolean | — | no | — | ▸ false |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
stateful-node-without-zone-redundancy
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "cloud-tpu", component: "google-cloud-tpu" }Auto Scalingalibaba-auto-scalingElastic Compute Servicealibaba-ecsEdge Node Servicealibaba-ensSimple Application Serveralibaba-simple-application-serverAmazon EC2aws-ec2Amazon EC2 Auto Scalingaws-ec2-auto-scalingAmazon EC2 Dedicated Hostsaws-ec2-dedicated-hostAmazon Elastic VMware Serviceaws-evsAmazon Lightsailaws-lightsailAWS Nitro Enclavesaws-nitro-enclaveAzure BareMetal Infrastructureazure-baremetal-infrastructureAzure Compute Fleetazure-compute-fleetAzure Dedicated Hostazure-dedicated-hostAzure Data Science Virtual Machineazure-dsvmNutanix Cloud Clusters on Azureazure-nutanix-cloud-clustersAzure Virtual Machinesazure-virtual-machineAzure Virtual Machine Scale Setsazure-vm-scale-setAzure VMware Solutionazure-vmware-solutionCrusoe Cloud VMcrusoeFirecrackerfirecrackerMicrosoft Hyper-Vhyper-vKubeVirtkubevirtLambda Cloud instancelambda-labsKVM with libvirtlibvirtNebius AI Cloud VMnebiusNutanix AHVnutanix-ahvOpenStack Novaopenstack-novaoVirtovirtProxmox VEproxmoxRunpod PodrunpodVast.ai instancevast-aiGeneric virtual machinevirtual-machineVMware vSpherevsphereXCP-ngxcp-ngXenServerxenserverDigitalOcean Bare Metal GPUsdigitalocean-bare-metal-gpuDropletsdigitalocean-dropletDroplet Autoscale Pooldigitalocean-droplet-autoscaleBare Metal Solutiongoogle-bare-metal-solutionCompute Enginegoogle-compute-engine
and 20 more → Virtual machine page# yaml-language-server: $schema=../../schema/component.schema.json # Cloud TPU: Google's ML accelerator ASICs, reached as TPU VMs built on Compute Engine # ("Introduction to Cloud TPU"). Chips are grouped into slices; on v6e a slice of up to 8 chips # attaches to a single host and 4x4 and larger topologies need multiple hosts, up to a 256-chip pod # ("TPU v6e"). Code must be compiled by XLA. schemaVersion: "1" type: "component" id: "google-cloud-tpu" kind: "virtual-machine" provider: "gcp" docs: "https://cloud.google.com/tpu/docs/intro-to-tpu" defaults: managed: false os: "linux" diskEncryption: true zoneRedundant: false properties: tpuVersion: type: "enum" values: ["v4", "v5e", "v5p", "v6e", "tpu7x"] sliceScope: type: "enum" values: ["single-host", "multi-host"] default: "single-host" chipsPerHost: type: "integer" default: 8