Data Source: oci_core_boot_volumes

This data source provides the list of Boot Volumes in Oracle Cloud Infrastructure Core service.

Lists the boot volumes in the specified compartment and availability domain.

Example Usage

data "oci_core_boot_volumes" "test_boot_volumes" {

	#Optional
	availability_domain = var.boot_volume_availability_domain
	compartment_id = var.compartment_id
	volume_group_id = oci_core_volume_group.test_volume_group.id
}

Argument Reference

The following arguments are supported:

• availability_domain - (Optional) The name of the availability domain. Example: Uocm:PHX-AD-1
• compartment_id - (Optional) The OCID of the compartment.
• volume_group_id - (Optional) The OCID of the volume group.

Attributes Reference

The following attributes are exported:

• boot_volumes - The list of boot_volumes.

BootVolume Reference

The following attributes are exported:

• auto_tuned_vpus_per_gb - The number of Volume Performance Units per GB that this boot volume is effectively tuned to.

• autotune_policies - The list of autotune policies enabled for this volume.

  • autotune_type - This specifies the type of autotunes supported by OCI.
  • max_vpus_per_gb - This will be the maximum VPUs/GB performance level that the volume will be auto-tuned temporarily based on performance monitoring.

• availability_domain - The availability domain of the boot volume. Example: Uocm:PHX-AD-1

• boot_volume_replicas - The list of boot volume replicas of this boot volume

  • availability_domain - The availability domain of the boot volume replica. Example: Uocm:PHX-AD-1
  • boot_volume_replica_id - The boot volume replica’s Oracle ID (OCID).
  • display_name - A user-friendly name. Does not have to be unique, and it’s changeable. Avoid entering confidential information.
  • kms_key_id - The OCID of the Vault service key to assign as the master encryption key for the block volume replica, see Overview of Vault service and Using Keys.

• cluster_placement_group_id - The clusterPlacementGroup Id of the volume for volume placement.

• compartment_id - The OCID of the compartment that contains the boot 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"}

• id - The boot volume’s Oracle ID (OCID).

• image_id - The image OCID used to create the boot volume.

• is_auto_tune_enabled - Specifies whether the auto-tune performance is enabled for this boot volume. This field is deprecated. Use the DetachedVolumeAutotunePolicy instead to enable the volume for detached autotune.

• is_hydrated - Specifies whether the boot volume’s data has finished copying from the source boot volume or boot volume backup.

• kms_key_id - The OCID of the Vault service master encryption key assigned to the boot volume.

• size_in_gbs - The size of the boot volume in GBs.

• size_in_mbs - The size of the volume in MBs. The value must be a multiple of 1024. This field is deprecated. Please use size_in_gbs.

• source_details -

  • change_block_size_in_bytes - Block size in bytes to be considered while performing volume restore. The value must be a power of 2; ranging from 4KB (4096 bytes) to 1MB (1048576 bytes). If omitted, defaults to 4,096 bytes (4 KiB).
  • first_backup_id - The OCID of the first boot volume backup.
  • id - The OCID of the boot volume replica.
  • second_backup_id - The OCID of the second boot volume backup.
  • type - The type can be one of these values: bootVolume, bootVolumeBackup, bootVolumeBackupDelta, bootVolumeReplica

• state - The current state of a boot volume.

• system_tags - System tags for this resource. Each key is predefined and scoped to a namespace. Example: {"foo-namespace.bar-key": "value"}

• time_created - The date and time the boot volume was created. Format defined by RFC3339.

• volume_group_id - The OCID of the source volume group.

• vpus_per_gb - The number of volume performance units (VPUs) that will be applied to this boot volume per GB, representing the Block Volume service’s elastic performance options. See Block Volume Performance Levels for more information.

  Allowed values:

  • 10: Represents Balanced option.
  • 20: Represents Higher Performance option.
  • 30-120: Represents the Ultra High Performance option.

  For performance autotune enabled volumes, it would be the Default(Minimum) VPUs/GB.