-
Notifications
You must be signed in to change notification settings - Fork 695
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[topo_mx] Add new topo for BMC Mgmt ToR Router #6636
Conversation
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
What is the motivation for this PR? For BMC Mgmt ToR Router, both testing methodology and physical wiring pattern are quite different with existing topos. Adding this topo can let us filter unrelated test cases from mgmt network. How did you do it? Add a new topo (inherit from t0-52) Enhance topo config and topo_facts for including interfaces Enhance minigraph templates to support generate minigraph for this new topo How did you verify/test it? Generate minigraph and deploy to DUT. Use ./testbed-cli.sh deploy-mg to gen&deploy minigraph with new topo mx successfully, All the related configuration are correct pushed to DUT after deploy.
…Azure/sonic-mgmt into internal Fix merge conflicts. Commit history: - Modified args for some of the calls (sonic-net#6605) - Run telemetry tests on all DUT types in a multi-dut setup (sonic-net#6098) - [dualtor]: Fix loopback route removal (sonic-net#6555) - Added support for one portChannel and one routed interface if two por… (sonic-net#5331) - Use config_reload when recovering from internal interfaces that are in down state (sonic-net#6076) - Added python fixture for resetting config changes to fix nightly backend snmp test failures (sonic-net#6607) - Fix Python3 RuntimeError - dictionary changed size during iteration (sonic-net#6646) - [mx] Add docs for mx topo (sonic-net#6634) - [topo_mx] Add new topo for BMC Mgmt ToR Router (sonic-net#6636) - [mx] Enhance announce routes to support MX topo (sonic-net#6635) - Merge branch 'azure-master' into dev/yaqiangzhu/internal_merge
…thub.com/Azure/sonic-mgmt into internal-202205 Fix merge conflicts. Commit history: - [202205][topo_mx] Add new topo for BMC Mgmt ToR Router and enhance announce routes for mx sonic-net#6635 sonic-net#6636 (sonic-net#6650) - Merge commit 'cb91a01b1d44404578d677d501d0e4d011940244' into internal-202205
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
For BMC Mgmt ToR Router, both testing methodology and physical wiring pattern are quite different with existing topos. Adding this topo can let us filter unrelated test cases from mgmt network.
How did you do it?
How did you verify/test it?
Generate minigraph and deploy to DUT.
Use ./testbed-cli.sh deploy-mg to gen&deploy minigraph with new topo mx successfully,
All the related configuration are correct pushed to DUT after deploy.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation