Data Source: oci_core_instance_pools

This data source provides the list of Instance Pools in Oracle Cloud Infrastructure Core service.

Lists the instance pools in the specified compartment.

Example Usage

data "oci_core_instance_pools" "test_instance_pools" {
	#Required
	compartment_id = var.compartment_id

	#Optional
	display_name = var.instance_pool_display_name
	state = var.instance_pool_state
}

Argument Reference

The following arguments are supported:

• compartment_id - (Required) The OCID of the compartment.
• display_name - (Optional) A filter to return only resources that match the given display name exactly.
• state - (Optional) A filter to only return resources that match the given lifecycle state. The state value is case-insensitive.

Attributes Reference

The following attributes are exported:

• instance_pools - The list of instance_pools.

InstancePool Reference

The following attributes are exported:

• compartment_id - The OCID of the compartment containing the instance pool.

• 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 instance pool.

• instance_configuration_id - The OCID of the instance configuration associated with the instance pool.

• instance_display_name_formatter - A user-friendly formatter for the instance pool’s instances. Instance displaynames follow the format. The formatter does not retroactively change instance’s displaynames, only instance displaynames in the future follow the format

• instance_hostname_formatter - A user-friendly formatter for the instance pool’s instances. Instance hostnames follow the format. The formatter does not retroactively change instance’s hostnames, only instance hostnames in the future follow the format

• load_balancers - The load balancers attached to the instance pool.

  • backend_set_name - The name of the backend set on the load balancer.
  • id - The OCID of the load balancer attachment.
  • instance_pool_id - The OCID of the instance pool of the load balancer attachment.
  • load_balancer_id - The OCID of the load balancer attached to the instance pool.
  • port - The port value used for the backends.
  • state - The status of the interaction between the instance pool and the load balancer.
  • vnic_selection - Indicates which VNIC on each instance in the instance pool should be used to associate with the load balancer. Possible values are “PrimaryVnic” or the displayName of one of the secondary VNICs on the instance configuration that is associated with the instance pool.

• placement_configurations - The placement configurations for the instance pool.

  • availability_domain - The availability domain to place instances. Example: Uocm:PHX-AD-1

  • fault_domains - The fault domains to place instances.

    If you don’t provide any values, the system makes a best effort to distribute instances across all fault domains based on capacity.

    To distribute the instances evenly across selected fault domains, provide a set of fault domains. For example, you might want instances to be evenly distributed if your applications require high availability.

    To get a list of fault domains, use the ListFaultDomains operation in the Identity and Access Management Service API.

    Example: [FAULT-DOMAIN-1, FAULT-DOMAIN-2, FAULT-DOMAIN-3]

  • primary_subnet_id - The OCID of the primary subnet to place instances. This field is deprecated. Use primaryVnicSubnets instead to set VNIC data for instances in the pool.

  • primary_vnic_subnets - Details about the IPv6 primary subnet.

    • ipv6address_ipv6subnet_cidr_pair_details - A list of IPv6 prefix ranges from which the VNIC should be assigned an IPv6 address. You can provide only the prefix ranges and Oracle Cloud Infrastructure will select an available address from the range. You can optionally choose to leave the prefix range empty and instead provide the specific IPv6 address that should be used from within that range.
      • ipv6subnet_cidr - Optional. Used to disambiguate which subnet prefix should be used to create an IPv6 allocation.
    • is_assign_ipv6ip - Whether to allocate an IPv6 address at instance and VNIC creation from an IPv6 enabled subnet. Default: False. When provided you may optionally provide an IPv6 prefix (ipv6SubnetCidr) of your choice to assign the IPv6 address from. If ipv6SubnetCidr is not provided then an IPv6 prefix is chosen for you.
    • subnet_id - The subnet OCID for the secondary VNIC.

  • secondary_vnic_subnets - The set of secondary VNIC data for instances in the pool.

    • display_name - The display name of the VNIC. This is also used to match against the instance configuration defined secondary VNIC.
    • ipv6address_ipv6subnet_cidr_pair_details - A list of IPv6 prefix ranges from which the VNIC should be assigned an IPv6 address. You can provide only the prefix ranges and Oracle Cloud Infrastructure will select an available address from the range. You can optionally choose to leave the prefix range empty and instead provide the specific IPv6 address that should be used from within that range.
      • ipv6subnet_cidr - Optional. Used to disambiguate which subnet prefix should be used to create an IPv6 allocation.
    • is_assign_ipv6ip - Whether to allocate an IPv6 address at instance and VNIC creation from an IPv6 enabled subnet. Default: False. When provided you may optionally provide an IPv6 prefix (ipv6SubnetCidr) of your choice to assign the IPv6 address from. If ipv6SubnetCidr is not provided then an IPv6 prefix is chosen for you.
    • subnet_id - The subnet OCID for the secondary VNIC.

• size - The number of actual instances in the instance pool on the cloud. This attribute will be different when instance pool is used along with autoScaling Configuration.

• state - The current state of the instance pool.

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