The request message for Operations.CancelOperation.

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance:

service Foo {
  rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty);
}

The JSON representation for Empty is empty JSON object {}.

The name of the file share (must be 16 characters or less).

File share capacity in gigabytes (GB). Cloud Filestore defines 1 GB as 1024^3 bytes.

Output only. Timestamp when the resource was last modified.

Output only. ID of the associated GCP tenant project. See go/get-instance-metadata.

Output only. Current lifecycle state of the resource (e.g. if it's being created or ready to use).

Software versions that are used to deploy this instance. This can be mutated by rollout services.

Output only. SLO metadata for instance classification in the Standardized dataplane SLO platform. See go/cloud-ssa-standard-slo for feature description.

The map between RolloutType and the corresponding RolloutMetadata. This is only mutated by rollout service. For actuation implementation, this information is pass-through for Rollout management. Producer shall not modify by itself. For update of a single entry in this map, the update field mask shall follow this sementics: go/advanced-field-masks

Output only. The list of data plane resources provisioned for this instance, e.g. compute VMs. See go/get-instance-metadata.

Output only. Custom string attributes used primarily to expose producer-specific information in monitoring dashboards. See go/get-instance-metadata.

Unique name of the resource. It uses the form: projects/{project_id}/locations/{location_id}/instances/{instance_id}

The MaintenanceSchedule contains the scheduling information of published maintenance schedule.

The MaintenancePolicies that have been attached to the instance. The key must be of the type name of the oneof policy name defined in MaintenancePolicy, and the referenced policy must define the same policy type. For complete details of MaintenancePolicy, please refer to go/cloud-saas-mw-ug.

Optional. Resource labels to represent user provided metadata. Each label is a key-value pair, where both the key and the value are arbitrary strings provided by the user.

Output only. Timestamp when the resource was created.

consumer_defined_name is the name that is set by the consumer. On the other hand Name field represents system-assigned id of an instance so consumers are not necessarily aware of it. consumer_defined_name is used for notification/UI purposes for consumer to recognize their instances.

The scheduled start time for the maintenance.

The rollout management policy this maintenance schedule is associated with. When doing reschedule update request, the reschedule should be against this given policy.

The scheduled end time for the maintenance.

Can this scheduled update be rescheduled? By default, it's true and API needs to do explicitly check whether it's set, if it's set as false explicitly, it's false

The id of the node. This should be equal to SaasInstanceNode.node_id.

The location of the node, if different from instance location.

By default node is eligible if instance is eligible. But individual node might be excluded from SLO by adding entry here. For semantic see SloMetadata.exclusions. If both instance and node level exclusions are present for time period, the node level's reason will be reported by Eligibility Exporter.

The target release to be applied to the instance.

The scheduled start time for the maintenance window during which update can be performed on the instance.

The scheduled end time for the maintenance window during which update can be performed on the instance.

Whether the instance update has been rescheduled.

URL identifying the resource, e.g. "https://www.googleapis.com/compute/v1/projects/...)".

Type of the resource. This can be either a GCP resource or a custom one (e.g. another cloud provider's VM). For GCP compute resources use singular form of the names listed in GCP compute API documentation (https://cloud.google.com/compute/docs/reference/rest/v1/), prefixed with 'compute-', for example: 'compute-instance', 'compute-disk', 'compute-autoscaler'.

The last rollout that has been applied to the instance.

The last Release that has been applied to the instance.

Instance level notification metadata.

Name of an SLI that this exclusion applies to. Can be left empty, signaling that the instance should be excluded from all SLIs defined in the service SLO configuration.

Human-readable reason for the exclusion. This should be a static string (e.g. "Disruptive update in progress") and should not contain dynamically generated data (e.g. instance name). Can be left empty.

Start time of the exclusion. No alignment (e.g. to a full minute) needed.

Exclusion duration. No restrictions on the possible values.

When an ongoing operation is taking longer than initially expected, an existing entry in the exclusion list can be updated by extending the duration. This is supported by the subsystem exporting eligibility data as long as such extension is committed at least 10 minutes before the original exclusion expiration - otherwise it is possible that there will be "gaps" in the exclusion application in the exported timeseries.

Name of the SLO tier the Instance belongs to. This name will be expected to match the tiers specified in the service SLO configuration.

Field is mandatory and must not be empty.

Optional: list of nodes. Some producers need to use per-node metadata to calculate SLO. This field allows such producers to publish per-node SLO meta data, which will be consumed by SSA Eligibility Exporter and published in the form of per node metric to Monarch.

List of SLO exclusion windows. When multiple entries in the list match (matching the exclusion time-window against current time point) the exclusion reason used in the first matching entry will be published.

It is not needed to include expired exclusion in this list, as only the currently applicable exclusions are taken into account by the eligibility exporting subsystem (the historical state of exclusions will be reflected in the historically produced timeseries regardless of the current state).

This field can be used to mark the instance as temporary ineligible for the purpose of SLO calculation. For permanent instance SLO exclusion, a dedicated tier name can be used that does not have targets specified in the service SLO configuration.

The service tier of the instance.

Output only. Additional information about the instance state, if available.

Output only. The instance state.

VPC networks to which the instance is connected. For this version, only a single network is supported.

Output only. The resource name of the instance, in the format projects/{project_id}/locations/{location_id}/instances/{instance_id}.

Resource labels to represent user provided metadata.

File system shares on the instance. For this version, only a single file share is supported.

Server-specified ETag for the instance resource to prevent simultaneous updates from overwriting each other.

Optional. A description of the instance (2048 characters or less).

Output only. The time when the instance was created.

Locations that could not be reached.

The token you can use to retrieve the next page of results. Not returned if there are no more results in the list.

A list of instances in the project for the specified location.

If the {location} value in the request is "-", the response contains a list of instances from all locations. If any location is unreachable, the response will only return instances in reachable locations and the "unreachable" field will be populated with a list of unreachable locations.

The standard List next-page token.

A list of locations that matches the specified filter in the request.

A list of operations that matches the specified filter in the request.

The standard List next-page token.

Resource name for the location, which may vary between implementations. For example: "projects/example-project/locations/us-east1"

Service-specific metadata. For example the available capacity at the given location.

The canonical id for this location. For example: "us-east1".

Cross-service attributes for the location. For example

{"cloud.googleapis.com/region": "us-east1"}

The friendly name for this location, typically a nearby city name. For example, "Tokyo".

A /29 CIDR block in one of the internal IP address ranges that identifies the range of IP addresses reserved for this instance. For example, 10.0.0.0/29 or 192.168.0.0/29. The range you specify can't overlap with either existing subnets or assigned IP address ranges for other Cloud Filestore instances in the selected VPC network.

The name of the Google Compute Engine VPC network to which the instance is connected.

Internet protocol versions for which the instance has IP addresses assigned. For this version, only MODE_IPV4 is supported.

Output only. IPv4 addresses in the format {octet 1}.{octet 2}.{octet 3}.{octet 4} or IPv6 addresses in the format {block 1}:{block 2}:{block 3}:{block 4}:{block 5}:{block 6}:{block 7}:{block 8}.

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.

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}.

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.

The error result of the operation in case of failure or cancellation.

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.

[Output only] Name of the verb executed by the operation.

[Output only] Server-defined resource path for the target of the operation.

[Output only] Human-readable status of the operation, if any.

[Output only] The time the operation finished running.

[Output only] The time the operation was created.

[Output only] Identifies whether the user has requested cancellation of the operation. Operations that have successfully been cancelled have Operation.error value with a google.rpc.Status.code of 1, corresponding to Code.CANCELLED.

[Output only] API version used to start the operation.

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.

A list of messages that carry the error details. There is a common set of message types for APIs to use.

The status code, which should be an enum value of google.rpc.Code.