Skip to content

Add optional Hub label for tunnel naming#32

Merged
dmitryperets merged 2 commits intorelease/7.4from
feature/hub_name
Nov 28, 2024
Merged

Add optional Hub label for tunnel naming#32
dmitryperets merged 2 commits intorelease/7.4from
feature/hub_name

Conversation

@dmitryperets
Copy link
Member

@dmitryperets dmitryperets commented Nov 22, 2024

The default naming convention for the tunnels generated on the Spokes is:

H<hub_index>_<ol_type>

For example, for a Dual-Hub topology we will generate tunnels like H1_INET and H2_INET.

To simplify operations, we introduce an option to set a more meaningful label for each Hub, using an optional hub_name parameter in the hubs structure:

{# Hubs #}
{% set hubs = {

    'site1-H1': {
      'lo_bgp': '10.200.1.253',
      'hub_name': 'TRN',          <<<<<<
      'overlays': {
         ...

If this option is defined, the naming convention will be:

<hub_name>_<ol_type>

In other words: TRN_INET.

Similarly, this optional name will be used for the Hub-to-Hub tunnels in a multi-regional deployment (e.g. EAST_TRN_INET).

@dmitryperets dmitryperets self-assigned this Nov 22, 2024
@dmitryperets dmitryperets added the enhancement New feature or request label Nov 22, 2024
@dmitryperets dmitryperets merged commit f7a64f5 into release/7.4 Nov 28, 2024
@dmitryperets dmitryperets deleted the feature/hub_name branch November 28, 2024 10:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant