» Data Source: oci_core_instance_configurations

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

Lists the available instanceConfigurations in the specific compartment.

» Example Usage

data "oci_core_instance_configurations" "test_instance_configurations" {
    #Required
    compartment_id = "${var.compartment_id}"
}

» Argument Reference

The following arguments are supported:

» Attributes Reference

The following attributes are exported:

» InstanceConfiguration Reference

The following attributes are exported:

  • compartment_id - The OCID of the compartment containing the instance configuration.
  • deferred_fields - The required details when using the LaunchInstanceConfiguration operation. These attributes are optional when using the CreateInstanceConfiguration operation.
  • 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 for the instance configuration.
  • 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 configuration.
  • instance_details -

    • block_volumes -
      • attach_details -
        • display_name - A user-friendly name. Does not have to be unique, and it cannot be changed. Avoid entering confidential information.
        • is_read_only - Whether the attachment should be created in read-only mode.
        • type - The type of volume. The only supported values are "iscsi" and "paravirtualized".
        • use_chap - Whether to use CHAP authentication for the volume attachment. Defaults to false.
      • create_details -
        • availability_domain - The availability domain of the volume. Example: Uocm:PHX-AD-1
        • backup_policy_id - If provided, specifies the ID of the volume backup policy to assign to the newly created volume. If omitted, no policy will be assigned.
        • compartment_id - The OCID of the compartment that contains the volume.
        • 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"}
        • size_in_gbs - The size of the volume in GBs.
        • source_details - Specifies the volume source details for a new Block volume. The volume source is either another Block volume in the same availability domain or a Block volume backup. This is an optional field. If not specified or set to null, the new Block volume will be empty. When specified, the new Block volume will contain data from the source volume or backup.
          • id - The OCID of the volume backup.
          • type - The type can be one of these values: volume, volumeBackup
      • volume_id - The OCID of the volume.
    • instance_type - The type of instance details. Supported instanceType is compute
    • launch_details -

      • availability_domain - The availability domain of the instance. Example: Uocm:PHX-AD-1
      • compartment_id - The OCID of the compartment.
      • create_vnic_details - Details for the primary VNIC, which is automatically created and attached when the instance is launched.
        • assign_public_ip - Whether the VNIC should be assigned a public IP address. See the assignPublicIp attribute of CreateVnicDetails for more information.
        • display_name - A user-friendly name for the VNIC. Does not have to be unique. Avoid entering confidential information.
        • hostname_label - The hostname for the VNIC's primary private IP. See the hostnameLabel attribute of CreateVnicDetails for more information.
        • nsg_ids - A list of the OCIDs of the network security groups (NSGs) to add the VNIC to. For more information about NSGs, see NetworkSecurityGroup.
        • private_ip - A private IP address of your choice to assign to the VNIC. See the privateIp attribute of CreateVnicDetails for more information.
        • skip_source_dest_check - Whether the source/destination check is disabled on the VNIC. See the skipSourceDestCheck attribute of CreateVnicDetails for more information.
        • subnet_id - The OCID of the subnet to create the VNIC in. See the subnetId attribute of CreateVnicDetails for more information.
      • 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. Example: My bare metal instance
      • extended_metadata - Additional metadata key/value pairs that you provide. They serve the same purpose and functionality as fields in the 'metadata' object.

        They are distinguished from 'metadata' fields in that these can be nested JSON objects (whereas 'metadata' fields are string/string maps only).

      • fault_domain - A fault domain is a grouping of hardware and infrastructure within an availability domain. Each availability domain contains three fault domains. Fault domains let you distribute your instances so that they are not on the same physical hardware within a single availability domain. A hardware failure or Compute hardware maintenance that affects one fault domain does not affect instances in other fault domains.

        If you do not specify the fault domain, the system selects one for you. To change the fault domain for an instance, terminate it and launch a new instance in the preferred fault domain.

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

        Example: FAULT-DOMAIN-1

      • 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"}

      • ipxe_script - This is an advanced option.

        When a bare metal or virtual machine instance boots, the iPXE firmware that runs on the instance is configured to run an iPXE script to continue the boot process.

        If you want more control over the boot process, you can provide your own custom iPXE script that will run when the instance boots; however, you should be aware that the same iPXE script will run every time an instance boots; not only after the initial LaunchInstance call.

        The default iPXE script connects to the instance's local boot volume over iSCSI and performs a network boot. If you use a custom iPXE script and want to network-boot from the instance's local boot volume over iSCSI the same way as the default iPXE script, you should use the following iSCSI IP address: 169.254.0.2, and boot volume IQN: iqn.2015-02.oracle.boot.

        For more information about the Bring Your Own Image feature of Oracle Cloud Infrastructure, see Bring Your Own Image.

        For more information about iPXE, see http://ipxe.org.

      • metadata - Custom metadata key/value pairs that you provide, such as the SSH public key required to connect to the instance.

        A metadata service runs on every launched instance. The service is an HTTP endpoint listening on 169.254.169.254. You can use the service to:

        • Provide information to Cloud-Init to be used for various system initialization tasks.
        • Get information about the instance, including the custom metadata that you provide when you launch the instance.

        Providing Cloud-Init Metadata

        You can use the following metadata key names to provide information to Cloud-Init:

        "ssh_authorized_keys" - Provide one or more public SSH keys to be included in the ~/.ssh/authorized_keys file for the default user on the instance. Use a newline character to separate multiple keys. The SSH keys must be in the format necessary for the authorized_keys file, as shown in the example below.

        "user_data" - Provide your own base64-encoded data to be used by Cloud-Init to run custom scripts or provide custom Cloud-Init configuration. For information about how to take advantage of user data, see the Cloud-Init Documentation.

        Note: Cloud-Init does not pull this data from the http://169.254.169.254/opc/v1/instance/metadata/ path. When the instance launches and either of these keys are provided, the key values are formatted as OpenStack metadata and copied to the following locations, which are recognized by Cloud-Init:

        http://169.254.169.254/openstack/latest/meta_data.json - This JSON blob contains, among other things, the SSH keys that you provided for "ssh_authorized_keys".

        http://169.254.169.254/openstack/latest/user_data - Contains the base64-decoded data that you provided for "user_data".

        Metadata Example

        "metadata" : { "quake_bot_level" : "Severe", "ssh_authorized_keys" : "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCZ06fccNTQfq+xubFlJ5ZR3kt+uzspdH9tXL+lAejSM1NXM+CFZev7MIxfEjas06y80ZBZ7DUTQO0GxJPeD8NCOb1VorF8M4xuLwrmzRtkoZzU16umt4y1W0Q4ifdp3IiiU0U8/WxczSXcUVZOLqkz5dc6oMHdMVpkimietWzGZ4LBBsH/LjEVY7E0V+a0sNchlVDIZcm7ErReBLcdTGDq0uLBiuChyl6RUkX1PNhusquTGwK7zc8OBXkRuubn5UKXhI3Ul9Nyk4XESkVWIGNKmw8mSpoJSjR8P9ZjRmcZVo8S+x4KVPMZKQEor== ryan.smith@company.com ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAQEAzJSAtwEPoB3Jmr58IXrDGzLuDYkWAYg8AsLYlo6JZvKpjY1xednIcfEVQJm4T2DhVmdWhRrwQ8DmayVZvBkLt+zs2LdoAJEVimKwXcJFD/7wtH8Lnk17HiglbbbNXsemjDY0hea4JUE5CfvkIdZBITuMrfqSmA4n3VNoorXYdvtTMoGG8fxMub46RPtuxtqi9bG9Zqenordkg5FJt2mVNfQRqf83CWojcOkklUWq4CjyxaeLf5i9gv1fRoBo4QhiA8I6NCSppO8GnoV/6Ox6TNoh9BiifqGKC9VGYuC89RvUajRBTZSK2TK4DPfaT+2R+slPsFrwiT/oPEhhEK1S5Q== rsa-key-20160227", "user_data" : "SWYgeW91IGNhbiBzZWUgdGhpcywgdGhlbiBpdCB3b3JrZWQgbWF5YmUuCg==" } Getting Metadata on the Instance

        To get information about your instance, connect to the instance using SSH and issue any of the following GET requests:

        curl http://169.254.169.254/opc/v1/instance/ curl http://169.254.169.254/opc/v1/instance/metadata/ curl http://169.254.169.254/opc/v1/instance/metadata/

        You'll get back a response that includes all the instance information; only the metadata information; or the metadata information for the specified key name, respectively.

      • shape - The shape of an instance. The shape determines the number of CPUs, amount of memory, and other resources allocated to the instance.

        You can enumerate all available shapes by calling ListShapes.

      • source_details - Details for creating an instance. Use this parameter to specify whether a boot volume or an image should be used to launch a new instance.

        • boot_volume_id - The OCID of the boot volume used to boot the instance.
        • boot_volume_size_in_gbs - The size of the boot volume in GBs. The minimum value is 50 GB and the maximum value is 16384 GB (16TB).
        • image_id - The OCID of the image used to boot the instance.
        • source_type - The source type for the instance. Use image when specifying the image OCID. Use bootVolume when specifying the boot volume OCID.
    • secondary_vnics -

      • create_vnic_details - Details for creating a new VNIC.
        • assign_public_ip - Whether the VNIC should be assigned a public IP address. See the assignPublicIp attribute of CreateVnicDetails for more information.
        • display_name - A user-friendly name for the VNIC. Does not have to be unique. Avoid entering confidential information.
        • hostname_label - The hostname for the VNIC's primary private IP. See the hostnameLabel attribute of CreateVnicDetails for more information.
        • nsg_ids - A list of the OCIDs of the network security groups (NSGs) to add the VNIC to. For more information about NSGs, see NetworkSecurityGroup.
        • private_ip - A private IP address of your choice to assign to the VNIC. See the privateIp attribute of CreateVnicDetails for more information.
        • skip_source_dest_check - Whether the source/destination check is disabled on the VNIC. See the skipSourceDestCheck attribute of CreateVnicDetails for more information.
        • subnet_id - The OCID of the subnet to create the VNIC in. See the subnetId attribute of CreateVnicDetails for more information.
      • display_name - A user-friendly name for the attachment. Does not have to be unique, and it cannot be changed.
      • nic_index - Which physical network interface card (NIC) the VNIC will use. Defaults to 0. Certain bare metal instance shapes have two active physical NICs (0 and 1). If you add a secondary VNIC to one of these instances, you can specify which NIC the VNIC will use. For more information, see Virtual Network Interface Cards (VNICs).
  • time_created - The date and time the instance configuration was created, in the format defined by RFC3339. Example: 2016-08-25T21:10:29.600Z