Skip to content

revert topo change in #18152 and add t1-isolated-lag topo#18683

Merged
StormLiangMS merged 2 commits intosonic-net:masterfrom
sdszhang:th5_topo_revert
May 29, 2025
Merged

revert topo change in #18152 and add t1-isolated-lag topo#18683
StormLiangMS merged 2 commits intosonic-net:masterfrom
sdszhang:th5_topo_revert

Conversation

@sdszhang
Copy link
Contributor

Description of PR

Summary:
As discussed, revert topo change in #18152 and use a different topo name for t1-isolated-lag topo which has upstream port-channel.

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
    • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202205
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505

Approach

What is the motivation for this PR?

use new name for t1-isolated topo with upstream port-channel.

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

@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@sdszhang
Copy link
Contributor Author

manual cherry-pick 202412: Azure/sonic-mgmt.msft#338

Copy link
Collaborator

@StormLiangMS StormLiangMS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@StormLiangMS StormLiangMS merged commit af6a539 into sonic-net:master May 29, 2025
21 checks passed
StormLiangMS added a commit to Azure/sonic-mgmt.msft that referenced this pull request May 29, 2025
…ag topo (#338)

<!--
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:
As discussed, revert topo change in #18152 and use a different topo name
for t1-isolated-lag topo which has upstream port-channel.

cherry-pick sonic-net/sonic-mgmt#18683 into
202412

### Type of change

<!--
- Fill x for your type of change.
- e.g.
- [x] Bug fix
-->

- [ ] Bug fix
- [ ] Testbed and Framework(new/improvement)
- [ ] New Test case
    - [ ] Skipped for non-supported platforms
- [ ] Test case improvement


### Back port request
- [ ] 202205
- [ ] 202305
- [ ] 202311
- [ ] 202405
- [ ] 202411
- [x] 202505

### Approach
#### What is the motivation for this PR?
use new name for t1-isolated topo with upstream port-channel.

#### 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
<!--
(If it's a new feature, new test case)
Did you update documentation/Wiki relevant to your implementation?
Link to the wiki page?
-->
@mssonicbld
Copy link
Collaborator

@sdszhang PR conflicts with 202505 branch

bachalla pushed a commit to bachalla/sonic-mgmt that referenced this pull request Jun 2, 2025
…onic-net#18683)

What is the motivation for this PR?
use new name for t1-isolated topo with upstream port-channel.
sdszhang added a commit to sdszhang/sonic-mgmt that referenced this pull request Jun 30, 2025
…onic-net#18683)

What is the motivation for this PR?
use new name for t1-isolated topo with upstream port-channel.

(cherry picked from commit af6a539)
Xichen96 pushed a commit to Xichen96/sonic-mgmt that referenced this pull request Jun 30, 2025
…and add t1-isolated-lag topo (sonic-net#18683)

revert topo change in sonic-net#18152 and add t1-isolated-lag topo (sonic-net#18683)

What is the motivation for this PR?
use new name for t1-isolated topo with upstream port-channel.

(cherry picked from commit af6a539)
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.
opcoder0 pushed a commit to opcoder0/sonic-mgmt that referenced this pull request Dec 8, 2025
…onic-net#18683)

What is the motivation for this PR?
use new name for t1-isolated topo with upstream port-channel.

Signed-off-by: opcoder0 <[email protected]>
AharonMalkin pushed a commit to AharonMalkin/sonic-mgmt that referenced this pull request Dec 16, 2025
…onic-net#18683)

What is the motivation for this PR?
use new name for t1-isolated topo with upstream port-channel.

Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2 pushed a commit to gshemesh2/sonic-mgmt that referenced this pull request Dec 21, 2025
…onic-net#18683)

What is the motivation for this PR?
use new name for t1-isolated topo with upstream port-channel.

Signed-off-by: Guy Shemesh <[email protected]>
venu-nexthop pushed a commit to venu-nexthop/sonic-mgmt that referenced this pull request Jan 13, 2026
…onic-net#18683)

What is the motivation for this PR?
use new name for t1-isolated topo with upstream port-channel.
gshemesh2 pushed a commit to gshemesh2/sonic-mgmt that referenced this pull request Jan 26, 2026
…onic-net#18683)

What is the motivation for this PR?
use new name for t1-isolated topo with upstream port-channel.

Signed-off-by: Guy Shemesh <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants