telefonicaopencloud_as_configuration_v1

Manages a V1 AS Configuration resource within TelefonicaOpenCloud.

Example Usage

Basic AS Configuration

resource "telefonicaopencloud_as_configuration_v1" "my_as_config" {
  scaling_configuration_name = "my_as_config"
  instance_config = {
    flavor = "${var.flavor}"
    image = "${var.image_id}"
    disk = [
      {size = 40
      volume_type = "SATA"
      disk_type = "SYS"}
    ]
    key_name = "${var.keyname}"
    user_data = "${file("userdata.txt")}"
  }
}

AS Configuration With User Data and Metadata

resource "telefonicaopencloud_as_configuration_v1" "my_as_config" {
  scaling_configuration_name = "my_as_config"
  instance_config = {
    flavor = "${var.flavor}"
    image = "${var.image_id}"
    disk = [
      {size = 40
      volume_type = "SATA"
      disk_type = "SYS"}
    ]
    key_name = "${var.keyname}"
    user_data = "${file("userdata.txt")}"
    metadata = {
      some_key = "some_value"
    }
  }
}

user_data can come from a variety of sources: inline, read in from the file function, or the template_cloudinit_config resource.

AS Configuration uses the existing instance specifications as the template

resource "telefonicaopencloud_as_configuration_v1" "my_as_config" {
  scaling_configuration_name = "my_as_config"
  instance_config = {
    instance_id = "4579f2f5-cbe8-425a-8f32-53dcb9d9053a"
    key_name = "${var.keyname}"
  }
}

Argument Reference

The following arguments are supported:

• region - (Optional) The region in which to create the AS configuration. If omitted, the region argument of the provider is used. Changing this creates a new AS configuration.

• scaling_configuration_name - (Required) The name of the AS configuration. The name can contain letters, digits, underscores(_), and hyphens(-), and cannot exceed 64 characters.

• instance_config - (Required) The information about instance configurations. The instance_config dictionary data structure is documented below.

The instance_config block supports:

• instance_id - (Optional) When using the existing instance specifications as the template to create AS configurations, specify this argument. In this case, flavor, image, and disk arguments do not take effect. If the instance_id argument is not specified, flavor, image, and disk arguments are mandatory.

• flavor - (Optional) The flavor ID.

• image - (Optional) The image ID.

• disk - (Optional) The disk group information. System disks are mandatory and data disks are optional. The dick structure is described below.

• key_name - (Required) The name of the SSH key pair used to log in to the instance.

• user_data - (Optional) The user data to provide when launching the instance. The file content must be encoded with Base64.

• personality - (Optional) Customize the personality of an instance by defining one or more files and their contents. The personality structure is described below.

• public_ip - (Optional) The elastic IP address of the instance. The public_ip structure is described below.

• metadata - (Optional) Metadata key/value pairs to make available from within the instance.

The disk block supports:

• size - (Required) The disk size. The unit is GB. The system disk size ranges from 40 to 32768, and the data disk size ranges from 10 to 32768.

• volume_type - (Required) The disk type, which must be the same as the disk type available in the system. The options include SATA (common I/O disk type) and SSD (ultra-high I/O disk type).

• disk_type - (Required) Whether the disk is a system disk or a data disk. Option DATA indicates a data disk. option SYS indicates a system disk.

The personality block supports:

• path - (Required) The absolute path of the destination file.

• contents - (Required) The content of the injected file, which must be encoded with base64.

The public_ip block supports:

• eip - (Required) The configuration parameter for creating an elastic IP address that will be automatically assigned to the instance. The eip structure is described below.

The eip block supports:

• ip_type - (Required) The IP address type. The system only supports 5_bgp (indicates dynamic BGP).

• bandwidth - (Required) The bandwidth information. The structure is described below.

The bandwidth block supports:

• size - (Required) The bandwidth (Mbit/s). The value range is 1 to 300.

• share_type - (Required) The bandwidth sharing type. The system only supports PER (indicates exclusive bandwidth).

• charging_mode - (Required) The bandwidth charging mode. The system only supports traffic.