This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

gcp_compute_node_template

accelerators

Type: UNORDERED_LIST_STRUCT
Provider name: accelerators

  • accelerator_count
    Type: INT32
    Provider name: acceleratorCount
    Description: The number of the guest accelerator cards exposed to this instance.
  • accelerator_type
    Type: STRING
    Provider name: acceleratorType
    Description: Full or partial URL of the accelerator type resource to attach to this instance. For example: projects/my-project/zones/us-central1-c/acceleratorTypes/nvidia-tesla-p100 If you are creating an instance template, specify only the accelerator name. See GPUs on Compute Engine for a full list of accelerator types.

ancestors

Type: UNORDERED_LIST_STRING

cpu_overcommit_type

Type: STRING
Provider name: cpuOvercommitType
Description: CPU overcommit.
Possible values:

  • CPU_OVERCOMMIT_TYPE_UNSPECIFIED
  • ENABLED
  • NONE

creation_timestamp

Type: TIMESTAMP
Provider name: creationTimestamp
Description: [Output Only] Creation timestamp in RFC3339 text format.

description

Type: STRING
Provider name: description
Description: An optional description of this resource. Provide this property when you create the resource.

disks

Type: UNORDERED_LIST_STRUCT
Provider name: disks

  • disk_count
    Type: INT32
    Provider name: diskCount
    Description: Specifies the number of such disks.
  • disk_size_gb
    Type: INT32
    Provider name: diskSizeGb
    Description: Specifies the size of the disk in base-2 GB.
  • disk_type
    Type: STRING
    Provider name: diskType
    Description: Specifies the desired disk type on the node. This disk type must be a local storage type (e.g.: local-ssd). Note that for nodeTemplates, this should be the name of the disk type and not its URL.

gcp_status

Type: STRING
Provider name: status
Description: [Output Only] The status of the node template. One of the following values: CREATING, READY, and DELETING.
Possible values:

  • CREATING - Resources are being allocated.
  • DELETING - The node template is currently being deleted.
  • INVALID - Invalid status.
  • READY - The node template is ready.

id

Type: STRING
Provider name: id
Description: [Output Only] The unique identifier for the resource. This identifier is defined by the server.

kind

Type: STRING
Provider name: kind
Description: [Output Only] The type of the resource. Always compute#nodeTemplate for node templates.

labels

Type: UNORDERED_LIST_STRING

name

Type: STRING
Provider name: name
Description: The name of the resource, provided by the client when initially creating the resource. The resource name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.

node_type

Type: STRING
Provider name: nodeType
Description: The node type to use for nodes group that are created from this template.

node_type_flexibility

Type: STRUCT
Provider name: nodeTypeFlexibility
Description: Do not use. Instead, use the node_type property.

  • cpus
    Type: STRING
    Provider name: cpus
  • local_ssd
    Type: STRING
    Provider name: localSsd
  • memory
    Type: STRING
    Provider name: memory

organization_id

Type: STRING

parent

Type: STRING

project_id

Type: STRING

project_number

Type: STRING

region

Type: STRING
Provider name: region
Description: [Output Only] The name of the region where the node template resides, such as us-central1.

resource_name

Type: STRING

Type: STRING
Provider name: selfLink
Description: [Output Only] Server-defined URL for the resource.

server_binding

Type: STRUCT
Provider name: serverBinding
Description: Sets the binding properties for the physical server. Valid values include: - [Default] RESTART_NODE_ON_ANY_SERVER: Restarts VMs on any available physical server - RESTART_NODE_ON_MINIMAL_SERVER: Restarts VMs on the same physical server whenever possible See Sole-tenant node options for more information.

  • type
    Type: STRING
    Provider name: type

status_message

Type: STRING
Provider name: statusMessage
Description: [Output Only] An optional, human-readable explanation of the status.

tags

Type: UNORDERED_LIST_STRING

PREVIEWING: guacbot/translation-pipeline