Data Source: oci_core_compute_clusters

This data source provides the list of Compute Clusters in Oracle Cloud Infrastructure Core service.

Lists the compute clusters in the specified compartment. A compute cluster is a remote direct memory access (RDMA) network group.

Example Usage

data "oci_core_compute_clusters" "test_compute_clusters" {
	#Required
	compartment_id = var.compartment_id

	#Optional
	availability_domain = var.compute_cluster_availability_domain
	display_name = var.compute_cluster_display_name
}

Argument Reference

The following arguments are supported:

• availability_domain - (Optional) The name of the availability domain. Example: Uocm:PHX-AD-1
• compartment_id - (Required) The OCID of the compartment.
• display_name - (Optional) A filter to return only resources that match the given display name exactly.

Attributes Reference

The following attributes are exported:

• compute_cluster_collection - The list of compute_cluster_collection.

ComputeCluster Reference

The following attributes are exported:

• availability_domain - The availability domain the compute cluster is running in. Example: Uocm:PHX-AD-1

• compartment_id - The OCID of the compartment that contains the compute cluster.

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

• display_name - A user-friendly name. Does not have to be unique, and it’s changeable. Avoid entering confidential information.

• freeform_tags - 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: {"Department": "Finance"}

• id - The OCID of the compute cluster.

• placement_constraint_details - The details for providing placement constraints.

  • hpc_island_id - The OCID of the HPC island for the compute cluster.

    This field cannot be updated after creation of the compute cluster.

  • logical_placement_constraint - The logical placement strategy to apply. Allowed values are SINGLE_TIER, SINGLE_BLOCK, and PACKED_DISTRIBUTION_MULTI_BLOCK.

  • target_memory_fabric_ids - The list of target GPU memory fabric OCIDs to constrain placement. Up to 15 items are allowed.

    If GMFs are passed in, the hpcIslandId must be set on the compute cluster, and the provided GMFs must belong to that same HPC island.

    The ordering of the array will be preserved. Ensure that all items in the array are unique.

  • target_network_block_ids - The list of target network block OCIDs to constrain placement. Up to 15 items are allowed.

    If targetNetworkBlockIds is provided, the hpcIslandId must be set on the compute cluster, and the provided network blocks must belong to that same HPC island.

    The ordering of the array will be preserved. Ensure that all items in the array are unique.

  • type - The type for the placement constraints. Supported value: COMPUTE_CLUSTER.

• state - The current state of the compute cluster.

• time_created - The date and time the compute cluster was created, in the format defined by RFC3339. Example: 2016-08-25T21:10:29.600Z

• time_updated - The date and time the compute cluster was updated, in the format defined by RFC3339. Example: 2016-08-25T21:10:29.600Z