[Fix]: Enhancement of port selection criteria for multidut RDMA cases based on testbed informaition#14127
Conversation
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
@sdszhang Added the testbed info in the form of parameter |
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
@selldinesh PR conflicts with 202405 branch |
… based on testbed informaition (sonic-net#14127) Description of PR Summary: This PR enhances the logic for port selection for multidut RDMA cases based on the conf-name defined in the testbed.csv / testbed.yaml file. And also a generic fixture for single and multidut topology to get the snappi ports, dut port, asic_type, asic_value information Fixes # (issue) Approach What is the motivation for this PR? For enhancing the port selection logic and a generic fixture for single and multidut topology How did you do it? Added a pytest fixture called get_snappi_ports and get_snappi_ports_for_rdma whcih selects the ports from the information provided in MULTIDUT_PORT_INFO in variables.py and the testbed info as shown below in testbed.csv vms-snappi-sonic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,sonic-s6100-dut1,snappi-sonic,True,Batman vms-snappi-sonic-multidut,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,[sonic-s6100-dut1;sonic-s6100-dut2],snappi-sonic,True,Batman vms-snappi-single-dut-multi-asic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,sonic-s6100-dut1,snappi-sonic,True,Batman vms-snappi-multi-dut-multi-asic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,[sonic-s6100-dut1;sonic-s6100-dut2],snappi-sonic,True,Batman How did you verify/test it? Tested the logic on pfc cases co-authorized by: [email protected]
… based on testbed informaition (sonic-net#14127) Description of PR Summary: This PR enhances the logic for port selection for multidut RDMA cases based on the conf-name defined in the testbed.csv / testbed.yaml file. And also a generic fixture for single and multidut topology to get the snappi ports, dut port, asic_type, asic_value information Fixes # (issue) Approach What is the motivation for this PR? For enhancing the port selection logic and a generic fixture for single and multidut topology How did you do it? Added a pytest fixture called get_snappi_ports and get_snappi_ports_for_rdma whcih selects the ports from the information provided in MULTIDUT_PORT_INFO in variables.py and the testbed info as shown below in testbed.csv vms-snappi-sonic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,sonic-s6100-dut1,snappi-sonic,True,Batman vms-snappi-sonic-multidut,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,[sonic-s6100-dut1;sonic-s6100-dut2],snappi-sonic,True,Batman vms-snappi-single-dut-multi-asic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,sonic-s6100-dut1,snappi-sonic,True,Batman vms-snappi-multi-dut-multi-asic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,[sonic-s6100-dut1;sonic-s6100-dut2],snappi-sonic,True,Batman How did you verify/test it? Tested the logic on pfc cases co-authorized by: [email protected]
… prio from test_flow for oversubscribtion cases (#14153) Description of PR Summary: This PR accomodates the infra change from PR 14127 and separates the flow prio from test_flow Fixes # (issue) #14004 Approach What is the motivation for this PR? To accomodate the infra change from PR 14127 and separe the flow prio from test_flow How did you do it? Assigned single prio to the test flow instead of passing the entire flow priority to the test flow Dependency Need to incorporate the changes from #14127 co-authorized by: [email protected]
… prio from test_flow for oversubscribtion cases (sonic-net#14153) Description of PR Summary: This PR accomodates the infra change from PR 14127 and separates the flow prio from test_flow Fixes # (issue) sonic-net#14004 Approach What is the motivation for this PR? To accomodate the infra change from PR 14127 and separe the flow prio from test_flow How did you do it? Assigned single prio to the test flow instead of passing the entire flow priority to the test flow Dependency Need to incorporate the changes from sonic-net#14127 co-authorized by: [email protected]
… based on testbed informaition (sonic-net#14127) Description of PR Summary: This PR enhances the logic for port selection for multidut RDMA cases based on the conf-name defined in the testbed.csv / testbed.yaml file. And also a generic fixture for single and multidut topology to get the snappi ports, dut port, asic_type, asic_value information Fixes # (issue) sonic-net#13389 sonic-net#13769 Approach What is the motivation for this PR? For enhancing the port selection logic and a generic fixture for single and multidut topology How did you do it? Added a pytest fixture called get_snappi_ports and get_snappi_ports_for_rdma whcih selects the ports from the information provided in MULTIDUT_PORT_INFO in variables.py and the testbed info as shown below in testbed.csv vms-snappi-sonic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,sonic-s6100-dut1,snappi-sonic,True,Batman vms-snappi-sonic-multidut,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,[sonic-s6100-dut1;sonic-s6100-dut2],snappi-sonic,True,Batman vms-snappi-single-dut-multi-asic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,sonic-s6100-dut1,snappi-sonic,True,Batman vms-snappi-multi-dut-multi-asic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,[sonic-s6100-dut1;sonic-s6100-dut2],snappi-sonic,True,Batman How did you verify/test it? Tested the logic on pfc cases co-authorized by: [email protected]
|
Cherry-pick PR to 202405: #14314 |
… based on testbed informaition (#14127) Description of PR Summary: This PR enhances the logic for port selection for multidut RDMA cases based on the conf-name defined in the testbed.csv / testbed.yaml file. And also a generic fixture for single and multidut topology to get the snappi ports, dut port, asic_type, asic_value information Fixes # (issue) #13389 #13769 Approach What is the motivation for this PR? For enhancing the port selection logic and a generic fixture for single and multidut topology How did you do it? Added a pytest fixture called get_snappi_ports and get_snappi_ports_for_rdma whcih selects the ports from the information provided in MULTIDUT_PORT_INFO in variables.py and the testbed info as shown below in testbed.csv vms-snappi-sonic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,sonic-s6100-dut1,snappi-sonic,True,Batman vms-snappi-sonic-multidut,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,[sonic-s6100-dut1;sonic-s6100-dut2],snappi-sonic,True,Batman vms-snappi-single-dut-multi-asic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,sonic-s6100-dut1,snappi-sonic,True,Batman vms-snappi-multi-dut-multi-asic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,[sonic-s6100-dut1;sonic-s6100-dut2],snappi-sonic,True,Batman How did you verify/test it? Tested the logic on pfc cases co-authorized by: [email protected]
… prio from test_flow for oversubscribtion cases (#14153) Description of PR Summary: This PR accomodates the infra change from PR 14127 and separates the flow prio from test_flow Fixes # (issue) #14004 Approach What is the motivation for this PR? To accomodate the infra change from PR 14127 and separe the flow prio from test_flow How did you do it? Assigned single prio to the test flow instead of passing the entire flow priority to the test flow Dependency Need to incorporate the changes from #14127 co-authorized by: [email protected]
… prio from test_flow for oversubscribtion cases (sonic-net#14153) Description of PR Summary: This PR accomodates the infra change from PR 14127 and separates the flow prio from test_flow Fixes # (issue) sonic-net#14004 Approach What is the motivation for this PR? To accomodate the infra change from PR 14127 and separe the flow prio from test_flow How did you do it? Assigned single prio to the test flow instead of passing the entire flow priority to the test flow Dependency Need to incorporate the changes from sonic-net#14127 co-authorized by: [email protected]
… based on testbed informaition (sonic-net#14127) Description of PR Summary: This PR enhances the logic for port selection for multidut RDMA cases based on the conf-name defined in the testbed.csv / testbed.yaml file. And also a generic fixture for single and multidut topology to get the snappi ports, dut port, asic_type, asic_value information Fixes # (issue) sonic-net#13389 sonic-net#13769 Approach What is the motivation for this PR? For enhancing the port selection logic and a generic fixture for single and multidut topology How did you do it? Added a pytest fixture called get_snappi_ports and get_snappi_ports_for_rdma whcih selects the ports from the information provided in MULTIDUT_PORT_INFO in variables.py and the testbed info as shown below in testbed.csv vms-snappi-sonic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,sonic-s6100-dut1,snappi-sonic,True,Batman vms-snappi-sonic-multidut,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,[sonic-s6100-dut1;sonic-s6100-dut2],snappi-sonic,True,Batman vms-snappi-single-dut-multi-asic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,sonic-s6100-dut1,snappi-sonic,True,Batman vms-snappi-multi-dut-multi-asic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,[sonic-s6100-dut1;sonic-s6100-dut2],snappi-sonic,True,Batman How did you verify/test it? Tested the logic on pfc cases co-authorized by: [email protected]
… prio from test_flow for oversubscribtion cases (sonic-net#14153) Description of PR Summary: This PR accomodates the infra change from PR 14127 and separates the flow prio from test_flow Fixes # (issue) sonic-net#14004 Approach What is the motivation for this PR? To accomodate the infra change from PR 14127 and separe the flow prio from test_flow How did you do it? Assigned single prio to the test flow instead of passing the entire flow priority to the test flow Dependency Need to incorporate the changes from sonic-net#14127 co-authorized by: [email protected]
… based on testbed informaition (sonic-net#14127) Description of PR Summary: This PR enhances the logic for port selection for multidut RDMA cases based on the conf-name defined in the testbed.csv / testbed.yaml file. And also a generic fixture for single and multidut topology to get the snappi ports, dut port, asic_type, asic_value information Fixes # (issue) sonic-net#13389 sonic-net#13769 Approach What is the motivation for this PR? For enhancing the port selection logic and a generic fixture for single and multidut topology How did you do it? Added a pytest fixture called get_snappi_ports and get_snappi_ports_for_rdma whcih selects the ports from the information provided in MULTIDUT_PORT_INFO in variables.py and the testbed info as shown below in testbed.csv vms-snappi-sonic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,sonic-s6100-dut1,snappi-sonic,True,Batman vms-snappi-sonic-multidut,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,[sonic-s6100-dut1;sonic-s6100-dut2],snappi-sonic,True,Batman vms-snappi-single-dut-multi-asic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,sonic-s6100-dut1,snappi-sonic,True,Batman vms-snappi-multi-dut-multi-asic,vms6-1,ptf64,docker-ptf-snappi,snappi-sonic-ptf,10.36.78.59,,Server_6,,[sonic-s6100-dut1;sonic-s6100-dut2],snappi-sonic,True,Batman How did you verify/test it? Tested the logic on pfc cases co-authorized by: [email protected]
… prio from test_flow for oversubscribtion cases (sonic-net#14153) Description of PR Summary: This PR accomodates the infra change from PR 14127 and separates the flow prio from test_flow Fixes # (issue) sonic-net#14004 Approach What is the motivation for this PR? To accomodate the infra change from PR 14127 and separe the flow prio from test_flow How did you do it? Assigned single prio to the test flow instead of passing the entire flow priority to the test flow Dependency Need to incorporate the changes from sonic-net#14127 co-authorized by: [email protected]
Description of PR
Summary: This PR enhances the logic for port selection for multidut RDMA cases based on the conf-name defined in the testbed.csv / testbed.yaml file. And also a generic fixture for single and multidut topology to get the snappi ports, dut port, asic_type, asic_value information
Fixes # (issue)
#13389
#13769
Type of change
Back port request
Approach
What is the motivation for this PR?
For enhancing the port selection logic and a generic fixture for single and multidut topology
How did you do it?
Added a pytest fixture called get_snappi_ports and get_snappi_ports_for_rdma whcih selects the ports from the information provided in MULTIDUT_PORT_INFO in variables.py and the testbed info as shown below in testbed.csv
How did you verify/test it?
Tested the logic on pfc cases
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation