README.md

Partner Interconnect module

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

Prerequisites

1. Provisioning of four VLAN attachments in the Hub project in the specified environment. That would be the prj-c-{base|restricted}-net-hub under the folder fldr-common in case of Hub and Spoke architecture.

Without Hub and Spoke enabled VLAN attachments will be created in prj-{p|n|d}-shared-{base|restricted} under corresponding environment's folder.

Usage

1. Rename partner_interconnect.tf.example to partner_interconnect.tf in the environment folder in 3-networks-hub-and-spoke/modules/base_env .
2. Update the enable_partner_interconnect to true in each main.tf file in the environment folder in 3-networks-hub-and-spoke/envs/<environment> .
3. Update the file partner_interconnect.tf with values that are valid for your environment for the VLAN attachments, locations.

Inputs

Name	Description	Type	Default	Required
attachment_project_id	the Interconnect project ID.	string	n/a	yes
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
preactivate	Preactivate Partner Interconnect attachments, works only for level3 Partner Interconnect	string	false	no
region1	First subnet region. The Partner Interconnect module only configures two regions.	string	n/a	yes
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_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_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 Partner Interconnect module only configures two regions.	string	n/a	yes
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_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_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
vpc_type	To which Shared VPC Host attach the Partner Interconnect - base/restricted	string	null	no

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.