TPU VM

Related topics

• Agent Platform works with TPU VM From the official documentation: “Agent Platform supports training with various frameworks and libraries using a TPU VM.”
• Cloud TPU works with TPU VM From the official documentation: “Google Cloud makes TPUs available as compute resources through TPU VMs.”
• Compute Engine works with TPU VM From the official documentation: “This page describes how to connect to, view information about, delete, or reset a TPU VM using Compute Engine.”
• managed instance group works with TPU VM From the official documentation: “For information about applying new TPU VM configurations in a managed instance group (MIG), see [Apply new VM configurations in a MIG](/compute/docs/instance-groups/updating-migs).”
• Shared VPC works with TPU VM From the official documentation: “You connect a TPU VM to a Shared VPC network when you create your TPU.”
• TPU VM depends on Compute Engine From the official documentation: “TPU VMs are instances of Compute Engine VMs with attached TPU hardware.”
• TPU VM is part of managed instance group From the official documentation: “To create multiple, independent TPU VMs in a MIG: 1. Create an instance template. 2. Create the MIG.”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
• Apigee works with Shared VPC From the official documentation: “If your project uses Shared Virtual Private Cloud (VPC) networking, you can select the shared network that will be used to peer with Apigee.”
• Shared VPC works with VPC Service Controls From the official documentation: “If you use both Shared VPC and VPC Service Controls, the host project that contains the network and the service project that contains the Managed Lustre instance must both be inside the same perimeter.”
• Spot VMs is part of Compute Engine From the official documentation: “Spot VMs are virtual machine (VM) instances that are excess Compute Engine capacity.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• managed instance group works with Spot VMs From the official documentation: “This document explains how to create a managed instance group (MIG) that uses Spot VMs.”
• Agent Platform works with Cloud Storage From the official documentation: “Load the model's `state_dict` object into Cloud Storage by using a Agent Platform custom job:”
• Agent Platform works with Spot VMs From the official documentation: “Using Spot VMs with Agent Platform is supported only for serverless training and inference.”
• Apigee works with Compute Engine From the official documentation: “| [Compute Engine](https://console.cloud.google.com/apis/library/compute.googleapis.com) | `compute.googleapis.com` | Used for managing your Apigee runtime. |”
• Cloud TPU works with Compute Engine From the official documentation: “You can use TPUs through Compute Engine, Google Kubernetes Engine, and Vertex AI.”
• managed instance group is part of Compute Engine From the official documentation: “Checks if a Compute Engine Managed Instance Group (MIG) is configured as Zonal.”
• VPC Service Controls secures Cloud TPU From the official documentation: “The API for Cloud TPU can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• VPC Service Controls secures Compute Engine From the official documentation: “To further protect your Compute Engine resources, you can protect them using [VPC Service Controls](/vpc-service-controls/docs/overview).”
• Agent Platform works with Cloud Logging From the official documentation: “If any containers restart before Agent Platform shuts down the entire job, these containers may produce logs in Cloud Logging.”
• Agent Platform works with GKE From the official documentation: “GKE reserves memory on Agent Platform nodes.”
• Agent Platform works with VPC Service Controls From the official documentation: “If you use Agent Platform in a VPC-SC environment, you must create an ingress rule in your perimeter to allow ingress from the Reasoning Engine Service Agent (`service-PROJECT_NUMBER@gcp-sa-aiplatform-re.iam.gserviceaccount.com`) into the `storage.googleapis.com` service and…”
• Apigee works with Cloud Logging From the official documentation: “This page describes how to find and use [Cloud Logging](/logging/docs) to query and view maintenance logs for an Apigee instance.”
• Apigee works with managed instance group From the official documentation: “There are a set of VMs (with an `apigee-proxy` prefix) running in a managed instance group (MIG) that forward the traffic to the Apigee instance.”
• Apigee works with VPC Service Controls From the official documentation: “Apigee integrations with VPC Service Controls have the following limitations:”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “When you specify your own service account for builds, you must store your build logs either in Cloud Logging or in a user-created Cloud Storage bucket.”
• Cloud Logging works with Cloud TPU From the official documentation: “Cloud TPU logs upcoming maintenance events in Cloud Logging by the individual VM instance, for example, `t1v-n-5bdca789-w-0`.”
• Cloud Logging works with VPC Service Controls From the official documentation: “This page describes how you can find VPC Service Controls errors using Cloud Logging.”
• Cloud Storage works with Cloud TPU From the official documentation: “Ensure you are using a regional Cloud Storage bucket in the same region as the TPU for training datasets and checkpoints.”
• Cloud Storage works with GKE From the official documentation: “Route Cloud Storage events to GKE”
• Cloud TPU works with GKE From the official documentation: “The following sections describe error messages related to TPU and GKE setups and resolutions.”
• Compute Engine works with GKE From the official documentation: “For example, Google Kubernetes Engine (GKE) can cause usage in Compute Engine.”
• GKE works with Shared VPC From the official documentation: “For networking, GKE clusters are deployed in a Shared VPC that's created as part of the enterprise foundation blueprint.”
• Spot VMs is part of GKE From the official documentation: “The following table describes the modifiable options for the termination and graceful shutdown period for Spot VMs in GKE.”
• VPC Service Controls secures Agent Platform From the official documentation: “(Optional) To mitigate the risk of data exfiltration from Agent Platform, enable VPC Service Controls and specify a VPC network when you create a cluster.”
• VPC Service Controls secures Cloud Logging From the official documentation: “The API for Cloud Logging can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• VPC Service Controls secures GKE From the official documentation: “The Kubernetes Engine API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”