[action] [PR:15748] [testbed] announce routes with routes generation switch, aggregate routes and variable ipv6 address pattern #28
Conversation
This file contains 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
…utes and variable ipv6 address pattern <!-- Please make sure you've read and understood our contributing guidelines; https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md Please provide following information to help code review process a bit easier: --> ### Description of PR <!-- - Please include a summary of the change and which issue is fixed. - Please also include relevant motivation and context. Where should reviewer start? background context? - List any dependencies that are required for this change. --> Summary: In this PR, we added new features to make announce routes script more powerful. 1. Variable ipv6 address pattern, previously, we are hardcoding ipv6 prefix with pattern 20%02X:%02X%02X:0:%02X::/64, now, it can be set in script or topology file. 2. Selectable exabgp setting up and routes generation. now we can add flag in topology file to enable ipv4 or ipv6, or disable ipv4 or ipv6. 3. Aggregated routes on peers. At the VM definition in topology file, we now support define aggregate route on the VM. ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [ ] Bug fix - [x] Testbed and Framework(new/improvement) - [ ] Test case(new/improvement) ### Back port request - [ ] 202012 - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 ### Approach #### What is the motivation for this PR? To make route announcement more powerful. #### How did you do it? Add routes generation switch, aggregate routes and variable ipv6 address pattern #### How did you verify/test it? Verified on 7215 testbed with t0 and t1 topologies. #### Any platform specific information? #### Supported testbed topology if it's a new test case? ### Documentation <!-- (If it's a new feature, new test case) Did you update documentation/Wiki relevant to your implementation? Link to the wiki page? -->
|
Original PR: sonic-net/sonic-mgmt#15748 |
|
/azp run |
8 tasks
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:
In this PR, we added new features to make announce routes script more powerful.
Type of change
Back port request
Approach
What is the motivation for this PR?
To make route announcement more powerful.
How did you do it?
Add routes generation switch, aggregate routes and variable ipv6 address pattern
How did you verify/test it?
Verified on 7215 testbed with t0 and t1 topologies.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation