Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat(eos_designs): Support for IPv6 in underlay with RFC5549 #1723

Merged
merged 18 commits into from
May 6, 2022

Conversation

xaviramon
Copy link
Contributor

Change Summary

PR required to make #1719 work. Underlay supports IPv6 with RFC5549 and transport of IPv4 VTEP addresses

Related Issue(s)

Fixes #

Component(s) name

arista.avd. eos_designs

Proposed changes

Create new peer-groups for IPv6 AFs
Generate AFs as required
Modify PL and RM to support IPv6 addressing

How to test

molecule

Checklist

User Checklist

  • N/A

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)

@xaviramon xaviramon requested a review from a team as a code owner April 13, 2022 16:04
@github-actions github-actions bot added role: eos_designs issue related to eos_designs role state: CI Updated CI scenario have been updated in the PR state: Documentation role Updated labels Apr 13, 2022
Copy link
Contributor

@ClausHolbechArista ClausHolbechArista left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you are doing too many changes to ipv4 things in here. Basically you should just be adding IPv6 AF for the existing underlay protocol. It should not change everything else.
If someone wants to use different peer-group names, they can just set the names on the existing keys.
Also since you are not removing IPv4, the new name with IPv6 is just as wrong as the IPv4 name.
I suggest to simplify this PR, to just add the underlay AF, loopback, PL etc, and then leave the naming as it is. We can add a new - more neutral - underlay_peers and mlag_underlay_peer later (separate PR)

@ClausHolbechArista
Copy link
Contributor

Also the requirement for rfc5549 is not clear to me. It should just work for regular ibgp/ebgp also right? I understand it will not work for OSPF/ISIS as part of this PR, but I think those are already covered by Emil in the MPLS design.

@github-actions github-actions bot added the state: conflict PR with conflict label Apr 25, 2022
@github-actions
Copy link

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

@github-actions
Copy link

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

@github-actions github-actions bot removed the state: conflict PR with conflict label Apr 26, 2022
@ClausHolbechArista ClausHolbechArista changed the title Feat(eos_designs): Support for IPv6 underlay with RFC5549 with IPv4 VTEP addresses Feat(eos_designs): Support for IPv6 in underlay with RFC5549 Apr 26, 2022
@onurgashi
Copy link
Contributor

LGTM!

@ClausHolbechArista ClausHolbechArista merged commit 33dad45 into aristanetworks:devel May 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
role: eos_designs issue related to eos_designs role state: CI Updated CI scenario have been updated in the PR state: Documentation role Updated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants