Add phoenix wing ptf test plan#13645
Merged
wangxin merged 4 commits intosonic-net:masterfrom Nov 4, 2024
Merged
Conversation
6 tasks
7 tasks
Collaborator
|
@eddieruan-alibaba Content of this PR is also included in #14259. To avoid duplication, maybe it would be better to keep this PR for PTF test plan. And use #14259 for spytest test plan only. |
wangxin
reviewed
Sep 2, 2024
|
|
||
| configuration: | ||
| PE1: | ||
| cfg_file_loc : ../tests/srv6/7nodes_cisco/PE1.json |
Collaborator
There was a problem hiding this comment.
The topology file is supposed to contain logical relationship information between testbed components.
dut_cfg_file_loc and cfg_file_loc are detailed information for generating configuration files for testbed components. It is not appropriate to include them in topology file. It would be better to track these information in separate variable files.
The deploy-mg code should be updated to get these information from separate variable files.
Contributor
Author
There was a problem hiding this comment.
The DUT configuration is applied at deploy-mg, but other nodes configurations are done via add-topo. Since we don't use minigraph and want to use config_db.json to apply configuration, we copy over provided config files at the location when the configuration would be applied.
Contributor
Author
Yes. 14259 was raised for collecting spytest testplan's comments. But since both are not in and spytest test plan branch is a child branch of ptf testplan. It got both. But 14259 will be spytest only. |
Collaborator
Thanks for explaining the reason. Can you remove the PTF test plan from #14259 to avoid duplication? |
wangxin
pushed a commit
that referenced
this pull request
Nov 4, 2024
What is the motivation for this PR? This changes are used for phoenix wing initiative, to provide 1. 5-node testbed for running existing test cases in sonic-mgmt 2. 7-node testbed for running srv6 test cases. The difference for this testbed is to use Cisco's ngdp as dataplane simulation. This type of vsonic would allow us to simulate both control plane and data plane in virtual testing environment. How did you do it? Based on Test doc #13645 How did you verify/test it? Both sanity test cases are running daily for phoenix wing. Any platform specific information? cisco-8101-p4-32x100-vs Supported testbed topology if it's a new test case? 5-node and 7-node testbed listed in testplan #13645. Documentation #13645
wangxin
approved these changes
Nov 4, 2024
veronica-arista
pushed a commit
to veronica-arista/sonic-mgmt
that referenced
this pull request
Nov 7, 2024
…13785) What is the motivation for this PR? This changes are used for phoenix wing initiative, to provide 1. 5-node testbed for running existing test cases in sonic-mgmt 2. 7-node testbed for running srv6 test cases. The difference for this testbed is to use Cisco's ngdp as dataplane simulation. This type of vsonic would allow us to simulate both control plane and data plane in virtual testing environment. How did you do it? Based on Test doc sonic-net#13645 How did you verify/test it? Both sanity test cases are running daily for phoenix wing. Any platform specific information? cisco-8101-p4-32x100-vs Supported testbed topology if it's a new test case? 5-node and 7-node testbed listed in testplan sonic-net#13645. Documentation sonic-net#13645
veronica-arista
pushed a commit
to veronica-arista/sonic-mgmt
that referenced
this pull request
Nov 7, 2024
Summary: The purposes for this ptf test plan are Enhance current sonic-mgmt infra to support 7 node vsonic ptf topology with provided config db json. Verify all needed SRv6 functionalities and routing enhancements via running test casess on a 7-node PTF testbed. Use existing sonic-mgmt test cases to run a 5 node vsonic topology to secure current SONiC codes' quality with new codes for SRv6 functionalities and routing enhancements. PR title State Add test cases and infra changes for phoenixwing ptf test sonic-net#13785 GitHub issue/pull request detail What is the motivation for this PR? This is ptf test plan for Phoenix Wing initiative. This initiative is discussed in routing WG. The progress is tracked via https://lists.sonicfoundation.dev/g/sonic-wg-routing/wiki/36853. This PR is for layouting the test plan for this initiative as well as sonic-mgmt infra enhancements. 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 https://lists.sonicfoundation.dev/g/sonic-wg-routing/wiki/36853
sreejithsreekumaran
pushed a commit
to sreejithsreekumaran/sonic-mgmt
that referenced
this pull request
Nov 15, 2024
…13785) What is the motivation for this PR? This changes are used for phoenix wing initiative, to provide 1. 5-node testbed for running existing test cases in sonic-mgmt 2. 7-node testbed for running srv6 test cases. The difference for this testbed is to use Cisco's ngdp as dataplane simulation. This type of vsonic would allow us to simulate both control plane and data plane in virtual testing environment. How did you do it? Based on Test doc sonic-net#13645 How did you verify/test it? Both sanity test cases are running daily for phoenix wing. Any platform specific information? cisco-8101-p4-32x100-vs Supported testbed topology if it's a new test case? 5-node and 7-node testbed listed in testplan sonic-net#13645. Documentation sonic-net#13645
sreejithsreekumaran
pushed a commit
to sreejithsreekumaran/sonic-mgmt
that referenced
this pull request
Nov 15, 2024
Summary: The purposes for this ptf test plan are Enhance current sonic-mgmt infra to support 7 node vsonic ptf topology with provided config db json. Verify all needed SRv6 functionalities and routing enhancements via running test casess on a 7-node PTF testbed. Use existing sonic-mgmt test cases to run a 5 node vsonic topology to secure current SONiC codes' quality with new codes for SRv6 functionalities and routing enhancements. PR title State Add test cases and infra changes for phoenixwing ptf test sonic-net#13785 GitHub issue/pull request detail What is the motivation for this PR? This is ptf test plan for Phoenix Wing initiative. This initiative is discussed in routing WG. The progress is tracked via https://lists.sonicfoundation.dev/g/sonic-wg-routing/wiki/36853. This PR is for layouting the test plan for this initiative as well as sonic-mgmt infra enhancements. 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 https://lists.sonicfoundation.dev/g/sonic-wg-routing/wiki/36853
yutongzhang-microsoft
pushed a commit
to yutongzhang-microsoft/sonic-mgmt
that referenced
this pull request
Nov 21, 2024
…13785) What is the motivation for this PR? This changes are used for phoenix wing initiative, to provide 1. 5-node testbed for running existing test cases in sonic-mgmt 2. 7-node testbed for running srv6 test cases. The difference for this testbed is to use Cisco's ngdp as dataplane simulation. This type of vsonic would allow us to simulate both control plane and data plane in virtual testing environment. How did you do it? Based on Test doc sonic-net#13645 How did you verify/test it? Both sanity test cases are running daily for phoenix wing. Any platform specific information? cisco-8101-p4-32x100-vs Supported testbed topology if it's a new test case? 5-node and 7-node testbed listed in testplan sonic-net#13645. Documentation sonic-net#13645
yutongzhang-microsoft
pushed a commit
to yutongzhang-microsoft/sonic-mgmt
that referenced
this pull request
Nov 21, 2024
Summary: The purposes for this ptf test plan are Enhance current sonic-mgmt infra to support 7 node vsonic ptf topology with provided config db json. Verify all needed SRv6 functionalities and routing enhancements via running test casess on a 7-node PTF testbed. Use existing sonic-mgmt test cases to run a 5 node vsonic topology to secure current SONiC codes' quality with new codes for SRv6 functionalities and routing enhancements. PR title State Add test cases and infra changes for phoenixwing ptf test sonic-net#13785 GitHub issue/pull request detail What is the motivation for this PR? This is ptf test plan for Phoenix Wing initiative. This initiative is discussed in routing WG. The progress is tracked via https://lists.sonicfoundation.dev/g/sonic-wg-routing/wiki/36853. This PR is for layouting the test plan for this initiative as well as sonic-mgmt infra enhancements. 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 https://lists.sonicfoundation.dev/g/sonic-wg-routing/wiki/36853
mssonicbld
added a commit
to mssonicbld/sonic-swss.msft
that referenced
this pull request
Feb 18, 2025
**What I did** [HLD] [SRv6 VPN HLD](https://github.com/sonic-net/SONiC/blob/master/doc/srv6/srv6_vpn.md) **Why I did it** This PR is to support SRv6 VPN functions **How I verified it** 1. sonic-mgmt [phoenix wing ptf test plan](sonic-net/sonic-mgmt#13645) 2. orchagent UT (tests/test_srv6.py) in this PR **Details if related** Depends on sonic-swss-common[#919](sonic-net/sonic-swss-common#919)
mssonicbld
added a commit
to Azure/sonic-swss.msft
that referenced
this pull request
Feb 18, 2025
**What I did** [HLD] [SRv6 VPN HLD](https://github.com/sonic-net/SONiC/blob/master/doc/srv6/srv6_vpn.md) **Why I did it** This PR is to support SRv6 VPN functions **How I verified it** 1. sonic-mgmt [phoenix wing ptf test plan](sonic-net/sonic-mgmt#13645) 2. orchagent UT (tests/test_srv6.py) in this PR **Details if related** Depends on sonic-swss-common[#919](sonic-net/sonic-swss-common#919)
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
2 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:
The purposes for this ptf test plan are
Type of change
Back port request
Approach
What is the motivation for this PR?
This is ptf test plan for Phoenix Wing initiative. This initiative is discussed in routing WG. The progress is tracked via https://lists.sonicfoundation.dev/g/sonic-wg-routing/wiki/36853.
This PR is for layouting the test plan for this initiative as well as sonic-mgmt infra enhancements.
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
https://lists.sonicfoundation.dev/g/sonic-wg-routing/wiki/36853