Transit Gateway: Adding new connection type Redundant GRE to the transite gateway #5433
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Enhancement:
To build in redundancy and eliminate the need to schedule an outage when a TGR needs to goes down for maintenance, there will be a new connection type named Redundant GRE which is essentially a grouping of at least 2 Unbound GRE Tunnels. This will allow GRE Tunnels to be placed onto different devices in the same zone and not flag overlapping routes that are in the Redundant GRE tunnels.
Tunnels under Redundant GREs are Unbound GRE Tunnels that can connect to classic or VPC networks. For this document, Unbound GRE Tunnels under a Redundant GRE will be referred to as a Redundant GRE tunnel to make the distinction from stand-alone Unbound GRE Tunnels.
Below are the resources modified
ibm_tg_connection. -> resource Block
ibm_tg_gateway. ->data Block
Below are the resources newly added resource block
ibm_tg_connection_rgre_tunnel