Add TH-512 topo: t0-isolated, t1-isolated#17642
Merged
StormLiangMS merged 3 commits intosonic-net:masterfrom Mar 24, 2025
Merged
Add TH-512 topo: t0-isolated, t1-isolated#17642StormLiangMS merged 3 commits intosonic-net:masterfrom
StormLiangMS merged 3 commits intosonic-net:masterfrom
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
@r12f for review. |
# Conflicts: # ansible/generate_topo.py
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
r12f
approved these changes
Mar 24, 2025
sdszhang
added
Request for msft-202412 Branch
and removed
Cherry Pick Conflict_msft-202412
Request for msft-202412 Branch
labels
Collaborator
|
Cherry-pick PR to msft-202412: Azure/sonic-mgmt.msft#168 |
amulyan7
pushed a commit
to amulyan7/sonic-mgmt
that referenced
this pull request
Mar 31, 2025
Description of PR Summary: add the following topology: ansible/vars/topo_t0-isolated-d256u256s2.yml ansible/vars/topo_t0-isolated-d32u32s2.yml ansible/vars/topo_t1-isolated-d448u16.yml ansible/vars/topo_t1-isolated-d56u2.yml
11 tasks
OriTrabelsi
pushed a commit
to OriTrabelsi/sonic-mgmt
that referenced
this pull request
Apr 1, 2025
Description of PR Summary: add the following topology: ansible/vars/topo_t0-isolated-d256u256s2.yml ansible/vars/topo_t0-isolated-d32u32s2.yml ansible/vars/topo_t1-isolated-d448u16.yml ansible/vars/topo_t1-isolated-d56u2.yml
nhe-NV
pushed a commit
to nhe-NV/sonic-mgmt
that referenced
this pull request
May 12, 2025
<!-- 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: Add the new topologies in sonic-net#17642 and sonic-net#17599 into the supported veos topologies list: ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [x] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [ ] Test case improvement ### Back port request - [ ] 202012 - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 ### Approach #### What is the motivation for this PR? Add the topologies into the supported list. #### How did you do it? #### How did you verify/test it? run add-topo on a physical testbed. #### 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? -->
nhe-NV
pushed a commit
to nhe-NV/sonic-mgmt
that referenced
this pull request
May 12, 2025
…ic-net#180) <!-- 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: Add the new topologies in sonic-net#17642 and sonic-net#17599 into the supported veos topologies list: ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [x] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [ ] Test case improvement ### Back port request - [ ] 202012 - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 ### Approach #### What is the motivation for this PR? Add the topologies into the supported list. #### How did you do it? #### How did you verify/test it? run add-topo on a physical testbed. #### 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? -->
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
Description of PR Summary: add the following topology: ansible/vars/topo_t0-isolated-d256u256s2.yml ansible/vars/topo_t0-isolated-d32u32s2.yml ansible/vars/topo_t1-isolated-d448u16.yml ansible/vars/topo_t1-isolated-d56u2.yml 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
Description of PR Summary: add the following topology: ansible/vars/topo_t0-isolated-d256u256s2.yml ansible/vars/topo_t0-isolated-d32u32s2.yml ansible/vars/topo_t1-isolated-d448u16.yml ansible/vars/topo_t1-isolated-d56u2.yml Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
Description of PR Summary: add the following topology: ansible/vars/topo_t0-isolated-d256u256s2.yml ansible/vars/topo_t0-isolated-d32u32s2.yml ansible/vars/topo_t1-isolated-d448u16.yml ansible/vars/topo_t1-isolated-d56u2.yml 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
4 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 the following topology:
ansible/vars/topo_t0-isolated-d256u256s2.yml
ansible/vars/topo_t0-isolated-d32u32s2.yml
ansible/vars/topo_t1-isolated-d448u16.yml
ansible/vars/topo_t1-isolated-d56u2.yml
Type of change
Back port request
Approach
What is the motivation for this PR?
Add TH-512 topo
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