Test Plan for Chassis/Multi-ASIC GCU#16905
Conversation
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
| /localhost/DEVICE_NEIGHBOR_METADATA | ||
| /localhost/INTERFACE | ||
| /localhost/PORTCHANNEL_INTERFACE | ||
| /localhost/PORTCHANNEL_MEMBER |
There was a problem hiding this comment.
why do we need localhost change in add cluster scenario?
|
|
||
| ### Key Changes | ||
| 1. Multi-ASIC Adaptation: | ||
| Test cases have been adapted to use a fixture that returns a random ASIC namespace for verification. |
There was a problem hiding this comment.
We have submitted a PR to address the add cluster: #17744. The test plan doc could adjust a little bit to align with the real case.
|
do we need this PR ? @okaravasi as I see this testplan already included in #14887 |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
@okaravasi wondering if review comments are addressed? let us know when it's ready to be re-review again |
|
@vperumal can you please review this at priority @kenneth-arista please see if someone can review. |
judyjoseph
left a comment
There was a problem hiding this comment.
LGTM for the basic tests for Add cluster. We would need to enhance with more traffic tests when we update the cable length/buffer-profile etc
Signed-off-by: opcoder0 <[email protected]>
Signed-off-by: Guy Shemesh <[email protected]>
Signed-off-by: Aharon Malkin <[email protected]>
Signed-off-by: Guy Shemesh <[email protected]>
Signed-off-by: Guy Shemesh <[email protected]>
Signed-off-by: Yael Tzur <[email protected]>
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation