terraform-ibm-modules / terraform-ibm-landing-zone-vsi Goto Github PK

Description

A VSI created using terraform, we would like to restore a VSI retaining the primary IP address, VSI tags, VSI name, VSI Hostname.
Restore from a snapshot consistency group snapshot (includes boot and data)
Get the VSI to a previous state by retaining IP address / Network interface, VSI tags, VSI name, VSI Hostname
Needs to be available for customers to consume via a deployable architecture and/or IBM Cloud Schematics

New or affected modules

terraform-ibm-landing-zone-vsi/main.tf

Line 92 in ca728d0

resource "ibm_is_instance" "vsi" {

By submitting this issue, you agree to follow our Code of Conduct

Description

Surface snapshot options at https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore&interface=terraform#snapshots-vpc-use-fast-restore

New or affected modules

By submitting this issue, you agree to follow our Code of Conduct

Description

What:

• https://github.com/terraform-ibm-modules/terraform-ibm-security-group has been made available
• The VSI module create security group with own logic at the moment

Goal:

• Replace the security group logic in the module with calls to https://github.com/terraform-ibm-modules/terraform-ibm-landing-zone-vsi/blob/main/security_group.tf .
• Add the extra capability add_ibm_cloud_internal_rules to the module interface https://github.com/terraform-ibm-modules/terraform-ibm-landing-zone-vsi/blob/main/variables.tf#L109
• Use moved blocks if possible to avoid breaking change https://github.com/terraform-ibm-modules/terraform-ibm-landing-zone-vsi/blob/main/security_group.tf (but this may not be fully possible - we should discuss if so)

Description

There are some limitations when using secondary interfaces which are not obvious at first glance (eg. matching zones in subnets and secondary_subnets), so it would be good to have an example creating 3 vsis across 3 zones, each with secondary interfaces

Description

See discussion at #569

Affected modules

• terraform-ibm-landing-zone-vsi

Terraform CLI and Terraform provider versions

• Terraform version: Terraform v1.5.7
• Provider version: registry.terraform.io/ibm-cloud/ibm v1.63.0

Terraform output

terraform_outout.txt

Debug output

Expected behavior

NLB Load Balancer Backend Pool should be attached with the generated VSIs from the module.

Actual behavior

terraform apply fails with above attached message:
"code": "member_invalid_nlb_target",
"message": "Network load balancer members must be specified with either id or href or crn."

Steps to reproduce (including links and screen captures)

Using this terraform configuration during terraform apply.
vsi_terraform.txt

Anything else

Any suggestions appreciated. Thanks!

By submitting this issue, you agree to follow our Code of Conduct

Description

Here

Similar to what we did in https://github.ibm.com/GoldenEye/operations/tree/master/slz-vsi-image-name-update except we need the image ID for the examples used in this module

Description

Currently the data volumes created by the module are provisioned in Default resource group, ignoring the VSI RG and not allowing to specify one for the data volume.

The module should use the resource group provided in VSI attributes or support a resource_group in data volume structure.

New or affected modules

• storage.tf - ibm_is_volume resource should use var.resource_group_id or RG provided in the storage volume variable structure.
• variables.tf - if resource_group attribute is added to block_storage_volumes structure