Feat(eos_designs): Add WAN interface configuration under l3_edge.l3_interfaces

[gmuloc]

Change Summary

• Add support for wan interfaces keys
• Add documentation

Component(s) name

arista.avd.eos_designs

Proposed changes

• Add the following keys for the l3_edge.l3_interfaces:

  l3_interfaces:

      # PREVIEW: This key is currently not supported

      # The WAN path-group this interface is connected to.
      wan_path_group: <str>

      # PREVIEW: This key is currently not supported

      # The WAN Carrier this interface is connected to.
      # This is not rendered in the configuration but used for WAN designs.
      wan_carrier: <str>

      # PREVIEW: This key is currently not supported

      # The WAN Circuit ID for this interface.
      # This is not rendered in the configuration but used for WAN designs.
      wan_circuit_id: <str>

      # PREVIEW: This key is currently not supported

      # For a WAN interface (`wan_path_group` is set), allow to disable the static tunnel towards Pathfinders.
      # Default True.
      connected_to_pathfinder: <bool>

• Add logic to generate the path-groups, stun profiles, and bgp related config

How to test

molecule test

Checklist

User Checklist

• Build path-groups
• Build Stun
• Support connected_to_pathfinder key

Future work

• Add a key under wan interfaces to specify a public IP when the IP is DHCP - needed for WAN route servers (supported today via the wan_route_servers.path_groups.interfaces.ip_address)
• Add auto path-group ID generation (today required to set it via input)
• Handle ipsec / ip_local under dynamic peers in path-groups
• Ability to add static routes for a WAN interface (different from the default route)
• Implement support for "import path_group" statements once it is available in CLI
• Move interfaces under nodes
• Revisit stun.client.server_profiles names

Repository Checklist

• My code has been rebased from devel before I start
• I have read the CONTRIBUTING document.
• My change requires a change to the documentation and documentation have been updated accordingly.
• I have updated molecule CI testing accordingly. (check the box if not applicable)

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[github-actions]

Conflicts have been resolved. A maintainer will review the pull request shortly.