You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<pclass="firstline">Resets a QueuedResource TPU instance</p>
95
98
<h3>Method Details</h3>
96
99
<divclass="method">
97
100
<codeclass="details" id="close">close()</code>
@@ -160,6 +163,10 @@ <h3>Method Details</h3>
160
163
"tpu": { # Details of the TPU resource(s) being requested. # Defines a TPU resource.
161
164
"nodeSpec": [ # The TPU node(s) being requested.
162
165
{ # Details of the TPU node(s) being requested. Users can request either a single node or multiple nodes. NodeSpec provides the specification for node(s) to be created.
166
+
"multiNodeParams": { # Parameters to specify for multi-node QueuedResource requests. This field must be populated in case of multi-node requests instead of node_id. It's an error to specify both node_id and multi_node_params. # Optional. Fields to specify in case of multi-node request.
167
+
"nodeCount": 42, # Required. Number of nodes with this spec. The system will attempt to provison "node_count" nodes as part of the request. This needs to be > 1.
168
+
"nodeIdPrefix": "A String", # Prefix of node_ids in case of multi-node request Should follow the `^[A-Za-z0-9_.~+%-]+$` regex format. If node_count = 3 and node_id_prefix = "np", node ids of nodes created will be "np-0", "np-1", "np-2". If this field is not provided we use queued_resource_id as the node_id_prefix.
169
+
},
163
170
"node": { # A TPU instance. # Required. The node.
164
171
"acceleratorConfig": { # A TPU accelerator configuration. # The AccleratorConfig for the TPU Node.
165
172
"topology": "A String", # Required. Topology of TPU in chips.
@@ -372,6 +379,10 @@ <h3>Method Details</h3>
372
379
"tpu": { # Details of the TPU resource(s) being requested. # Defines a TPU resource.
373
380
"nodeSpec": [ # The TPU node(s) being requested.
374
381
{ # Details of the TPU node(s) being requested. Users can request either a single node or multiple nodes. NodeSpec provides the specification for node(s) to be created.
382
+
"multiNodeParams": { # Parameters to specify for multi-node QueuedResource requests. This field must be populated in case of multi-node requests instead of node_id. It's an error to specify both node_id and multi_node_params. # Optional. Fields to specify in case of multi-node request.
383
+
"nodeCount": 42, # Required. Number of nodes with this spec. The system will attempt to provison "node_count" nodes as part of the request. This needs to be > 1.
384
+
"nodeIdPrefix": "A String", # Prefix of node_ids in case of multi-node request Should follow the `^[A-Za-z0-9_.~+%-]+$` regex format. If node_count = 3 and node_id_prefix = "np", node ids of nodes created will be "np-0", "np-1", "np-2". If this field is not provided we use queued_resource_id as the node_id_prefix.
385
+
},
375
386
"node": { # A TPU instance. # Required. The node.
376
387
"acceleratorConfig": { # A TPU accelerator configuration. # The AccleratorConfig for the TPU Node.
377
388
"topology": "A String", # Required. Topology of TPU in chips.
@@ -522,6 +533,10 @@ <h3>Method Details</h3>
522
533
"tpu": { # Details of the TPU resource(s) being requested. # Defines a TPU resource.
523
534
"nodeSpec": [ # The TPU node(s) being requested.
524
535
{ # Details of the TPU node(s) being requested. Users can request either a single node or multiple nodes. NodeSpec provides the specification for node(s) to be created.
536
+
"multiNodeParams": { # Parameters to specify for multi-node QueuedResource requests. This field must be populated in case of multi-node requests instead of node_id. It's an error to specify both node_id and multi_node_params. # Optional. Fields to specify in case of multi-node request.
537
+
"nodeCount": 42, # Required. Number of nodes with this spec. The system will attempt to provison "node_count" nodes as part of the request. This needs to be > 1.
538
+
"nodeIdPrefix": "A String", # Prefix of node_ids in case of multi-node request Should follow the `^[A-Za-z0-9_.~+%-]+$` regex format. If node_count = 3 and node_id_prefix = "np", node ids of nodes created will be "np-0", "np-1", "np-2". If this field is not provided we use queued_resource_id as the node_id_prefix.
539
+
},
525
540
"node": { # A TPU instance. # Required. The node.
526
541
"acceleratorConfig": { # A TPU accelerator configuration. # The AccleratorConfig for the TPU Node.
527
542
"topology": "A String", # Required. Topology of TPU in chips.
name: string, Required. The name of the queued resource. (required)
643
+
body: object, The request body.
644
+
The object takes the form of:
645
+
646
+
{ # Request for ResetQueuedResource.
647
+
}
648
+
649
+
x__xgafv: string, V1 error format.
650
+
Allowed values
651
+
1 - v1 error format
652
+
2 - v2 error format
653
+
654
+
Returns:
655
+
An object of the form:
656
+
657
+
{ # This resource represents a long-running operation that is the result of a network API call.
658
+
"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.
659
+
"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). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # The error result of the operation in case of failure or cancellation.
660
+
"code": 42, # The status code, which should be an enum value of google.rpc.Code.
661
+
"details": [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
662
+
{
663
+
"a_key": "", # Properties of the object. Contains field @type with type URL.
664
+
},
665
+
],
666
+
"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.
667
+
},
668
+
"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.
669
+
"a_key": "", # Properties of the object. Contains field @type with type URL.
670
+
},
671
+
"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 be a resource name ending with `operations/{unique_id}`.
672
+
"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`.
673
+
"a_key": "", # Properties of the object. Contains field @type with type URL.
"description": "Parameters to specify for multi-node QueuedResource requests. This field must be populated in case of multi-node requests instead of node_id. It's an error to specify both node_id and multi_node_params.",
1366
+
"id": "MultiNodeParams",
1367
+
"properties": {
1368
+
"nodeCount": {
1369
+
"description": "Required. Number of nodes with this spec. The system will attempt to provison \"node_count\" nodes as part of the request. This needs to be > 1.",
1370
+
"format": "int32",
1371
+
"type": "integer"
1372
+
},
1373
+
"nodeIdPrefix": {
1374
+
"description": "Prefix of node_ids in case of multi-node request Should follow the `^[A-Za-z0-9_.~+%-]+$` regex format. If node_count = 3 and node_id_prefix = \"np\", node ids of nodes created will be \"np-0\", \"np-1\", \"np-2\". If this field is not provided we use queued_resource_id as the node_id_prefix.",
1375
+
"type": "string"
1376
+
}
1377
+
},
1378
+
"type": "object"
1379
+
},
1336
1380
"NetworkConfig": {
1337
1381
"description": "Network related configurations.",
1338
1382
"id": "NetworkConfig",
@@ -1573,6 +1617,10 @@
1573
1617
"description": "Details of the TPU node(s) being requested. Users can request either a single node or multiple nodes. NodeSpec provides the specification for node(s) to be created.",
1574
1618
"id": "NodeSpec",
1575
1619
"properties": {
1620
+
"multiNodeParams": {
1621
+
"$ref": "MultiNodeParams",
1622
+
"description": "Optional. Fields to specify in case of multi-node request."
1623
+
},
1576
1624
"node": {
1577
1625
"$ref": "Node",
1578
1626
"description": "Required. The node."
@@ -1818,6 +1866,12 @@
1818
1866
},
1819
1867
"type": "object"
1820
1868
},
1869
+
"ResetQueuedResourceRequest": {
1870
+
"description": "Request for ResetQueuedResource.",
1871
+
"id": "ResetQueuedResourceRequest",
1872
+
"properties": {},
1873
+
"type": "object"
1874
+
},
1821
1875
"RuntimeVersion": {
1822
1876
"description": "A runtime version that a Node can be configured with.",
0 commit comments