support t1-isolated-d56u2 in test_acl.py, test_stress_acl.py and test_qos_sai#18444
Merged
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sdszhang
changed the title
r12f
reviewed
May 17, 2025
r12f
reviewed
May 17, 2025
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sdszhang
commented
May 18, 2025
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sdszhang
added
Request for msft-202412 Branch
and removed
Request for msft-202412 Branch
Cherry Pick Conflict_msft-202412
labels
11 tasks
Collaborator
|
Cherry-pick PR to msft-202412: Azure/sonic-mgmt.msft#305 |
r12f
reviewed
May 27, 2025
|
|
||
| dst_ip_addr = None | ||
| if tbinfo["topo"]['name'] == "t1-isolated-d28u1": | ||
| if tbinfo["topo"]['name'] in ["t1-isolated-d28u1", "t1-isolated-d56u2", "t1-isolated-d448u16"]: |
sdszhang
added a commit
to sdszhang/sonic-mgmt
that referenced
this pull request
Jun 30, 2025
…_qos_sai (sonic-net#18444) What is the motivation for this PR? Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai How did you do it? Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai How did you verify/test it? Ran on physical testbed. (cherry picked from commit 33b6673)
11 tasks
yejianquan
pushed a commit
that referenced
this pull request
Jul 1, 2025
…changes (#19254) * update t1-isolated-d56u2 topo with port-channel (#18152) Description of PR Summary: update t1-isolated-d56u2 to use port-channel for upstream neighbor. (cherry picked from commit b288741) * revert topo change in #18152 and add t1-isolated-lag topo (#18683) What is the motivation for this PR? use new name for t1-isolated topo with upstream port-channel. (cherry picked from commit af6a539) * support t1-isolated-d56u2 in test_acl.py, test_stress_acl.py and test_qos_sai (#18444) What is the motivation for this PR? Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai How did you do it? Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai How did you verify/test it? Ran on physical testbed. (cherry picked from commit 33b6673) * Add t1-isolated-d56u1-lag into support list. (#18826) What is the motivation for this PR? Add t1-isolated-d56u1-lag into support list How did you do it? How did you verify/test it? Run on physical testbed. (cherry picked from commit 460e375) * copy generate_topo.py over.
Collaborator
|
@sdszhang PR conflicts with 202505 branch |
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
…_qos_sai (sonic-net#18444) What is the motivation for this PR? Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai How did you do it? Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai How did you verify/test it? Ran on physical testbed. Signed-off-by: opcoder0 <110003254+opcoder0@users.noreply.github.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
…_qos_sai (sonic-net#18444) What is the motivation for this PR? Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai How did you do it? Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai How did you verify/test it? Ran on physical testbed. Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
…_qos_sai (sonic-net#18444) What is the motivation for this PR? Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai How did you do it? Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai How did you verify/test it? Ran on physical testbed. Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
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
5 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:
Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai
Type of change
Back port request
Approach
What is the motivation for this PR?
Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai
How did you do it?
Add t1-isolated-d56u2 topo support into test_acl.py, test_stress_acl.py and test_qos_sai
How did you verify/test it?
Ran on physical testbed.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation