updating the testplan to include the new test case and metrics measur… #21437
Conversation
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
Collaborator
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
10 tasks
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 # (issue)
This test plan update is to add a test case to see if control/data plane can handle the flapping of numerous admin BGP session holding a lot routes, and estimate the impact on it.
We also introduce route programming timing measurement.
Related PRs:
Type of change
Back port request
Approach
What is the motivation for this PR?
Update the test plan documents with methodology and details of the new test plan.
How did you do it?
How did you verify/test it?
Any platform specific information?
Ran the tests on t0-isolated-d2u510s2 topology
Supported testbed topology if it's a new test case?
Documentation