Test plan for Distributed VoQ architecture #2659
Merged
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
|
|
wangxin
reviewed
Jan 4, 2021
wangxin
approved these changes
Jan 5, 2021
|
Eswaran (Arista) - could you please review, thanks. |
tarundeepsharma88
approved these changes
Feb 5, 2021
|
@wangxin can this be merged? We have the next set of VoQ TCs ready to be pushed. But it's in the same file. Hence there's a dependency. |
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 # (issue)
Type of change
Approach
What is the motivation for this PR?
Creating test plan and cases for validating the design of the distributed VoQ architecture HLD
How did you do it?
Based on the code changes in the associated PRs
How did you verify/test it?
N/A
Any platform specific information?
This is only applicable for distributed VoQ systems.
Supported testbed topology if it's a new test case?
Only T2 topology as mentioned in #2638
Documentation