Skip to content

Optimizing the location of topology information and generating according to dut#959

Open
Harrison-SH wants to merge 1 commit intosonic-net:masterfrom
Harrison-SH:daily-pr
Open

Optimizing the location of topology information and generating according to dut#959
Harrison-SH wants to merge 1 commit intosonic-net:masterfrom
Harrison-SH:daily-pr

Conversation

@Harrison-SH
Copy link
Copy Markdown
Contributor

Summary:
Optimizing the location of topology information to be specified by the varible of topo_file.
Optimizing topology information could be generated according to the special dut.

Signed-off-by: Harrison-hu harrihu@celestica.com

Type of change

  • [] Test case(new/improvement)

Approach

Within testbed-cli.sh. Setting the location of topology files to topo_file.
Within testbed_add_vm_topology.yml ... . instead of vars/topo_{{ topo }}.yml with {{ topo_file }}.

Within testbed-cli.sh. If user has defined the topology information with the dut. Use the topology
information as topo_file

How did you verify/test it?

  1. Not Generated topo_t1_xxxxdut.yml. Run cases. pick up topo vars from topo_t1.yml successfully.
  2. Generated topo_t1_xxxxdut.yml. Run cases. pick up topo vars from topo_t1_xxxxdut.yml successfully.

…e varible of topo_file. Optimizing topology information could be generated according to the special dut.
kazinator-arista pushed a commit to kazinator-arista/sonic-mgmt that referenced this pull request Mar 4, 2026
These changes are included in this PR:

07e1f79 [syncd] Add workaround for warm boot new objects (sonic-net#959)
50fd353 Fix the option missing in kernel config issue (sonic-net#956)
e77503c [syncd] Comparison logic workaround for empty buffer profile (sonic-net#906) (sonic-net#941)
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.

2 participants