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): Add more granular settings for flow_tracking #3776

Merged
merged 9 commits into from
Apr 23, 2024

Conversation

ayushmittal-arista
Copy link
Contributor

Change Summary

Enable flow_tracking for multiple interface types and follow design conventions of sflow

Related Issue(s)

Fixes #

Component(s) name

arista.avd.eos_designs

Proposed changes

Change format for flow_tracking_settings to accept multiple trackers, instead of just override settings.

Add fabric_flow_tracking to add toggle for enabling flow tracking on various link types with an option to specify a tracker if want to override. By default, we will add hardware type named FLOW-TRACKER., with some default settings. To override this you will need to specify full block of settings.

Add flow_tracking option at per interface level which can override enable/ tracker type and name.

How to test

molecule
TODO: Add test after data model is approved.

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)

Copy link

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

@github-actions github-actions bot removed the state: conflict PR with conflict label Mar 28, 2024
Copy link

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

@ClausHolbechArista ClausHolbechArista marked this pull request as draft April 10, 2024 06:35
@ayushmittal-arista ayushmittal-arista marked this pull request as ready for review April 15, 2024 19:56
Copy link

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

@github-actions github-actions bot added the state: conflict PR with conflict label Apr 17, 2024
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 19, 2024
@github-actions github-actions bot added the role: eos_cli_config_gen issue related to eos_cli_config_gen role label Apr 22, 2024
Copy link
Contributor

@gmuloc gmuloc left a comment

Choose a reason for hiding this comment

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

LGTM once CI is rebuilt after pre-commit trigger

thanks for this @ayushmittal-arista

lets see if we remove the PREVIEW from the model before we merge @ClausHolbechArista

@gmuloc
Copy link
Contributor

gmuloc commented Apr 23, 2024

Thanks @ayushmittal-arista !

@gmuloc gmuloc merged commit a82a1b5 into aristanetworks:devel Apr 23, 2024
40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EPIC - AVD AutoVPN/WAN rn: Feat(eos_designs) role: eos_cli_config_gen issue related to eos_cli_config_gen role 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.

None yet

3 participants