Add new topology for smartswitch #14797
Conversation
|
@ganglyu can we rename this topo as t1-smartswitch? Please refer a related PR in sonic-net/sonic-buildimage#17326 |
I suggest using t1-8-lag-smartswitch, t1-32-lag-smartswitch, and t1-64-lag-smartswitch as topology names, please let me know what you think. |
|
seems to be the same work that Jing is doing? PR: #14595 (Please ignore the demo folder). |
| @@ -351,3 +351,20 @@ | |||
| inv_name: veos_vtb | |||
| auto_recover: 'False' | |||
| comment: Tests virtual switch vm | |||
|
|
|||
| - conf-name: vms-kvm-smartswitch | |||
There was a problem hiding this comment.
where is the topology update between NPU to DPU VMs?
There was a problem hiding this comment.
I only created VM for NPU and DPU in this PR.
We will have another PR to cover the connection between NPU to DPU VMs.
Need to check with Jing |
Description of PR
Summary:
Fixes # (issue)
Microsoft ADO: 25068545
Type of change
Back port request
Approach
What is the motivation for this PR?
Need new topology to support smartswitch testbed
How did you do it?
Add new topology and related testbed information
How did you verify/test it?
Run add-topo and deploy-mg, check device configuration
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation