Namespace MountTargetSummary

The availability domain the mount target is in. May be unset as a blank or NULL value.

Example: {@code Uocm:PHX-AD-1}

The OCID of the compartment that contains the mount target.

Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {@code {"Operations": {"CostCenter": "42"}}}

A user-friendly name. It does not have to be unique, and it is changeable. Avoid entering confidential information.

Example: {@code My mount target}

The OCID of the associated export set. Controls what file systems will be exported using Network File System (NFS) protocol on this mount target.

Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {@code {"Department": "Finance"}}

The OCID of the mount target.

The current state of the mount target.

A list of Network Security Group OCIDs associated with this mount target. A maximum of 5 is allowed. Setting this to an empty array after the list is created removes the mount target from all NSGs. For more information about NSGs, see Security Rules.

Current billed throughput for mount target in Gbps. This corresponds to shape of mount target. Available shapes and corresponding throughput are listed at Mount Target Performance. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.

The OCIDs of the private IP addresses associated with this mount target.

• New throughput for mount target at the end of billing cycle in Gbps. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.

• Reserved capacity (GB) associated with this mount target. Reserved capacity depends on observedThroughput value of mount target. Value is listed at Mount Target Performance. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.

The OCID of the subnet the mount target is in.

The date and time the mount target current billing cycle will end, expressed in RFC 3339 timestamp format. Once a cycle ends, it is updated automatically to next timestamp which is after 30 days.

Example: {@code 2016-08-25T21:10:29.600Z}

The date and time the mount target was created, expressed in RFC 3339 timestamp format.

Example: {@code 2016-08-25T21:10:29.600Z}