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): Inject default VRF policy with a match-all statement when missing #3560

Merged

Conversation

gmuloc
Copy link
Contributor

@gmuloc gmuloc commented Jan 29, 2024

Change Summary

In the current implementation, when there is no policy defined under wan_virtual_topology.vrfs for VRF default. AVD will raise an error.

This PR replaces this behavior with auto configuring a policy with one default statement (default_virtual_topology) matching all local path_groups in the load balance policy.

Of course, because it is VRF default, the Control plane special virtual topology is still injected.

Component(s) name

arista.avd.eos_designs

Proposed changes

When the VRF default is missing from wan_virtual_topology.vrfs, AVD creates a policy called DEFAULT-AVT-POLICY that is configured with one default statement to match all traffic using all locally available path-groups

How to test

molecule updated to test it in AutoVPN use case.

Checklist

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)

@gmuloc gmuloc requested review from a team as code owners January 29, 2024 11:05
@github-actions github-actions bot added state: CI Updated CI scenario have been updated in the PR role: eos_designs issue related to eos_designs role labels Jan 29, 2024
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.

The logic becomes increasingly hard to follow. More comments in the code might help.

@ClausHolbechArista ClausHolbechArista requested a review from a team January 30, 2024 20:07
@ClausHolbechArista ClausHolbechArista added the one approval This PR has one approval and is only missing one more. label Jan 30, 2024
Copy link
Member

@carlbuchmann carlbuchmann left a comment

Choose a reason for hiding this comment

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

LGTM, works as expected in test topology

@carlbuchmann carlbuchmann removed the one approval This PR has one approval and is only missing one more. label Feb 1, 2024
@carlbuchmann carlbuchmann merged commit 8fed1a3 into aristanetworks:devel Feb 1, 2024
38 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants