Skip to content

Latest commit

 

History

History
67 lines (57 loc) · 7.73 KB

README.md

File metadata and controls

67 lines (57 loc) · 7.73 KB
Raw

Dedicated Interconnect module

This module implements the recommendation proposed in Establishing 99.99% Availability for Dedicated Interconnect.

Prerequisites

  1. Provisioning of four Dedicated Interconnect connections in the prj-interconnect project created in step 1-org under folder fldr-common.

Usage

  1. Rename interconnect.tf.example to interconnect.tf in the shared envs folder in 3-networks-dual-svpc/envs/shared
  2. Update the file interconnect.tf with values that are valid for your environment for the interconnects, locations, candidate subnetworks, vlan_tag8021q and peer info.
  3. Rename interconnect.tf.example to interconnect.tf in base_env folder in 3-networks-dual-svpc/modules/base_env.
  4. Update the file interconnect.tf with values that are valid for your environment for the interconnects, locations, candidate subnetworks, vlan_tag8021q and peer info.
  5. The candidate subnetworks and vlan_tag8021q variables can be set to null to allow the interconnect module to auto generate these values.

Inputs

Name Description Type Default Required
cloud_router_labels A map of suffixes for labelling vlans with four entries like "vlan_1" => "suffix1" with keys from vlan_1 to vlan_4. map(string) {} no
interconnect_project_id Interconnect project ID. string n/a yes
peer_asn Peer BGP Autonomous System Number (ASN). number n/a yes
peer_name Name of this BGP peer. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression a-z? string n/a yes
region1 First subnet region. The Dedicated Interconnect module only configures two regions. string n/a yes
region1_interconnect1 URL of the underlying Interconnect object that this attachment's traffic will traverse through. string n/a yes
region1_interconnect1_candidate_subnets Up to 16 candidate prefixes that can be used to restrict the allocation of cloudRouterIpAddress and customerRouterIpAddress for this attachment. All prefixes must be within link-local address space (169.254.0.0/16) and must be /29 or shorter (/28, /27, etc). list(string) null no
region1_interconnect1_location Name of the interconnect location used in the creation of the Interconnect for the first location of region1 string n/a yes
region1_interconnect1_onprem_dc Name of the on premisses data center used in the creation of the Interconnect for the first location of region1. string n/a yes
region1_interconnect1_vlan_tag8021q The IEEE 802.1Q VLAN tag for this attachment, in the range 2-4094. string null no
region1_interconnect2 URL of the underlying Interconnect object that this attachment's traffic will traverse through. string n/a yes
region1_interconnect2_candidate_subnets Up to 16 candidate prefixes that can be used to restrict the allocation of cloudRouterIpAddress and customerRouterIpAddress for this attachment. All prefixes must be within link-local address space (169.254.0.0/16) and must be /29 or shorter (/28, /27, etc). list(string) null no
region1_interconnect2_location Name of the interconnect location used in the creation of the Interconnect for the second location of region1 string n/a yes
region1_interconnect2_onprem_dc Name of the on premisses data center used in the creation of the Interconnect for the second location of region1. string n/a yes
region1_interconnect2_vlan_tag8021q The IEEE 802.1Q VLAN tag for this attachment, in the range 2-4094. string null no
region1_router1_name Name of the Router 1 for Region 1 where the attachment resides. string n/a yes
region1_router2_name Name of the Router 2 for Region 1 where the attachment resides. string n/a yes
region2 Second subnet region. The Dedicated Interconnect module only configures two regions. string n/a yes
region2_interconnect1 URL of the underlying Interconnect object that this attachment's traffic will traverse through. string n/a yes
region2_interconnect1_candidate_subnets Up to 16 candidate prefixes that can be used to restrict the allocation of cloudRouterIpAddress and customerRouterIpAddress for this attachment. All prefixes must be within link-local address space (169.254.0.0/16) and must be /29 or shorter (/28, /27, etc). list(string) null no
region2_interconnect1_location Name of the interconnect location used in the creation of the Interconnect for the first location of region2 string n/a yes
region2_interconnect1_onprem_dc Name of the on premisses data center used in the creation of the Interconnect for the first location of region2. string n/a yes
region2_interconnect1_vlan_tag8021q The IEEE 802.1Q VLAN tag for this attachment, in the range 2-4094. string null no
region2_interconnect2 URL of the underlying Interconnect object that this attachment's traffic will traverse through. string n/a yes
region2_interconnect2_candidate_subnets Up to 16 candidate prefixes that can be used to restrict the allocation of cloudRouterIpAddress and customerRouterIpAddress for this attachment. All prefixes must be within link-local address space (169.254.0.0/16) and must be /29 or shorter (/28, /27, etc). list(string) null no
region2_interconnect2_location Name of the interconnect location used in the creation of the Interconnect for the second location of region2 string n/a yes
region2_interconnect2_onprem_dc Name of the on premisses data center used in the creation of the Interconnect for the second location of region2. string n/a yes
region2_interconnect2_vlan_tag8021q The IEEE 802.1Q VLAN tag for this attachment, in the range 2-4094. string null no
region2_router1_name Name of the Router 1 for Region 2 where the attachment resides. string n/a yes
region2_router2_name Name of the Router 2 for Region 2 where the attachment resides string n/a yes
vpc_name Label to identify the VPC associated with shared VPC that will use the Interconnect. string n/a yes

Outputs

Name Description
interconnect_attachment1_region1 The interconnect attachment 1 for region 1
interconnect_attachment1_region1_customer_router_ip_address IPv4 address + prefix length to be configured on the customer router subinterface for this interconnect attachment.
interconnect_attachment1_region2 The interconnect attachment 1 for region 2
interconnect_attachment1_region2_customer_router_ip_address IPv4 address + prefix length to be configured on the customer router subinterface for this interconnect attachment.
interconnect_attachment2_region1 The interconnect attachment 2 for region 1
interconnect_attachment2_region1_customer_router_ip_address IPv4 address + prefix length to be configured on the customer router subinterface for this interconnect attachment.
interconnect_attachment2_region2 The interconnect attachment 2 for region 2
interconnect_attachment2_region2_customer_router_ip_address IPv4 address + prefix length to be configured on the customer router subinterface for this interconnect attachment.