GetNodeResult

data class GetNodeResult(val acceleratorType: String, val apiVersion: String, val cidrBlock: String, val createTime: String, val description: String, val health: String, val healthDescription: String, val ipAddress: String, val labels: Map<String, String>, val name: String, val network: String, val networkEndpoints: List<NetworkEndpointResponse>, val port: String, val schedulingConfig: SchedulingConfigResponse, val serviceAccount: String, val state: String, val symptoms: List<SymptomResponse>, val tensorflowVersion: String, val useServiceNetworking: Boolean)

Constructors

Link copied to clipboard
fun GetNodeResult(acceleratorType: String, apiVersion: String, cidrBlock: String, createTime: String, description: String, health: String, healthDescription: String, ipAddress: String, labels: Map<String, String>, name: String, network: String, networkEndpoints: List<NetworkEndpointResponse>, port: String, schedulingConfig: SchedulingConfigResponse, serviceAccount: String, state: String, symptoms: List<SymptomResponse>, tensorflowVersion: String, useServiceNetworking: Boolean)

Types

Link copied to clipboard
object Companion

Properties

Link copied to clipboard

The type of hardware accelerators associated with this node.

Link copied to clipboard

The API version that created this Node.

Link copied to clipboard

The CIDR block that the TPU node will use when selecting an IP address. This CIDR block must be a /29 block; the Compute Engine networks API forbids a smaller block, and using a larger block would be wasteful (a node can only consume one IP address). Errors will occur if the CIDR block has already been used for a currently existing TPU node, the CIDR block conflicts with any subnetworks in the user's provided network, or the provided network is peered with another network that is using that CIDR block.

Link copied to clipboard

The time when the node was created.

Link copied to clipboard

The user-supplied description of the TPU. Maximum of 512 characters.

Link copied to clipboard

The health status of the TPU node.

Link copied to clipboard

If this field is populated, it contains a description of why the TPU Node is unhealthy.

Link copied to clipboard

DEPRECATED! Use network_endpoints instead. The network address for the TPU Node as visible to Compute Engine instances.

Link copied to clipboard

Resource labels to represent user-provided metadata.

Link copied to clipboard

Immutable. The name of the TPU

Link copied to clipboard

The name of a network they wish to peer the TPU node to. It must be a preexisting Compute Engine network inside of the project on which this API has been activated. If none is provided, "default" will be used.

Link copied to clipboard

The network endpoints where TPU workers can be accessed and sent work. It is recommended that Tensorflow clients of the node reach out to the 0th entry in this map first.

Link copied to clipboard

DEPRECATED! Use network_endpoints instead. The network port for the TPU Node as visible to Compute Engine instances.

Link copied to clipboard

The scheduling options for this node.

Link copied to clipboard

The service account used to run the tensor flow services within the node. To share resources, including Google Cloud Storage data, with the Tensorflow job running in the Node, this account must have permissions to that data.

Link copied to clipboard

The current state for the TPU Node.

Link copied to clipboard

The Symptoms that have occurred to the TPU Node.

Link copied to clipboard

The version of Tensorflow running in the Node.

Link copied to clipboard

Whether the VPC peering for the node is set up through Service Networking API. The VPC Peering should be set up before provisioning the node. If this field is set, cidr_block field should not be specified. If the network, that you want to peer the TPU Node to, is Shared VPC networks, the node must be created with this this field enabled.