-
Notifications
You must be signed in to change notification settings - Fork 220
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
Fix(eos_designs): Do not filter AVT on HA device if one path-group is present on peer #4463
Fix(eos_designs): Do not filter AVT on HA device if one path-group is present on peer #4463
Conversation
Review docs on Read the Docs To test this pull request: # Create virtual environment for this testing below the current directory
python -m venv test-avd-pr-4463
# Activate the virtual environment
source test-avd-pr-4463/bin/activate
# Install all requirements including PyAVD
pip install "pyavd[ansible] @ git+https://github.com/gmuloc/avd.git@fix-path-groups-ha-peers#subdirectory=python-avd" --force
# Point Ansible collections path to the Python virtual environment
export ANSIBLE_COLLECTIONS_PATH=$VIRTUAL_ENV/ansible_collections
# Install Ansible collection
ansible-galaxy collection install git+https://github.com/gmuloc/avd.git#/ansible_collections/arista/avd/,fix-path-groups-ha-peers --force
# Optional: Install AVD examples
cd test-avd-pr-4463
ansible-playbook arista.avd.install_examples |
for more information, see https://pre-commit.ci
python-avd/pyavd/_eos_designs/structured_config/network_services/utils.py
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Change Summary
Until now, AVD is filtering completely a VT if none of the path-group listed is present locally,
This works as expected but there is one use case where this breaks potential connectivity:
Consider an HA site with two routers,
router1
connected to INET only androuter2
connected to MPLS only.If some matched traffic is configured to be sent only on MPLS (let's say voice), then AVD would not generate the profile on
router1
for this MPLS only traffic.When traffic for voice reaches
router1
, it will not be matched correctly and may be matched in one of the next application profile, default, or if no default is present, could be dropped.The correct behavior is to configure the profile targeting a load-balance policy containing only the LAN_HA path-group so that the traffic can be sent to the peer and forwarded out of MPLS.
Related Issue(s)
Reported during testing by AVD maintainers
Component(s) name
arista.avd.eos_designs
Proposed changes
This PR adds a check where if for a given VT, no path-group is present locally but any path-group is present on the HA peer, then AVD will now generate a load-balancing policy with only the
LAN_HA
path group and will generate the profile.How to test
Molecule - some molecule tests were already demonstrating this.
Checklist
Repository Checklist