Announce vips routes for bgp_multipath_relax testing#1692
Merged
lguohan merged 1 commit intosonic-net:masterfrom May 21, 2020
wangxin:vips-routes-pr
Merged
Announce vips routes for bgp_multipath_relax testing#1692lguohan merged 1 commit intosonic-net:masterfrom wangxin:vips-routes-pr
lguohan merged 1 commit intosonic-net:masterfrom
wangxin:vips-routes-pr
Conversation
Previously the vips routes were statically configured in the VMs for bgp_multipath_relax testing. After the change of announcing routes from exabgp in PTF to VMs, the vips routes were missing. The bgp_multipath_relax testing depends on the vips routes failed. This change is to announce the vips routes to VMs that have the vips routes configuration. The functions in the fib fixture definition file were refactored a little bit. Signed-off-by: Xin Wang <[email protected]>
3 tasks
|
This pull request introduces 2 alerts when merging a2b4fc7 into f17471c - view on LGTM.com new alerts:
|
lguohan
reviewed
May 21, 2020
| routes_vips = [] | ||
| for prefix in v["vips"]["ipv4"]["prefixes"]: | ||
| routes_vips.append((prefix, local_ip, v["vips"]["ipv4"]["asn"])) | ||
| announce_routes(ptfip, port, routes_vips) |
Contributor
There was a problem hiding this comment.
I am not sure we want to advertise to every tor about the vip. I remember topology has information which tor needs to advertise the vip.
Collaborator
Author
There was a problem hiding this comment.
This will not advertise to every tor. It will only advertise to tor VMs that have configuration "vips" in topology definition file.
For example, in ansible/vars/topo_t1-lag.yml, only two VMs have the "vips" configuration: ARISTA01T0, ARISTA03T0.
ARISTA01T0:
properties:
- common
- tor
tornum: 1
bgp:
asn: 64001
peers:
65100:
- 10.0.0.32
- FC00::41
interfaces:
Loopback0:
ipv4: 100.1.0.17/32
ipv6: 2064:100::11/128
Ethernet1:
ipv4: 10.0.0.33/31
ipv6: fc00::42/126
bp_interface:
ipv4: 10.10.246.17/24
ipv6: fc0a::22/64
vips:
ipv4:
prefixes:
- 200.0.1.0/26
asn: 64700
ARISTA03T0:
properties:
- common
- tor
tornum: 3
bgp:
asn: 64003
peers:
65100:
- 10.0.0.36
- FC00::49
interfaces:
Loopback0:
ipv4: 100.1.0.19/32
ipv6: 2064:100::13/128
Ethernet1:
ipv4: 10.0.0.37/31
ipv6: fc00::4a/126
bp_interface:
ipv4: 10.10.246.19/24
ipv6: fc0a::26/64
vips:
ipv4:
prefixes:
- 200.0.1.0/26
asn: 64700
The vips routes will only be advertised to these two tor VMs.
lguohan
approved these changes
May 21, 2020
3 tasks
lguohan
pushed a commit
that referenced
this pull request
May 22, 2020
#1697) I used wrong port for announcing IPv6 routes in PR #1692. This PR is to fix that issue. Signed-off-by: Xin Wang <[email protected]>
shlomibitton
pushed a commit
to Junchao-Mellanox/sonic-mgmt
that referenced
this pull request
Jul 12, 2020
commit d79d500 Author: Xin Wang <[email protected]> Date: Sat May 23 11:31:48 2020 +0800 Fix acl testing for new t1 routes (sonic-net#1688) The t1 and t1-lag routes have been changed after replacing static routes on VM with exabgp announced routes. This caused the acl testing failed. This PR is to fix this issue reported in sonic-net#1603. Changes: 1. Update the acl rules template to use new IP addresses 2. Update the acl script to use new IP addresses Signed-off-by: Xin Wang <[email protected]> commit c84e699 Author: yvolynets-mlnx <[email protected]> Date: Sat May 23 04:41:19 2020 +0300 [pytest/ntp] Minor fix for NTP test case. (sonic-net#1698) Added verification of 'wait_until' result, to easier understand test case failure reason. Signed-off-by: Yuriy Volynets <[email protected]> commit 441ddfa Author: Vitaliy Senchyshyn <[email protected]> Date: Sat May 23 00:40:02 2020 +0300 [wr_arp][pytest] Fixed wr_arp test (sonic-net#1695) * [wr_arp] Fixed wr_arp test Signed-off-by: Vitaliy Senchyshyn <[email protected]> * Make show ip protocol command working for different sonic images * Fixed review comments * Made records variable a class memeber * Fixed DIP taking from ip route show for sonic master commit abdb746 Author: Xin Wang <[email protected]> Date: Fri May 22 18:45:56 2020 +0800 [pytest/fib]: Fix the issue of using wrong port announcing IPv6 routes (sonic-net#1697) I used wrong port for announcing IPv6 routes in PR sonic-net#1692. This PR is to fix that issue. Signed-off-by: Xin Wang <[email protected]> commit 9e52bba Author: lguohan <[email protected]> Date: Fri May 22 03:45:14 2020 -0700 [pytest/snmp_cpu]: query nproc when ansible facts does not have vcpu info (sonic-net#1693) sometimes, ansible facts does not gather vcpu information. in this case, use nproc to query the cpu number directly. Signed-off-by: Guohan Lu <[email protected]> commit b175f8f Author: yvolynets-mlnx <[email protected]> Date: Fri May 22 02:49:30 2020 +0300 [pytest/test_drop_counters.py] Fixed IGMP test case (sonic-net#1624) Signed-off-by: Yuriy Volynets <[email protected]> commit 208d02a Author: Xin Wang <[email protected]> Date: Fri May 22 00:23:19 2020 +0800 Announce vips routes for bgp_multipath_relax testing (sonic-net#1692) Previously the vips routes were statically configured in the VMs for bgp_multipath_relax testing. After the change of announcing routes from exabgp in PTF to VMs, the vips routes were missing. The bgp_multipath_relax testing depends on the vips routes failed. This change is to announce the vips routes to VMs that have the vips routes configuration. The functions in the fib fixture definition file were refactored a little bit. Signed-off-by: Xin Wang <[email protected]> commit 6d7498f Author: yvolynets-mlnx <[email protected]> Date: Thu May 21 11:38:08 2020 +0300 Fixed fib tests: test_hash_ipv4/test_hash_ipv6 (sonic-net#1683) Fixes sonic-net#1679 Signed-off-by: Yuriy Volynets <[email protected]> commit f17471c Author: Neetha John <[email protected]> Date: Wed May 20 15:53:44 2020 -0700 Qos SAI test restructure (sonic-net#1682) * Qos SAI test restructure Signed-off-by: Neetha John <[email protected]> commit 87f3a23 Author: Joe LeVeque <[email protected]> Date: Wed May 20 10:42:22 2020 -0700 [pytest][cacl] Remove unused 'testbed_devices' from parameters (sonic-net#1689) commit bd6e135 Author: Ying Xie <[email protected]> Date: Wed May 20 08:11:55 2020 -0700 [reload config] redirect reload config output to /dev/null (sonic-net#1687) config reload command will restart interface-config service, which will reset eth0. Which will reset the connection issues config reload if the output is coming to stdio/stderr. It in turn could cause the pytest to stuck for long time. Signed-off-by: Ying Xie <[email protected]> Signed-off-by: Stepan Blyschak <[email protected]>
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
…tically (#24551) #### Why I did it src/sonic-sairedis ``` * 45bf5582 - (HEAD -> 202411, origin/202411) migrate agent pool from sonicbld-arm64 to sonicso1ES-arm64, and sonicbld-armhf to sonicso1ES-armhf for branch 202411 (sonic-net#1692) (3 weeks ago) [yijingyan2] ``` #### How I did it #### How to verify it #### Description for the changelog
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
Fixes #1587
Previously the vips routes were statically configured in the VMs for
bgp_multipath_relax testing. After the change of announcing
routes from exabgp in PTF to VMs, the vips routes were missing.
The bgp_multipath_relax testing depends on the vips routes failed.
This change is to announce the vips routes to VMs that have the
vips routes configuration. The functions in the fib fixture definition
file were refactored a little bit.
Type of change
Approach
How did you do it?
Updated the fib fixture to announce vips routes to VMs that have this configuration in topology definition.
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation