Home | History | Annotate | Download | only in dyn
      1 <html><body>
      2 <style>
      3 
      4 body, h1, h2, h3, div, span, p, pre, a {
      5   margin: 0;
      6   padding: 0;
      7   border: 0;
      8   font-weight: inherit;
      9   font-style: inherit;
     10   font-size: 100%;
     11   font-family: inherit;
     12   vertical-align: baseline;
     13 }
     14 
     15 body {
     16   font-size: 13px;
     17   padding: 1em;
     18 }
     19 
     20 h1 {
     21   font-size: 26px;
     22   margin-bottom: 1em;
     23 }
     24 
     25 h2 {
     26   font-size: 24px;
     27   margin-bottom: 1em;
     28 }
     29 
     30 h3 {
     31   font-size: 20px;
     32   margin-bottom: 1em;
     33   margin-top: 1em;
     34 }
     35 
     36 pre, code {
     37   line-height: 1.5;
     38   font-family: Monaco, 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', monospace;
     39 }
     40 
     41 pre {
     42   margin-top: 0.5em;
     43 }
     44 
     45 h1, h2, h3, p {
     46   font-family: Arial, sans serif;
     47 }
     48 
     49 h1, h2, h3 {
     50   border-bottom: solid #CCC 1px;
     51 }
     52 
     53 .toc_element {
     54   margin-top: 0.5em;
     55 }
     56 
     57 .firstline {
     58   margin-left: 2 em;
     59 }
     60 
     61 .method  {
     62   margin-top: 1em;
     63   border: solid 1px #CCC;
     64   padding: 1em;
     65   background: #EEE;
     66 }
     67 
     68 .details {
     69   font-weight: bold;
     70   font-size: 14px;
     71 }
     72 
     73 </style>
     74 
     75 <h1><a href="dataproc_v1.html">Google Cloud Dataproc API</a> . <a href="dataproc_v1.projects.html">projects</a> . <a href="dataproc_v1.projects.regions.html">regions</a> . <a href="dataproc_v1.projects.regions.clusters.html">clusters</a></h1>
     76 <h2>Instance Methods</h2>
     77 <p class="toc_element">
     78   <code><a href="#create">create(projectId, region, body, x__xgafv=None)</a></code></p>
     79 <p class="firstline">Creates a cluster in a project.</p>
     80 <p class="toc_element">
     81   <code><a href="#delete">delete(projectId, region, clusterName, x__xgafv=None)</a></code></p>
     82 <p class="firstline">Deletes a cluster in a project.</p>
     83 <p class="toc_element">
     84   <code><a href="#diagnose">diagnose(projectId, region, clusterName, body, x__xgafv=None)</a></code></p>
     85 <p class="firstline">Gets cluster diagnostic information. After the operation completes, the Operation.response field contains DiagnoseClusterOutputLocation.</p>
     86 <p class="toc_element">
     87   <code><a href="#get">get(projectId, region, clusterName, x__xgafv=None)</a></code></p>
     88 <p class="firstline">Gets the resource representation for a cluster in a project.</p>
     89 <p class="toc_element">
     90   <code><a href="#list">list(projectId, region, pageSize=None, filter=None, pageToken=None, x__xgafv=None)</a></code></p>
     91 <p class="firstline">Lists all regions/{region}/clusters in a project.</p>
     92 <p class="toc_element">
     93   <code><a href="#list_next">list_next(previous_request, previous_response)</a></code></p>
     94 <p class="firstline">Retrieves the next page of results.</p>
     95 <p class="toc_element">
     96   <code><a href="#patch">patch(projectId, region, clusterName, body, updateMask=None, x__xgafv=None)</a></code></p>
     97 <p class="firstline">Updates a cluster in a project.</p>
     98 <h3>Method Details</h3>
     99 <div class="method">
    100     <code class="details" id="create">create(projectId, region, body, x__xgafv=None)</code>
    101   <pre>Creates a cluster in a project.
    102 
    103 Args:
    104   projectId: string, Required. The ID of the Google Cloud Platform project that the cluster belongs to. (required)
    105   region: string, Required. The Cloud Dataproc region in which to handle the request. (required)
    106   body: object, The request body. (required)
    107     The object takes the form of:
    108 
    109 { # Describes the identifying information, config, and status of a cluster of Google Compute Engine instances.
    110   "status": { # The status of a cluster and its instances. # Output-only. Cluster status.
    111     "state": "A String", # Output-only. The cluster's state.
    112     "stateStartTime": "A String", # Output-only. Time when this state was entered.
    113     "substate": "A String", # Output-only. Additional state information that includes status reported by the agent.
    114     "detail": "A String", # Output-only. Optional details of cluster's state.
    115   },
    116   "clusterUuid": "A String", # Output-only. A cluster UUID (Unique Universal Identifier). Cloud Dataproc generates this value when it creates the cluster.
    117   "clusterName": "A String", # Required. The cluster name. Cluster names within a project must be unique. Names of deleted clusters can be reused.
    118   "projectId": "A String", # Required. The Google Cloud Platform project ID that the cluster belongs to.
    119   "labels": { # Optional. The labels to associate with this cluster. Label keys must contain 1 to 63 characters, and must conform to RFC 1035 (https://www.ietf.org/rfc/rfc1035.txt). Label values may be empty, but, if present, must contain 1 to 63 characters, and must conform to RFC 1035 (https://www.ietf.org/rfc/rfc1035.txt). No more than 32 labels can be associated with a cluster.
    120     "a_key": "A String",
    121   },
    122   "metrics": { # Contains cluster daemon metrics, such as HDFS and YARN stats.Beta Feature: This report is available for testing purposes only. It may be changed before final release. # Contains cluster daemon metrics such as HDFS and YARN stats.Beta Feature: This report is available for testing purposes only. It may be changed before final release.
    123     "yarnMetrics": { # The YARN metrics.
    124       "a_key": "A String",
    125     },
    126     "hdfsMetrics": { # The HDFS metrics.
    127       "a_key": "A String",
    128     },
    129   },
    130   "statusHistory": [ # Output-only. The previous cluster status.
    131     { # The status of a cluster and its instances.
    132       "state": "A String", # Output-only. The cluster's state.
    133       "stateStartTime": "A String", # Output-only. Time when this state was entered.
    134       "substate": "A String", # Output-only. Additional state information that includes status reported by the agent.
    135       "detail": "A String", # Output-only. Optional details of cluster's state.
    136     },
    137   ],
    138   "config": { # The cluster config. # Required. The cluster config. Note that Cloud Dataproc may set default values, and values may change when clusters are updated.
    139     "softwareConfig": { # Specifies the selection and config of software inside the cluster. # Optional. The config settings for software inside the cluster.
    140       "imageVersion": "A String", # Optional. The version of software inside the cluster. It must match the regular expression [0-9]+\.[0-9]+. If unspecified, it defaults to the latest version (see Cloud Dataproc Versioning).
    141       "properties": { # Optional. The properties to set on daemon config files.Property keys are specified in prefix:property format, such as core:fs.defaultFS. The following are supported prefixes and their mappings:
    142           # capacity-scheduler: capacity-scheduler.xml
    143           # core: core-site.xml
    144           # distcp: distcp-default.xml
    145           # hdfs: hdfs-site.xml
    146           # hive: hive-site.xml
    147           # mapred: mapred-site.xml
    148           # pig: pig.properties
    149           # spark: spark-defaults.conf
    150           # yarn: yarn-site.xml
    151         "a_key": "A String",
    152       },
    153     },
    154     "configBucket": "A String", # Optional. A Google Cloud Storage staging bucket used for sharing generated SSH keys and config. If you do not specify a staging bucket, Cloud Dataproc will determine an appropriate Cloud Storage location (US, ASIA, or EU) for your cluster's staging bucket according to the Google Compute Engine zone where your cluster is deployed, and then it will create and manage this project-level, per-location bucket for you.
    155     "gceClusterConfig": { # Common config settings for resources of Google Compute Engine cluster instances, applicable to all instances in the cluster. # Required. The shared Google Compute Engine config settings for all instances in a cluster.
    156       "internalIpOnly": True or False, # Optional. If true, all instances in the cluster will only have internal IP addresses. By default, clusters are not restricted to internal IP addresses, and will have ephemeral external IP addresses assigned to each instance. This internal_ip_only restriction can only be enabled for subnetwork enabled networks, and all off-cluster dependencies must be configured to be accessible without external IP addresses.
    157       "networkUri": "A String", # Optional. The Google Compute Engine network to be used for machine communications. Cannot be specified with subnetwork_uri. If neither network_uri nor subnetwork_uri is specified, the "default" network of the project is used, if it exists. Cannot be a "Custom Subnet Network" (see Using Subnetworks for more information). Example: https://www.googleapis.com/compute/v1/projects/[project_id]/regions/global/default.
    158       "tags": [ # The Google Compute Engine tags to add to all instances (see Tagging instances).
    159         "A String",
    160       ],
    161       "serviceAccount": "A String", # Optional. The service account of the instances. Defaults to the default Google Compute Engine service account. Custom service accounts need permissions equivalent to the folloing IAM roles:
    162           # roles/logging.logWriter
    163           # roles/storage.objectAdmin(see https://cloud.google.com/compute/docs/access/service-accounts#custom_service_accounts for more information). Example: [account_id]@[project_id].iam.gserviceaccount.com
    164       "zoneUri": "A String", # Required. The zone where the Google Compute Engine cluster will be located. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/[zone].
    165       "subnetworkUri": "A String", # Optional. The Google Compute Engine subnetwork to be used for machine communications. Cannot be specified with network_uri. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/regions/us-east1/sub0.
    166       "serviceAccountScopes": [ # Optional. The URIs of service account scopes to be included in Google Compute Engine instances. The following base set of scopes is always included:
    167           # https://www.googleapis.com/auth/cloud.useraccounts.readonly
    168           # https://www.googleapis.com/auth/devstorage.read_write
    169           # https://www.googleapis.com/auth/logging.writeIf no scopes are specified, the following defaults are also provided:
    170           # https://www.googleapis.com/auth/bigquery
    171           # https://www.googleapis.com/auth/bigtable.admin.table
    172           # https://www.googleapis.com/auth/bigtable.data
    173           # https://www.googleapis.com/auth/devstorage.full_control
    174         "A String",
    175       ],
    176       "metadata": { # The Google Compute Engine metadata entries to add to all instances (see Project and instance metadata (https://cloud.google.com/compute/docs/storing-retrieving-metadata#project_and_instance_metadata)).
    177         "a_key": "A String",
    178       },
    179     },
    180     "workerConfig": { # Optional. The config settings for Google Compute Engine resources in an instance group, such as a master or worker group. # Optional. The Google Compute Engine config settings for worker instances in a cluster.
    181       "numInstances": 42, # Required. The number of VM instances in the instance group. For master instance groups, must be set to 1.
    182       "machineTypeUri": "A String", # Required. The Google Compute Engine machine type used for cluster instances. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2.
    183       "instanceNames": [ # Optional. The list of instance names. Cloud Dataproc derives the names from cluster_name, num_instances, and the instance group if not set by user (recommended practice is to let Cloud Dataproc derive the name).
    184         "A String",
    185       ],
    186       "imageUri": "A String", # Output-only. The Google Compute Engine image resource used for cluster instances. Inferred from SoftwareConfig.image_version.
    187       "managedGroupConfig": { # Specifies the resources used to actively manage an instance group. # Output-only. The config for Google Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
    188         "instanceTemplateName": "A String", # Output-only. The name of the Instance Template used for the Managed Instance Group.
    189         "instanceGroupManagerName": "A String", # Output-only. The name of the Instance Group Manager for this group.
    190       },
    191       "accelerators": [ # Optional. The Google Compute Engine accelerator configuration for these instances.Beta Feature: This feature is still under development. It may be changed before final release.
    192         { # Specifies the type and number of accelerator cards attached to the instances of an instance group (see GPUs on Compute Engine).
    193           "acceleratorCount": 42, # The number of the accelerator cards of this type exposed to this instance.
    194           "acceleratorTypeUri": "A String", # Full or partial URI of the accelerator type resource to expose to this instance. See Google Compute Engine AcceleratorTypes( /compute/docs/reference/beta/acceleratorTypes)
    195         },
    196       ],
    197       "isPreemptible": True or False, # Optional. Specifies that this instance group contains preemptible instances.
    198       "diskConfig": { # Specifies the config of disk options for a group of VM instances. # Optional. Disk option config settings.
    199         "numLocalSsds": 42, # Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.
    200         "bootDiskSizeGb": 42, # Optional. Size in GB of the boot disk (default is 500GB).
    201       },
    202     },
    203     "initializationActions": [ # Optional. Commands to execute on each node after config is completed. By default, executables are run on master and all worker nodes. You can test a node's role metadata to run an executable on a master or worker node, as shown below using curl (you can also use wget):
    204         # ROLE=$(curl -H Metadata-Flavor:Google http://metadata/computeMetadata/v1/instance/attributes/dataproc-role)
    205         # if [[ "${ROLE}" == 'Master' ]]; then
    206         #   ... master specific actions ...
    207         # else
    208         #   ... worker specific actions ...
    209         # fi
    210       { # Specifies an executable to run on a fully configured node and a timeout period for executable completion.
    211         "executionTimeout": "A String", # Optional. Amount of time executable has to complete. Default is 10 minutes. Cluster creation fails with an explanatory error message (the name of the executable that caused the error and the exceeded timeout period) if the executable is not completed at end of the timeout period.
    212         "executableFile": "A String", # Required. Google Cloud Storage URI of executable file.
    213       },
    214     ],
    215     "secondaryWorkerConfig": { # Optional. The config settings for Google Compute Engine resources in an instance group, such as a master or worker group. # Optional. The Google Compute Engine config settings for additional worker instances in a cluster.
    216       "numInstances": 42, # Required. The number of VM instances in the instance group. For master instance groups, must be set to 1.
    217       "machineTypeUri": "A String", # Required. The Google Compute Engine machine type used for cluster instances. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2.
    218       "instanceNames": [ # Optional. The list of instance names. Cloud Dataproc derives the names from cluster_name, num_instances, and the instance group if not set by user (recommended practice is to let Cloud Dataproc derive the name).
    219         "A String",
    220       ],
    221       "imageUri": "A String", # Output-only. The Google Compute Engine image resource used for cluster instances. Inferred from SoftwareConfig.image_version.
    222       "managedGroupConfig": { # Specifies the resources used to actively manage an instance group. # Output-only. The config for Google Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
    223         "instanceTemplateName": "A String", # Output-only. The name of the Instance Template used for the Managed Instance Group.
    224         "instanceGroupManagerName": "A String", # Output-only. The name of the Instance Group Manager for this group.
    225       },
    226       "accelerators": [ # Optional. The Google Compute Engine accelerator configuration for these instances.Beta Feature: This feature is still under development. It may be changed before final release.
    227         { # Specifies the type and number of accelerator cards attached to the instances of an instance group (see GPUs on Compute Engine).
    228           "acceleratorCount": 42, # The number of the accelerator cards of this type exposed to this instance.
    229           "acceleratorTypeUri": "A String", # Full or partial URI of the accelerator type resource to expose to this instance. See Google Compute Engine AcceleratorTypes( /compute/docs/reference/beta/acceleratorTypes)
    230         },
    231       ],
    232       "isPreemptible": True or False, # Optional. Specifies that this instance group contains preemptible instances.
    233       "diskConfig": { # Specifies the config of disk options for a group of VM instances. # Optional. Disk option config settings.
    234         "numLocalSsds": 42, # Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.
    235         "bootDiskSizeGb": 42, # Optional. Size in GB of the boot disk (default is 500GB).
    236       },
    237     },
    238     "masterConfig": { # Optional. The config settings for Google Compute Engine resources in an instance group, such as a master or worker group. # Optional. The Google Compute Engine config settings for the master instance in a cluster.
    239       "numInstances": 42, # Required. The number of VM instances in the instance group. For master instance groups, must be set to 1.
    240       "machineTypeUri": "A String", # Required. The Google Compute Engine machine type used for cluster instances. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2.
    241       "instanceNames": [ # Optional. The list of instance names. Cloud Dataproc derives the names from cluster_name, num_instances, and the instance group if not set by user (recommended practice is to let Cloud Dataproc derive the name).
    242         "A String",
    243       ],
    244       "imageUri": "A String", # Output-only. The Google Compute Engine image resource used for cluster instances. Inferred from SoftwareConfig.image_version.
    245       "managedGroupConfig": { # Specifies the resources used to actively manage an instance group. # Output-only. The config for Google Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
    246         "instanceTemplateName": "A String", # Output-only. The name of the Instance Template used for the Managed Instance Group.
    247         "instanceGroupManagerName": "A String", # Output-only. The name of the Instance Group Manager for this group.
    248       },
    249       "accelerators": [ # Optional. The Google Compute Engine accelerator configuration for these instances.Beta Feature: This feature is still under development. It may be changed before final release.
    250         { # Specifies the type and number of accelerator cards attached to the instances of an instance group (see GPUs on Compute Engine).
    251           "acceleratorCount": 42, # The number of the accelerator cards of this type exposed to this instance.
    252           "acceleratorTypeUri": "A String", # Full or partial URI of the accelerator type resource to expose to this instance. See Google Compute Engine AcceleratorTypes( /compute/docs/reference/beta/acceleratorTypes)
    253         },
    254       ],
    255       "isPreemptible": True or False, # Optional. Specifies that this instance group contains preemptible instances.
    256       "diskConfig": { # Specifies the config of disk options for a group of VM instances. # Optional. Disk option config settings.
    257         "numLocalSsds": 42, # Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.
    258         "bootDiskSizeGb": 42, # Optional. Size in GB of the boot disk (default is 500GB).
    259       },
    260     },
    261   },
    262 }
    263 
    264   x__xgafv: string, V1 error format.
    265     Allowed values
    266       1 - v1 error format
    267       2 - v2 error format
    268 
    269 Returns:
    270   An object of the form:
    271 
    272     { # This resource represents a long-running operation that is the result of a network API call.
    273     "metadata": { # Service-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method that returns a long-running operation should document the metadata type, if any.
    274       "a_key": "", # Properties of the object. Contains field @type with type URL.
    275     },
    276     "error": { # The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC (https://github.com/grpc). The error model is designed to be: # The error result of the operation in case of failure or cancellation.
    277         # Simple to use and understand for most users
    278         # Flexible enough to meet unexpected needsOverviewThe Status message contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers understand and resolve the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the package google.rpc that can be used for common error conditions.Language mappingThe Status message is the logical representation of the error model, but it is not necessarily the actual wire format. When the Status message is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C.Other usesThe error model and the Status message can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments.Example uses of this error model include:
    279         # Partial errors. If a service needs to return partial errors to the client, it may embed the Status in the normal response to indicate the partial errors.
    280         # Workflow errors. A typical workflow has multiple steps. Each step may have a Status message for error reporting.
    281         # Batch operations. If a client uses batch request and batch response, the Status message should be used directly inside batch response, one for each error sub-response.
    282         # Asynchronous operations. If an API call embeds asynchronous operation results in its response, the status of those operations should be represented directly using the Status message.
    283         # Logging. If some API errors are stored in logs, the message Status could be used directly after any stripping needed for security/privacy reasons.
    284       "message": "A String", # A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.
    285       "code": 42, # The status code, which should be an enum value of google.rpc.Code.
    286       "details": [ # A list of messages that carry the error details. There will be a common set of message types for APIs to use.
    287         {
    288           "a_key": "", # Properties of the object. Contains field @type with type URL.
    289         },
    290       ],
    291     },
    292     "done": True or False, # If the value is false, it means the operation is still in progress. If true, the operation is completed, and either error or response is available.
    293     "response": { # The normal response of the operation in case of success. If the original method returns no data on success, such as Delete, the response is google.protobuf.Empty. If the original method is standard Get/Create/Update, the response should be the resource. For other methods, the response should have the type XxxResponse, where Xxx is the original method name. For example, if the original method name is TakeSnapshot(), the inferred response type is TakeSnapshotResponse.
    294       "a_key": "", # Properties of the object. Contains field @type with type URL.
    295     },
    296     "name": "A String", # The server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the name should have the format of operations/some/unique/name.
    297   }</pre>
    298 </div>
    299 
    300 <div class="method">
    301     <code class="details" id="delete">delete(projectId, region, clusterName, x__xgafv=None)</code>
    302   <pre>Deletes a cluster in a project.
    303 
    304 Args:
    305   projectId: string, Required. The ID of the Google Cloud Platform project that the cluster belongs to. (required)
    306   region: string, Required. The Cloud Dataproc region in which to handle the request. (required)
    307   clusterName: string, Required. The cluster name. (required)
    308   x__xgafv: string, V1 error format.
    309     Allowed values
    310       1 - v1 error format
    311       2 - v2 error format
    312 
    313 Returns:
    314   An object of the form:
    315 
    316     { # This resource represents a long-running operation that is the result of a network API call.
    317     "metadata": { # Service-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method that returns a long-running operation should document the metadata type, if any.
    318       "a_key": "", # Properties of the object. Contains field @type with type URL.
    319     },
    320     "error": { # The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC (https://github.com/grpc). The error model is designed to be: # The error result of the operation in case of failure or cancellation.
    321         # Simple to use and understand for most users
    322         # Flexible enough to meet unexpected needsOverviewThe Status message contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers understand and resolve the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the package google.rpc that can be used for common error conditions.Language mappingThe Status message is the logical representation of the error model, but it is not necessarily the actual wire format. When the Status message is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C.Other usesThe error model and the Status message can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments.Example uses of this error model include:
    323         # Partial errors. If a service needs to return partial errors to the client, it may embed the Status in the normal response to indicate the partial errors.
    324         # Workflow errors. A typical workflow has multiple steps. Each step may have a Status message for error reporting.
    325         # Batch operations. If a client uses batch request and batch response, the Status message should be used directly inside batch response, one for each error sub-response.
    326         # Asynchronous operations. If an API call embeds asynchronous operation results in its response, the status of those operations should be represented directly using the Status message.
    327         # Logging. If some API errors are stored in logs, the message Status could be used directly after any stripping needed for security/privacy reasons.
    328       "message": "A String", # A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.
    329       "code": 42, # The status code, which should be an enum value of google.rpc.Code.
    330       "details": [ # A list of messages that carry the error details. There will be a common set of message types for APIs to use.
    331         {
    332           "a_key": "", # Properties of the object. Contains field @type with type URL.
    333         },
    334       ],
    335     },
    336     "done": True or False, # If the value is false, it means the operation is still in progress. If true, the operation is completed, and either error or response is available.
    337     "response": { # The normal response of the operation in case of success. If the original method returns no data on success, such as Delete, the response is google.protobuf.Empty. If the original method is standard Get/Create/Update, the response should be the resource. For other methods, the response should have the type XxxResponse, where Xxx is the original method name. For example, if the original method name is TakeSnapshot(), the inferred response type is TakeSnapshotResponse.
    338       "a_key": "", # Properties of the object. Contains field @type with type URL.
    339     },
    340     "name": "A String", # The server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the name should have the format of operations/some/unique/name.
    341   }</pre>
    342 </div>
    343 
    344 <div class="method">
    345     <code class="details" id="diagnose">diagnose(projectId, region, clusterName, body, x__xgafv=None)</code>
    346   <pre>Gets cluster diagnostic information. After the operation completes, the Operation.response field contains DiagnoseClusterOutputLocation.
    347 
    348 Args:
    349   projectId: string, Required. The ID of the Google Cloud Platform project that the cluster belongs to. (required)
    350   region: string, Required. The Cloud Dataproc region in which to handle the request. (required)
    351   clusterName: string, Required. The cluster name. (required)
    352   body: object, The request body. (required)
    353     The object takes the form of:
    354 
    355 { # A request to collect cluster diagnostic information.
    356   }
    357 
    358   x__xgafv: string, V1 error format.
    359     Allowed values
    360       1 - v1 error format
    361       2 - v2 error format
    362 
    363 Returns:
    364   An object of the form:
    365 
    366     { # This resource represents a long-running operation that is the result of a network API call.
    367     "metadata": { # Service-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method that returns a long-running operation should document the metadata type, if any.
    368       "a_key": "", # Properties of the object. Contains field @type with type URL.
    369     },
    370     "error": { # The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC (https://github.com/grpc). The error model is designed to be: # The error result of the operation in case of failure or cancellation.
    371         # Simple to use and understand for most users
    372         # Flexible enough to meet unexpected needsOverviewThe Status message contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers understand and resolve the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the package google.rpc that can be used for common error conditions.Language mappingThe Status message is the logical representation of the error model, but it is not necessarily the actual wire format. When the Status message is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C.Other usesThe error model and the Status message can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments.Example uses of this error model include:
    373         # Partial errors. If a service needs to return partial errors to the client, it may embed the Status in the normal response to indicate the partial errors.
    374         # Workflow errors. A typical workflow has multiple steps. Each step may have a Status message for error reporting.
    375         # Batch operations. If a client uses batch request and batch response, the Status message should be used directly inside batch response, one for each error sub-response.
    376         # Asynchronous operations. If an API call embeds asynchronous operation results in its response, the status of those operations should be represented directly using the Status message.
    377         # Logging. If some API errors are stored in logs, the message Status could be used directly after any stripping needed for security/privacy reasons.
    378       "message": "A String", # A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.
    379       "code": 42, # The status code, which should be an enum value of google.rpc.Code.
    380       "details": [ # A list of messages that carry the error details. There will be a common set of message types for APIs to use.
    381         {
    382           "a_key": "", # Properties of the object. Contains field @type with type URL.
    383         },
    384       ],
    385     },
    386     "done": True or False, # If the value is false, it means the operation is still in progress. If true, the operation is completed, and either error or response is available.
    387     "response": { # The normal response of the operation in case of success. If the original method returns no data on success, such as Delete, the response is google.protobuf.Empty. If the original method is standard Get/Create/Update, the response should be the resource. For other methods, the response should have the type XxxResponse, where Xxx is the original method name. For example, if the original method name is TakeSnapshot(), the inferred response type is TakeSnapshotResponse.
    388       "a_key": "", # Properties of the object. Contains field @type with type URL.
    389     },
    390     "name": "A String", # The server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the name should have the format of operations/some/unique/name.
    391   }</pre>
    392 </div>
    393 
    394 <div class="method">
    395     <code class="details" id="get">get(projectId, region, clusterName, x__xgafv=None)</code>
    396   <pre>Gets the resource representation for a cluster in a project.
    397 
    398 Args:
    399   projectId: string, Required. The ID of the Google Cloud Platform project that the cluster belongs to. (required)
    400   region: string, Required. The Cloud Dataproc region in which to handle the request. (required)
    401   clusterName: string, Required. The cluster name. (required)
    402   x__xgafv: string, V1 error format.
    403     Allowed values
    404       1 - v1 error format
    405       2 - v2 error format
    406 
    407 Returns:
    408   An object of the form:
    409 
    410     { # Describes the identifying information, config, and status of a cluster of Google Compute Engine instances.
    411     "status": { # The status of a cluster and its instances. # Output-only. Cluster status.
    412       "state": "A String", # Output-only. The cluster's state.
    413       "stateStartTime": "A String", # Output-only. Time when this state was entered.
    414       "substate": "A String", # Output-only. Additional state information that includes status reported by the agent.
    415       "detail": "A String", # Output-only. Optional details of cluster's state.
    416     },
    417     "clusterUuid": "A String", # Output-only. A cluster UUID (Unique Universal Identifier). Cloud Dataproc generates this value when it creates the cluster.
    418     "clusterName": "A String", # Required. The cluster name. Cluster names within a project must be unique. Names of deleted clusters can be reused.
    419     "projectId": "A String", # Required. The Google Cloud Platform project ID that the cluster belongs to.
    420     "labels": { # Optional. The labels to associate with this cluster. Label keys must contain 1 to 63 characters, and must conform to RFC 1035 (https://www.ietf.org/rfc/rfc1035.txt). Label values may be empty, but, if present, must contain 1 to 63 characters, and must conform to RFC 1035 (https://www.ietf.org/rfc/rfc1035.txt). No more than 32 labels can be associated with a cluster.
    421       "a_key": "A String",
    422     },
    423     "metrics": { # Contains cluster daemon metrics, such as HDFS and YARN stats.Beta Feature: This report is available for testing purposes only. It may be changed before final release. # Contains cluster daemon metrics such as HDFS and YARN stats.Beta Feature: This report is available for testing purposes only. It may be changed before final release.
    424       "yarnMetrics": { # The YARN metrics.
    425         "a_key": "A String",
    426       },
    427       "hdfsMetrics": { # The HDFS metrics.
    428         "a_key": "A String",
    429       },
    430     },
    431     "statusHistory": [ # Output-only. The previous cluster status.
    432       { # The status of a cluster and its instances.
    433         "state": "A String", # Output-only. The cluster's state.
    434         "stateStartTime": "A String", # Output-only. Time when this state was entered.
    435         "substate": "A String", # Output-only. Additional state information that includes status reported by the agent.
    436         "detail": "A String", # Output-only. Optional details of cluster's state.
    437       },
    438     ],
    439     "config": { # The cluster config. # Required. The cluster config. Note that Cloud Dataproc may set default values, and values may change when clusters are updated.
    440       "softwareConfig": { # Specifies the selection and config of software inside the cluster. # Optional. The config settings for software inside the cluster.
    441         "imageVersion": "A String", # Optional. The version of software inside the cluster. It must match the regular expression [0-9]+\.[0-9]+. If unspecified, it defaults to the latest version (see Cloud Dataproc Versioning).
    442         "properties": { # Optional. The properties to set on daemon config files.Property keys are specified in prefix:property format, such as core:fs.defaultFS. The following are supported prefixes and their mappings:
    443             # capacity-scheduler: capacity-scheduler.xml
    444             # core: core-site.xml
    445             # distcp: distcp-default.xml
    446             # hdfs: hdfs-site.xml
    447             # hive: hive-site.xml
    448             # mapred: mapred-site.xml
    449             # pig: pig.properties
    450             # spark: spark-defaults.conf
    451             # yarn: yarn-site.xml
    452           "a_key": "A String",
    453         },
    454       },
    455       "configBucket": "A String", # Optional. A Google Cloud Storage staging bucket used for sharing generated SSH keys and config. If you do not specify a staging bucket, Cloud Dataproc will determine an appropriate Cloud Storage location (US, ASIA, or EU) for your cluster's staging bucket according to the Google Compute Engine zone where your cluster is deployed, and then it will create and manage this project-level, per-location bucket for you.
    456       "gceClusterConfig": { # Common config settings for resources of Google Compute Engine cluster instances, applicable to all instances in the cluster. # Required. The shared Google Compute Engine config settings for all instances in a cluster.
    457         "internalIpOnly": True or False, # Optional. If true, all instances in the cluster will only have internal IP addresses. By default, clusters are not restricted to internal IP addresses, and will have ephemeral external IP addresses assigned to each instance. This internal_ip_only restriction can only be enabled for subnetwork enabled networks, and all off-cluster dependencies must be configured to be accessible without external IP addresses.
    458         "networkUri": "A String", # Optional. The Google Compute Engine network to be used for machine communications. Cannot be specified with subnetwork_uri. If neither network_uri nor subnetwork_uri is specified, the "default" network of the project is used, if it exists. Cannot be a "Custom Subnet Network" (see Using Subnetworks for more information). Example: https://www.googleapis.com/compute/v1/projects/[project_id]/regions/global/default.
    459         "tags": [ # The Google Compute Engine tags to add to all instances (see Tagging instances).
    460           "A String",
    461         ],
    462         "serviceAccount": "A String", # Optional. The service account of the instances. Defaults to the default Google Compute Engine service account. Custom service accounts need permissions equivalent to the folloing IAM roles:
    463             # roles/logging.logWriter
    464             # roles/storage.objectAdmin(see https://cloud.google.com/compute/docs/access/service-accounts#custom_service_accounts for more information). Example: [account_id]@[project_id].iam.gserviceaccount.com
    465         "zoneUri": "A String", # Required. The zone where the Google Compute Engine cluster will be located. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/[zone].
    466         "subnetworkUri": "A String", # Optional. The Google Compute Engine subnetwork to be used for machine communications. Cannot be specified with network_uri. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/regions/us-east1/sub0.
    467         "serviceAccountScopes": [ # Optional. The URIs of service account scopes to be included in Google Compute Engine instances. The following base set of scopes is always included:
    468             # https://www.googleapis.com/auth/cloud.useraccounts.readonly
    469             # https://www.googleapis.com/auth/devstorage.read_write
    470             # https://www.googleapis.com/auth/logging.writeIf no scopes are specified, the following defaults are also provided:
    471             # https://www.googleapis.com/auth/bigquery
    472             # https://www.googleapis.com/auth/bigtable.admin.table
    473             # https://www.googleapis.com/auth/bigtable.data
    474             # https://www.googleapis.com/auth/devstorage.full_control
    475           "A String",
    476         ],
    477         "metadata": { # The Google Compute Engine metadata entries to add to all instances (see Project and instance metadata (https://cloud.google.com/compute/docs/storing-retrieving-metadata#project_and_instance_metadata)).
    478           "a_key": "A String",
    479         },
    480       },
    481       "workerConfig": { # Optional. The config settings for Google Compute Engine resources in an instance group, such as a master or worker group. # Optional. The Google Compute Engine config settings for worker instances in a cluster.
    482         "numInstances": 42, # Required. The number of VM instances in the instance group. For master instance groups, must be set to 1.
    483         "machineTypeUri": "A String", # Required. The Google Compute Engine machine type used for cluster instances. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2.
    484         "instanceNames": [ # Optional. The list of instance names. Cloud Dataproc derives the names from cluster_name, num_instances, and the instance group if not set by user (recommended practice is to let Cloud Dataproc derive the name).
    485           "A String",
    486         ],
    487         "imageUri": "A String", # Output-only. The Google Compute Engine image resource used for cluster instances. Inferred from SoftwareConfig.image_version.
    488         "managedGroupConfig": { # Specifies the resources used to actively manage an instance group. # Output-only. The config for Google Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
    489           "instanceTemplateName": "A String", # Output-only. The name of the Instance Template used for the Managed Instance Group.
    490           "instanceGroupManagerName": "A String", # Output-only. The name of the Instance Group Manager for this group.
    491         },
    492         "accelerators": [ # Optional. The Google Compute Engine accelerator configuration for these instances.Beta Feature: This feature is still under development. It may be changed before final release.
    493           { # Specifies the type and number of accelerator cards attached to the instances of an instance group (see GPUs on Compute Engine).
    494             "acceleratorCount": 42, # The number of the accelerator cards of this type exposed to this instance.
    495             "acceleratorTypeUri": "A String", # Full or partial URI of the accelerator type resource to expose to this instance. See Google Compute Engine AcceleratorTypes( /compute/docs/reference/beta/acceleratorTypes)
    496           },
    497         ],
    498         "isPreemptible": True or False, # Optional. Specifies that this instance group contains preemptible instances.
    499         "diskConfig": { # Specifies the config of disk options for a group of VM instances. # Optional. Disk option config settings.
    500           "numLocalSsds": 42, # Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.
    501           "bootDiskSizeGb": 42, # Optional. Size in GB of the boot disk (default is 500GB).
    502         },
    503       },
    504       "initializationActions": [ # Optional. Commands to execute on each node after config is completed. By default, executables are run on master and all worker nodes. You can test a node's role metadata to run an executable on a master or worker node, as shown below using curl (you can also use wget):
    505           # ROLE=$(curl -H Metadata-Flavor:Google http://metadata/computeMetadata/v1/instance/attributes/dataproc-role)
    506           # if [[ "${ROLE}" == 'Master' ]]; then
    507           #   ... master specific actions ...
    508           # else
    509           #   ... worker specific actions ...
    510           # fi
    511         { # Specifies an executable to run on a fully configured node and a timeout period for executable completion.
    512           "executionTimeout": "A String", # Optional. Amount of time executable has to complete. Default is 10 minutes. Cluster creation fails with an explanatory error message (the name of the executable that caused the error and the exceeded timeout period) if the executable is not completed at end of the timeout period.
    513           "executableFile": "A String", # Required. Google Cloud Storage URI of executable file.
    514         },
    515       ],
    516       "secondaryWorkerConfig": { # Optional. The config settings for Google Compute Engine resources in an instance group, such as a master or worker group. # Optional. The Google Compute Engine config settings for additional worker instances in a cluster.
    517         "numInstances": 42, # Required. The number of VM instances in the instance group. For master instance groups, must be set to 1.
    518         "machineTypeUri": "A String", # Required. The Google Compute Engine machine type used for cluster instances. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2.
    519         "instanceNames": [ # Optional. The list of instance names. Cloud Dataproc derives the names from cluster_name, num_instances, and the instance group if not set by user (recommended practice is to let Cloud Dataproc derive the name).
    520           "A String",
    521         ],
    522         "imageUri": "A String", # Output-only. The Google Compute Engine image resource used for cluster instances. Inferred from SoftwareConfig.image_version.
    523         "managedGroupConfig": { # Specifies the resources used to actively manage an instance group. # Output-only. The config for Google Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
    524           "instanceTemplateName": "A String", # Output-only. The name of the Instance Template used for the Managed Instance Group.
    525           "instanceGroupManagerName": "A String", # Output-only. The name of the Instance Group Manager for this group.
    526         },
    527         "accelerators": [ # Optional. The Google Compute Engine accelerator configuration for these instances.Beta Feature: This feature is still under development. It may be changed before final release.
    528           { # Specifies the type and number of accelerator cards attached to the instances of an instance group (see GPUs on Compute Engine).
    529             "acceleratorCount": 42, # The number of the accelerator cards of this type exposed to this instance.
    530             "acceleratorTypeUri": "A String", # Full or partial URI of the accelerator type resource to expose to this instance. See Google Compute Engine AcceleratorTypes( /compute/docs/reference/beta/acceleratorTypes)
    531           },
    532         ],
    533         "isPreemptible": True or False, # Optional. Specifies that this instance group contains preemptible instances.
    534         "diskConfig": { # Specifies the config of disk options for a group of VM instances. # Optional. Disk option config settings.
    535           "numLocalSsds": 42, # Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.
    536           "bootDiskSizeGb": 42, # Optional. Size in GB of the boot disk (default is 500GB).
    537         },
    538       },
    539       "masterConfig": { # Optional. The config settings for Google Compute Engine resources in an instance group, such as a master or worker group. # Optional. The Google Compute Engine config settings for the master instance in a cluster.
    540         "numInstances": 42, # Required. The number of VM instances in the instance group. For master instance groups, must be set to 1.
    541         "machineTypeUri": "A String", # Required. The Google Compute Engine machine type used for cluster instances. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2.
    542         "instanceNames": [ # Optional. The list of instance names. Cloud Dataproc derives the names from cluster_name, num_instances, and the instance group if not set by user (recommended practice is to let Cloud Dataproc derive the name).
    543           "A String",
    544         ],
    545         "imageUri": "A String", # Output-only. The Google Compute Engine image resource used for cluster instances. Inferred from SoftwareConfig.image_version.
    546         "managedGroupConfig": { # Specifies the resources used to actively manage an instance group. # Output-only. The config for Google Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
    547           "instanceTemplateName": "A String", # Output-only. The name of the Instance Template used for the Managed Instance Group.
    548           "instanceGroupManagerName": "A String", # Output-only. The name of the Instance Group Manager for this group.
    549         },
    550         "accelerators": [ # Optional. The Google Compute Engine accelerator configuration for these instances.Beta Feature: This feature is still under development. It may be changed before final release.
    551           { # Specifies the type and number of accelerator cards attached to the instances of an instance group (see GPUs on Compute Engine).
    552             "acceleratorCount": 42, # The number of the accelerator cards of this type exposed to this instance.
    553             "acceleratorTypeUri": "A String", # Full or partial URI of the accelerator type resource to expose to this instance. See Google Compute Engine AcceleratorTypes( /compute/docs/reference/beta/acceleratorTypes)
    554           },
    555         ],
    556         "isPreemptible": True or False, # Optional. Specifies that this instance group contains preemptible instances.
    557         "diskConfig": { # Specifies the config of disk options for a group of VM instances. # Optional. Disk option config settings.
    558           "numLocalSsds": 42, # Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.
    559           "bootDiskSizeGb": 42, # Optional. Size in GB of the boot disk (default is 500GB).
    560         },
    561       },
    562     },
    563   }</pre>
    564 </div>
    565 
    566 <div class="method">
    567     <code class="details" id="list">list(projectId, region, pageSize=None, filter=None, pageToken=None, x__xgafv=None)</code>
    568   <pre>Lists all regions/{region}/clusters in a project.
    569 
    570 Args:
    571   projectId: string, Required. The ID of the Google Cloud Platform project that the cluster belongs to. (required)
    572   region: string, Required. The Cloud Dataproc region in which to handle the request. (required)
    573   pageSize: integer, Optional. The standard List page size.
    574   filter: string, Optional. A filter constraining the clusters to list. Filters are case-sensitive and have the following syntax:field = value AND field = value ...where field is one of status.state, clusterName, or labels.[KEY], and [KEY] is a label key. value can be * to match all values. status.state can be one of the following: ACTIVE, INACTIVE, CREATING, RUNNING, ERROR, DELETING, or UPDATING. ACTIVE contains the CREATING, UPDATING, and RUNNING states. INACTIVE contains the DELETING and ERROR states. clusterName is the name of the cluster provided at creation time. Only the logical AND operator is supported; space-separated items are treated as having an implicit AND operator.Example filter:status.state = ACTIVE AND clusterName = mycluster AND labels.env = staging AND labels.starred = *
    575   pageToken: string, Optional. The standard List page token.
    576   x__xgafv: string, V1 error format.
    577     Allowed values
    578       1 - v1 error format
    579       2 - v2 error format
    580 
    581 Returns:
    582   An object of the form:
    583 
    584     { # The list of all clusters in a project.
    585     "nextPageToken": "A String", # Output-only. This token is included in the response if there are more results to fetch. To fetch additional results, provide this value as the page_token in a subsequent ListClustersRequest.
    586     "clusters": [ # Output-only. The clusters in the project.
    587       { # Describes the identifying information, config, and status of a cluster of Google Compute Engine instances.
    588         "status": { # The status of a cluster and its instances. # Output-only. Cluster status.
    589           "state": "A String", # Output-only. The cluster's state.
    590           "stateStartTime": "A String", # Output-only. Time when this state was entered.
    591           "substate": "A String", # Output-only. Additional state information that includes status reported by the agent.
    592           "detail": "A String", # Output-only. Optional details of cluster's state.
    593         },
    594         "clusterUuid": "A String", # Output-only. A cluster UUID (Unique Universal Identifier). Cloud Dataproc generates this value when it creates the cluster.
    595         "clusterName": "A String", # Required. The cluster name. Cluster names within a project must be unique. Names of deleted clusters can be reused.
    596         "projectId": "A String", # Required. The Google Cloud Platform project ID that the cluster belongs to.
    597         "labels": { # Optional. The labels to associate with this cluster. Label keys must contain 1 to 63 characters, and must conform to RFC 1035 (https://www.ietf.org/rfc/rfc1035.txt). Label values may be empty, but, if present, must contain 1 to 63 characters, and must conform to RFC 1035 (https://www.ietf.org/rfc/rfc1035.txt). No more than 32 labels can be associated with a cluster.
    598           "a_key": "A String",
    599         },
    600         "metrics": { # Contains cluster daemon metrics, such as HDFS and YARN stats.Beta Feature: This report is available for testing purposes only. It may be changed before final release. # Contains cluster daemon metrics such as HDFS and YARN stats.Beta Feature: This report is available for testing purposes only. It may be changed before final release.
    601           "yarnMetrics": { # The YARN metrics.
    602             "a_key": "A String",
    603           },
    604           "hdfsMetrics": { # The HDFS metrics.
    605             "a_key": "A String",
    606           },
    607         },
    608         "statusHistory": [ # Output-only. The previous cluster status.
    609           { # The status of a cluster and its instances.
    610             "state": "A String", # Output-only. The cluster's state.
    611             "stateStartTime": "A String", # Output-only. Time when this state was entered.
    612             "substate": "A String", # Output-only. Additional state information that includes status reported by the agent.
    613             "detail": "A String", # Output-only. Optional details of cluster's state.
    614           },
    615         ],
    616         "config": { # The cluster config. # Required. The cluster config. Note that Cloud Dataproc may set default values, and values may change when clusters are updated.
    617           "softwareConfig": { # Specifies the selection and config of software inside the cluster. # Optional. The config settings for software inside the cluster.
    618             "imageVersion": "A String", # Optional. The version of software inside the cluster. It must match the regular expression [0-9]+\.[0-9]+. If unspecified, it defaults to the latest version (see Cloud Dataproc Versioning).
    619             "properties": { # Optional. The properties to set on daemon config files.Property keys are specified in prefix:property format, such as core:fs.defaultFS. The following are supported prefixes and their mappings:
    620                 # capacity-scheduler: capacity-scheduler.xml
    621                 # core: core-site.xml
    622                 # distcp: distcp-default.xml
    623                 # hdfs: hdfs-site.xml
    624                 # hive: hive-site.xml
    625                 # mapred: mapred-site.xml
    626                 # pig: pig.properties
    627                 # spark: spark-defaults.conf
    628                 # yarn: yarn-site.xml
    629               "a_key": "A String",
    630             },
    631           },
    632           "configBucket": "A String", # Optional. A Google Cloud Storage staging bucket used for sharing generated SSH keys and config. If you do not specify a staging bucket, Cloud Dataproc will determine an appropriate Cloud Storage location (US, ASIA, or EU) for your cluster's staging bucket according to the Google Compute Engine zone where your cluster is deployed, and then it will create and manage this project-level, per-location bucket for you.
    633           "gceClusterConfig": { # Common config settings for resources of Google Compute Engine cluster instances, applicable to all instances in the cluster. # Required. The shared Google Compute Engine config settings for all instances in a cluster.
    634             "internalIpOnly": True or False, # Optional. If true, all instances in the cluster will only have internal IP addresses. By default, clusters are not restricted to internal IP addresses, and will have ephemeral external IP addresses assigned to each instance. This internal_ip_only restriction can only be enabled for subnetwork enabled networks, and all off-cluster dependencies must be configured to be accessible without external IP addresses.
    635             "networkUri": "A String", # Optional. The Google Compute Engine network to be used for machine communications. Cannot be specified with subnetwork_uri. If neither network_uri nor subnetwork_uri is specified, the "default" network of the project is used, if it exists. Cannot be a "Custom Subnet Network" (see Using Subnetworks for more information). Example: https://www.googleapis.com/compute/v1/projects/[project_id]/regions/global/default.
    636             "tags": [ # The Google Compute Engine tags to add to all instances (see Tagging instances).
    637               "A String",
    638             ],
    639             "serviceAccount": "A String", # Optional. The service account of the instances. Defaults to the default Google Compute Engine service account. Custom service accounts need permissions equivalent to the folloing IAM roles:
    640                 # roles/logging.logWriter
    641                 # roles/storage.objectAdmin(see https://cloud.google.com/compute/docs/access/service-accounts#custom_service_accounts for more information). Example: [account_id]@[project_id].iam.gserviceaccount.com
    642             "zoneUri": "A String", # Required. The zone where the Google Compute Engine cluster will be located. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/[zone].
    643             "subnetworkUri": "A String", # Optional. The Google Compute Engine subnetwork to be used for machine communications. Cannot be specified with network_uri. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/regions/us-east1/sub0.
    644             "serviceAccountScopes": [ # Optional. The URIs of service account scopes to be included in Google Compute Engine instances. The following base set of scopes is always included:
    645                 # https://www.googleapis.com/auth/cloud.useraccounts.readonly
    646                 # https://www.googleapis.com/auth/devstorage.read_write
    647                 # https://www.googleapis.com/auth/logging.writeIf no scopes are specified, the following defaults are also provided:
    648                 # https://www.googleapis.com/auth/bigquery
    649                 # https://www.googleapis.com/auth/bigtable.admin.table
    650                 # https://www.googleapis.com/auth/bigtable.data
    651                 # https://www.googleapis.com/auth/devstorage.full_control
    652               "A String",
    653             ],
    654             "metadata": { # The Google Compute Engine metadata entries to add to all instances (see Project and instance metadata (https://cloud.google.com/compute/docs/storing-retrieving-metadata#project_and_instance_metadata)).
    655               "a_key": "A String",
    656             },
    657           },
    658           "workerConfig": { # Optional. The config settings for Google Compute Engine resources in an instance group, such as a master or worker group. # Optional. The Google Compute Engine config settings for worker instances in a cluster.
    659             "numInstances": 42, # Required. The number of VM instances in the instance group. For master instance groups, must be set to 1.
    660             "machineTypeUri": "A String", # Required. The Google Compute Engine machine type used for cluster instances. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2.
    661             "instanceNames": [ # Optional. The list of instance names. Cloud Dataproc derives the names from cluster_name, num_instances, and the instance group if not set by user (recommended practice is to let Cloud Dataproc derive the name).
    662               "A String",
    663             ],
    664             "imageUri": "A String", # Output-only. The Google Compute Engine image resource used for cluster instances. Inferred from SoftwareConfig.image_version.
    665             "managedGroupConfig": { # Specifies the resources used to actively manage an instance group. # Output-only. The config for Google Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
    666               "instanceTemplateName": "A String", # Output-only. The name of the Instance Template used for the Managed Instance Group.
    667               "instanceGroupManagerName": "A String", # Output-only. The name of the Instance Group Manager for this group.
    668             },
    669             "accelerators": [ # Optional. The Google Compute Engine accelerator configuration for these instances.Beta Feature: This feature is still under development. It may be changed before final release.
    670               { # Specifies the type and number of accelerator cards attached to the instances of an instance group (see GPUs on Compute Engine).
    671                 "acceleratorCount": 42, # The number of the accelerator cards of this type exposed to this instance.
    672                 "acceleratorTypeUri": "A String", # Full or partial URI of the accelerator type resource to expose to this instance. See Google Compute Engine AcceleratorTypes( /compute/docs/reference/beta/acceleratorTypes)
    673               },
    674             ],
    675             "isPreemptible": True or False, # Optional. Specifies that this instance group contains preemptible instances.
    676             "diskConfig": { # Specifies the config of disk options for a group of VM instances. # Optional. Disk option config settings.
    677               "numLocalSsds": 42, # Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.
    678               "bootDiskSizeGb": 42, # Optional. Size in GB of the boot disk (default is 500GB).
    679             },
    680           },
    681           "initializationActions": [ # Optional. Commands to execute on each node after config is completed. By default, executables are run on master and all worker nodes. You can test a node's role metadata to run an executable on a master or worker node, as shown below using curl (you can also use wget):
    682               # ROLE=$(curl -H Metadata-Flavor:Google http://metadata/computeMetadata/v1/instance/attributes/dataproc-role)
    683               # if [[ "${ROLE}" == 'Master' ]]; then
    684               #   ... master specific actions ...
    685               # else
    686               #   ... worker specific actions ...
    687               # fi
    688             { # Specifies an executable to run on a fully configured node and a timeout period for executable completion.
    689               "executionTimeout": "A String", # Optional. Amount of time executable has to complete. Default is 10 minutes. Cluster creation fails with an explanatory error message (the name of the executable that caused the error and the exceeded timeout period) if the executable is not completed at end of the timeout period.
    690               "executableFile": "A String", # Required. Google Cloud Storage URI of executable file.
    691             },
    692           ],
    693           "secondaryWorkerConfig": { # Optional. The config settings for Google Compute Engine resources in an instance group, such as a master or worker group. # Optional. The Google Compute Engine config settings for additional worker instances in a cluster.
    694             "numInstances": 42, # Required. The number of VM instances in the instance group. For master instance groups, must be set to 1.
    695             "machineTypeUri": "A String", # Required. The Google Compute Engine machine type used for cluster instances. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2.
    696             "instanceNames": [ # Optional. The list of instance names. Cloud Dataproc derives the names from cluster_name, num_instances, and the instance group if not set by user (recommended practice is to let Cloud Dataproc derive the name).
    697               "A String",
    698             ],
    699             "imageUri": "A String", # Output-only. The Google Compute Engine image resource used for cluster instances. Inferred from SoftwareConfig.image_version.
    700             "managedGroupConfig": { # Specifies the resources used to actively manage an instance group. # Output-only. The config for Google Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
    701               "instanceTemplateName": "A String", # Output-only. The name of the Instance Template used for the Managed Instance Group.
    702               "instanceGroupManagerName": "A String", # Output-only. The name of the Instance Group Manager for this group.
    703             },
    704             "accelerators": [ # Optional. The Google Compute Engine accelerator configuration for these instances.Beta Feature: This feature is still under development. It may be changed before final release.
    705               { # Specifies the type and number of accelerator cards attached to the instances of an instance group (see GPUs on Compute Engine).
    706                 "acceleratorCount": 42, # The number of the accelerator cards of this type exposed to this instance.
    707                 "acceleratorTypeUri": "A String", # Full or partial URI of the accelerator type resource to expose to this instance. See Google Compute Engine AcceleratorTypes( /compute/docs/reference/beta/acceleratorTypes)
    708               },
    709             ],
    710             "isPreemptible": True or False, # Optional. Specifies that this instance group contains preemptible instances.
    711             "diskConfig": { # Specifies the config of disk options for a group of VM instances. # Optional. Disk option config settings.
    712               "numLocalSsds": 42, # Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.
    713               "bootDiskSizeGb": 42, # Optional. Size in GB of the boot disk (default is 500GB).
    714             },
    715           },
    716           "masterConfig": { # Optional. The config settings for Google Compute Engine resources in an instance group, such as a master or worker group. # Optional. The Google Compute Engine config settings for the master instance in a cluster.
    717             "numInstances": 42, # Required. The number of VM instances in the instance group. For master instance groups, must be set to 1.
    718             "machineTypeUri": "A String", # Required. The Google Compute Engine machine type used for cluster instances. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2.
    719             "instanceNames": [ # Optional. The list of instance names. Cloud Dataproc derives the names from cluster_name, num_instances, and the instance group if not set by user (recommended practice is to let Cloud Dataproc derive the name).
    720               "A String",
    721             ],
    722             "imageUri": "A String", # Output-only. The Google Compute Engine image resource used for cluster instances. Inferred from SoftwareConfig.image_version.
    723             "managedGroupConfig": { # Specifies the resources used to actively manage an instance group. # Output-only. The config for Google Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
    724               "instanceTemplateName": "A String", # Output-only. The name of the Instance Template used for the Managed Instance Group.
    725               "instanceGroupManagerName": "A String", # Output-only. The name of the Instance Group Manager for this group.
    726             },
    727             "accelerators": [ # Optional. The Google Compute Engine accelerator configuration for these instances.Beta Feature: This feature is still under development. It may be changed before final release.
    728               { # Specifies the type and number of accelerator cards attached to the instances of an instance group (see GPUs on Compute Engine).
    729                 "acceleratorCount": 42, # The number of the accelerator cards of this type exposed to this instance.
    730                 "acceleratorTypeUri": "A String", # Full or partial URI of the accelerator type resource to expose to this instance. See Google Compute Engine AcceleratorTypes( /compute/docs/reference/beta/acceleratorTypes)
    731               },
    732             ],
    733             "isPreemptible": True or False, # Optional. Specifies that this instance group contains preemptible instances.
    734             "diskConfig": { # Specifies the config of disk options for a group of VM instances. # Optional. Disk option config settings.
    735               "numLocalSsds": 42, # Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.
    736               "bootDiskSizeGb": 42, # Optional. Size in GB of the boot disk (default is 500GB).
    737             },
    738           },
    739         },
    740       },
    741     ],
    742   }</pre>
    743 </div>
    744 
    745 <div class="method">
    746     <code class="details" id="list_next">list_next(previous_request, previous_response)</code>
    747   <pre>Retrieves the next page of results.
    748 
    749 Args:
    750   previous_request: The request for the previous page. (required)
    751   previous_response: The response from the request for the previous page. (required)
    752 
    753 Returns:
    754   A request object that you can call 'execute()' on to request the next
    755   page. Returns None if there are no more items in the collection.
    756     </pre>
    757 </div>
    758 
    759 <div class="method">
    760     <code class="details" id="patch">patch(projectId, region, clusterName, body, updateMask=None, x__xgafv=None)</code>
    761   <pre>Updates a cluster in a project.
    762 
    763 Args:
    764   projectId: string, Required. The ID of the Google Cloud Platform project the cluster belongs to. (required)
    765   region: string, Required. The Cloud Dataproc region in which to handle the request. (required)
    766   clusterName: string, Required. The cluster name. (required)
    767   body: object, The request body. (required)
    768     The object takes the form of:
    769 
    770 { # Describes the identifying information, config, and status of a cluster of Google Compute Engine instances.
    771   "status": { # The status of a cluster and its instances. # Output-only. Cluster status.
    772     "state": "A String", # Output-only. The cluster's state.
    773     "stateStartTime": "A String", # Output-only. Time when this state was entered.
    774     "substate": "A String", # Output-only. Additional state information that includes status reported by the agent.
    775     "detail": "A String", # Output-only. Optional details of cluster's state.
    776   },
    777   "clusterUuid": "A String", # Output-only. A cluster UUID (Unique Universal Identifier). Cloud Dataproc generates this value when it creates the cluster.
    778   "clusterName": "A String", # Required. The cluster name. Cluster names within a project must be unique. Names of deleted clusters can be reused.
    779   "projectId": "A String", # Required. The Google Cloud Platform project ID that the cluster belongs to.
    780   "labels": { # Optional. The labels to associate with this cluster. Label keys must contain 1 to 63 characters, and must conform to RFC 1035 (https://www.ietf.org/rfc/rfc1035.txt). Label values may be empty, but, if present, must contain 1 to 63 characters, and must conform to RFC 1035 (https://www.ietf.org/rfc/rfc1035.txt). No more than 32 labels can be associated with a cluster.
    781     "a_key": "A String",
    782   },
    783   "metrics": { # Contains cluster daemon metrics, such as HDFS and YARN stats.Beta Feature: This report is available for testing purposes only. It may be changed before final release. # Contains cluster daemon metrics such as HDFS and YARN stats.Beta Feature: This report is available for testing purposes only. It may be changed before final release.
    784     "yarnMetrics": { # The YARN metrics.
    785       "a_key": "A String",
    786     },
    787     "hdfsMetrics": { # The HDFS metrics.
    788       "a_key": "A String",
    789     },
    790   },
    791   "statusHistory": [ # Output-only. The previous cluster status.
    792     { # The status of a cluster and its instances.
    793       "state": "A String", # Output-only. The cluster's state.
    794       "stateStartTime": "A String", # Output-only. Time when this state was entered.
    795       "substate": "A String", # Output-only. Additional state information that includes status reported by the agent.
    796       "detail": "A String", # Output-only. Optional details of cluster's state.
    797     },
    798   ],
    799   "config": { # The cluster config. # Required. The cluster config. Note that Cloud Dataproc may set default values, and values may change when clusters are updated.
    800     "softwareConfig": { # Specifies the selection and config of software inside the cluster. # Optional. The config settings for software inside the cluster.
    801       "imageVersion": "A String", # Optional. The version of software inside the cluster. It must match the regular expression [0-9]+\.[0-9]+. If unspecified, it defaults to the latest version (see Cloud Dataproc Versioning).
    802       "properties": { # Optional. The properties to set on daemon config files.Property keys are specified in prefix:property format, such as core:fs.defaultFS. The following are supported prefixes and their mappings:
    803           # capacity-scheduler: capacity-scheduler.xml
    804           # core: core-site.xml
    805           # distcp: distcp-default.xml
    806           # hdfs: hdfs-site.xml
    807           # hive: hive-site.xml
    808           # mapred: mapred-site.xml
    809           # pig: pig.properties
    810           # spark: spark-defaults.conf
    811           # yarn: yarn-site.xml
    812         "a_key": "A String",
    813       },
    814     },
    815     "configBucket": "A String", # Optional. A Google Cloud Storage staging bucket used for sharing generated SSH keys and config. If you do not specify a staging bucket, Cloud Dataproc will determine an appropriate Cloud Storage location (US, ASIA, or EU) for your cluster's staging bucket according to the Google Compute Engine zone where your cluster is deployed, and then it will create and manage this project-level, per-location bucket for you.
    816     "gceClusterConfig": { # Common config settings for resources of Google Compute Engine cluster instances, applicable to all instances in the cluster. # Required. The shared Google Compute Engine config settings for all instances in a cluster.
    817       "internalIpOnly": True or False, # Optional. If true, all instances in the cluster will only have internal IP addresses. By default, clusters are not restricted to internal IP addresses, and will have ephemeral external IP addresses assigned to each instance. This internal_ip_only restriction can only be enabled for subnetwork enabled networks, and all off-cluster dependencies must be configured to be accessible without external IP addresses.
    818       "networkUri": "A String", # Optional. The Google Compute Engine network to be used for machine communications. Cannot be specified with subnetwork_uri. If neither network_uri nor subnetwork_uri is specified, the "default" network of the project is used, if it exists. Cannot be a "Custom Subnet Network" (see Using Subnetworks for more information). Example: https://www.googleapis.com/compute/v1/projects/[project_id]/regions/global/default.
    819       "tags": [ # The Google Compute Engine tags to add to all instances (see Tagging instances).
    820         "A String",
    821       ],
    822       "serviceAccount": "A String", # Optional. The service account of the instances. Defaults to the default Google Compute Engine service account. Custom service accounts need permissions equivalent to the folloing IAM roles:
    823           # roles/logging.logWriter
    824           # roles/storage.objectAdmin(see https://cloud.google.com/compute/docs/access/service-accounts#custom_service_accounts for more information). Example: [account_id]@[project_id].iam.gserviceaccount.com
    825       "zoneUri": "A String", # Required. The zone where the Google Compute Engine cluster will be located. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/[zone].
    826       "subnetworkUri": "A String", # Optional. The Google Compute Engine subnetwork to be used for machine communications. Cannot be specified with network_uri. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/regions/us-east1/sub0.
    827       "serviceAccountScopes": [ # Optional. The URIs of service account scopes to be included in Google Compute Engine instances. The following base set of scopes is always included:
    828           # https://www.googleapis.com/auth/cloud.useraccounts.readonly
    829           # https://www.googleapis.com/auth/devstorage.read_write
    830           # https://www.googleapis.com/auth/logging.writeIf no scopes are specified, the following defaults are also provided:
    831           # https://www.googleapis.com/auth/bigquery
    832           # https://www.googleapis.com/auth/bigtable.admin.table
    833           # https://www.googleapis.com/auth/bigtable.data
    834           # https://www.googleapis.com/auth/devstorage.full_control
    835         "A String",
    836       ],
    837       "metadata": { # The Google Compute Engine metadata entries to add to all instances (see Project and instance metadata (https://cloud.google.com/compute/docs/storing-retrieving-metadata#project_and_instance_metadata)).
    838         "a_key": "A String",
    839       },
    840     },
    841     "workerConfig": { # Optional. The config settings for Google Compute Engine resources in an instance group, such as a master or worker group. # Optional. The Google Compute Engine config settings for worker instances in a cluster.
    842       "numInstances": 42, # Required. The number of VM instances in the instance group. For master instance groups, must be set to 1.
    843       "machineTypeUri": "A String", # Required. The Google Compute Engine machine type used for cluster instances. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2.
    844       "instanceNames": [ # Optional. The list of instance names. Cloud Dataproc derives the names from cluster_name, num_instances, and the instance group if not set by user (recommended practice is to let Cloud Dataproc derive the name).
    845         "A String",
    846       ],
    847       "imageUri": "A String", # Output-only. The Google Compute Engine image resource used for cluster instances. Inferred from SoftwareConfig.image_version.
    848       "managedGroupConfig": { # Specifies the resources used to actively manage an instance group. # Output-only. The config for Google Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
    849         "instanceTemplateName": "A String", # Output-only. The name of the Instance Template used for the Managed Instance Group.
    850         "instanceGroupManagerName": "A String", # Output-only. The name of the Instance Group Manager for this group.
    851       },
    852       "accelerators": [ # Optional. The Google Compute Engine accelerator configuration for these instances.Beta Feature: This feature is still under development. It may be changed before final release.
    853         { # Specifies the type and number of accelerator cards attached to the instances of an instance group (see GPUs on Compute Engine).
    854           "acceleratorCount": 42, # The number of the accelerator cards of this type exposed to this instance.
    855           "acceleratorTypeUri": "A String", # Full or partial URI of the accelerator type resource to expose to this instance. See Google Compute Engine AcceleratorTypes( /compute/docs/reference/beta/acceleratorTypes)
    856         },
    857       ],
    858       "isPreemptible": True or False, # Optional. Specifies that this instance group contains preemptible instances.
    859       "diskConfig": { # Specifies the config of disk options for a group of VM instances. # Optional. Disk option config settings.
    860         "numLocalSsds": 42, # Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.
    861         "bootDiskSizeGb": 42, # Optional. Size in GB of the boot disk (default is 500GB).
    862       },
    863     },
    864     "initializationActions": [ # Optional. Commands to execute on each node after config is completed. By default, executables are run on master and all worker nodes. You can test a node's role metadata to run an executable on a master or worker node, as shown below using curl (you can also use wget):
    865         # ROLE=$(curl -H Metadata-Flavor:Google http://metadata/computeMetadata/v1/instance/attributes/dataproc-role)
    866         # if [[ "${ROLE}" == 'Master' ]]; then
    867         #   ... master specific actions ...
    868         # else
    869         #   ... worker specific actions ...
    870         # fi
    871       { # Specifies an executable to run on a fully configured node and a timeout period for executable completion.
    872         "executionTimeout": "A String", # Optional. Amount of time executable has to complete. Default is 10 minutes. Cluster creation fails with an explanatory error message (the name of the executable that caused the error and the exceeded timeout period) if the executable is not completed at end of the timeout period.
    873         "executableFile": "A String", # Required. Google Cloud Storage URI of executable file.
    874       },
    875     ],
    876     "secondaryWorkerConfig": { # Optional. The config settings for Google Compute Engine resources in an instance group, such as a master or worker group. # Optional. The Google Compute Engine config settings for additional worker instances in a cluster.
    877       "numInstances": 42, # Required. The number of VM instances in the instance group. For master instance groups, must be set to 1.
    878       "machineTypeUri": "A String", # Required. The Google Compute Engine machine type used for cluster instances. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2.
    879       "instanceNames": [ # Optional. The list of instance names. Cloud Dataproc derives the names from cluster_name, num_instances, and the instance group if not set by user (recommended practice is to let Cloud Dataproc derive the name).
    880         "A String",
    881       ],
    882       "imageUri": "A String", # Output-only. The Google Compute Engine image resource used for cluster instances. Inferred from SoftwareConfig.image_version.
    883       "managedGroupConfig": { # Specifies the resources used to actively manage an instance group. # Output-only. The config for Google Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
    884         "instanceTemplateName": "A String", # Output-only. The name of the Instance Template used for the Managed Instance Group.
    885         "instanceGroupManagerName": "A String", # Output-only. The name of the Instance Group Manager for this group.
    886       },
    887       "accelerators": [ # Optional. The Google Compute Engine accelerator configuration for these instances.Beta Feature: This feature is still under development. It may be changed before final release.
    888         { # Specifies the type and number of accelerator cards attached to the instances of an instance group (see GPUs on Compute Engine).
    889           "acceleratorCount": 42, # The number of the accelerator cards of this type exposed to this instance.
    890           "acceleratorTypeUri": "A String", # Full or partial URI of the accelerator type resource to expose to this instance. See Google Compute Engine AcceleratorTypes( /compute/docs/reference/beta/acceleratorTypes)
    891         },
    892       ],
    893       "isPreemptible": True or False, # Optional. Specifies that this instance group contains preemptible instances.
    894       "diskConfig": { # Specifies the config of disk options for a group of VM instances. # Optional. Disk option config settings.
    895         "numLocalSsds": 42, # Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.
    896         "bootDiskSizeGb": 42, # Optional. Size in GB of the boot disk (default is 500GB).
    897       },
    898     },
    899     "masterConfig": { # Optional. The config settings for Google Compute Engine resources in an instance group, such as a master or worker group. # Optional. The Google Compute Engine config settings for the master instance in a cluster.
    900       "numInstances": 42, # Required. The number of VM instances in the instance group. For master instance groups, must be set to 1.
    901       "machineTypeUri": "A String", # Required. The Google Compute Engine machine type used for cluster instances. Example: https://www.googleapis.com/compute/v1/projects/[project_id]/zones/us-east1-a/machineTypes/n1-standard-2.
    902       "instanceNames": [ # Optional. The list of instance names. Cloud Dataproc derives the names from cluster_name, num_instances, and the instance group if not set by user (recommended practice is to let Cloud Dataproc derive the name).
    903         "A String",
    904       ],
    905       "imageUri": "A String", # Output-only. The Google Compute Engine image resource used for cluster instances. Inferred from SoftwareConfig.image_version.
    906       "managedGroupConfig": { # Specifies the resources used to actively manage an instance group. # Output-only. The config for Google Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
    907         "instanceTemplateName": "A String", # Output-only. The name of the Instance Template used for the Managed Instance Group.
    908         "instanceGroupManagerName": "A String", # Output-only. The name of the Instance Group Manager for this group.
    909       },
    910       "accelerators": [ # Optional. The Google Compute Engine accelerator configuration for these instances.Beta Feature: This feature is still under development. It may be changed before final release.
    911         { # Specifies the type and number of accelerator cards attached to the instances of an instance group (see GPUs on Compute Engine).
    912           "acceleratorCount": 42, # The number of the accelerator cards of this type exposed to this instance.
    913           "acceleratorTypeUri": "A String", # Full or partial URI of the accelerator type resource to expose to this instance. See Google Compute Engine AcceleratorTypes( /compute/docs/reference/beta/acceleratorTypes)
    914         },
    915       ],
    916       "isPreemptible": True or False, # Optional. Specifies that this instance group contains preemptible instances.
    917       "diskConfig": { # Specifies the config of disk options for a group of VM instances. # Optional. Disk option config settings.
    918         "numLocalSsds": 42, # Optional. Number of attached SSDs, from 0 to 4 (default is 0). If SSDs are not attached, the boot disk is used to store runtime logs and HDFS (https://hadoop.apache.org/docs/r1.2.1/hdfs_user_guide.html) data. If one or more SSDs are attached, this runtime bulk data is spread across them, and the boot disk contains only basic config and installed binaries.
    919         "bootDiskSizeGb": 42, # Optional. Size in GB of the boot disk (default is 500GB).
    920       },
    921     },
    922   },
    923 }
    924 
    925   updateMask: string, Required. Specifies the path, relative to Cluster, of the field to update. For example, to change the number of workers in a cluster to 5, the update_mask parameter would be specified as config.worker_config.num_instances, and the PATCH request body would specify the new value, as follows:
    926 {
    927   "config":{
    928     "workerConfig":{
    929       "numInstances":"5"
    930     }
    931   }
    932 }
    933 Similarly, to change the number of preemptible workers in a cluster to 5, the update_mask parameter would be config.secondary_worker_config.num_instances, and the PATCH request body would be set as follows:
    934 {
    935   "config":{
    936     "secondaryWorkerConfig":{
    937       "numInstances":"5"
    938     }
    939   }
    940 }
    941 <strong>Note:</strong> Currently, only the following fields can be updated:<table>  <tbody>  <tr>  <td><strong>Mask</strong></td>  <td><strong>Purpose</strong></td>  </tr>  <tr>  <td><strong><em>labels</em></strong></td>  <td>Update labels</td>  </tr>  <tr>  <td><strong><em>config.worker_config.num_instances</em></strong></td>  <td>Resize primary worker group</td>  </tr>  <tr>  <td><strong><em>config.secondary_worker_config.num_instances</em></strong></td>  <td>Resize secondary worker group</td>  </tr>  </tbody>  </table>
    942   x__xgafv: string, V1 error format.
    943     Allowed values
    944       1 - v1 error format
    945       2 - v2 error format
    946 
    947 Returns:
    948   An object of the form:
    949 
    950     { # This resource represents a long-running operation that is the result of a network API call.
    951     "metadata": { # Service-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method that returns a long-running operation should document the metadata type, if any.
    952       "a_key": "", # Properties of the object. Contains field @type with type URL.
    953     },
    954     "error": { # The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC (https://github.com/grpc). The error model is designed to be: # The error result of the operation in case of failure or cancellation.
    955         # Simple to use and understand for most users
    956         # Flexible enough to meet unexpected needsOverviewThe Status message contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers understand and resolve the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the package google.rpc that can be used for common error conditions.Language mappingThe Status message is the logical representation of the error model, but it is not necessarily the actual wire format. When the Status message is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C.Other usesThe error model and the Status message can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments.Example uses of this error model include:
    957         # Partial errors. If a service needs to return partial errors to the client, it may embed the Status in the normal response to indicate the partial errors.
    958         # Workflow errors. A typical workflow has multiple steps. Each step may have a Status message for error reporting.
    959         # Batch operations. If a client uses batch request and batch response, the Status message should be used directly inside batch response, one for each error sub-response.
    960         # Asynchronous operations. If an API call embeds asynchronous operation results in its response, the status of those operations should be represented directly using the Status message.
    961         # Logging. If some API errors are stored in logs, the message Status could be used directly after any stripping needed for security/privacy reasons.
    962       "message": "A String", # A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.
    963       "code": 42, # The status code, which should be an enum value of google.rpc.Code.
    964       "details": [ # A list of messages that carry the error details. There will be a common set of message types for APIs to use.
    965         {
    966           "a_key": "", # Properties of the object. Contains field @type with type URL.
    967         },
    968       ],
    969     },
    970     "done": True or False, # If the value is false, it means the operation is still in progress. If true, the operation is completed, and either error or response is available.
    971     "response": { # The normal response of the operation in case of success. If the original method returns no data on success, such as Delete, the response is google.protobuf.Empty. If the original method is standard Get/Create/Update, the response should be the resource. For other methods, the response should have the type XxxResponse, where Xxx is the original method name. For example, if the original method name is TakeSnapshot(), the inferred response type is TakeSnapshotResponse.
    972       "a_key": "", # Properties of the object. Contains field @type with type URL.
    973     },
    974     "name": "A String", # The server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the name should have the format of operations/some/unique/name.
    975   }</pre>
    976 </div>
    977 
    978 </body></html>