[mtu] optimizing mtu for configurable in testbed#902
[mtu] optimizing mtu for configurable in testbed#902prsunny merged 2 commits intosonic-net:masterfrom Harrison-SH:daily-pr
Conversation
ansible/roles/test/tasks/mtu.yml
Outdated
There was a problem hiding this comment.
Can you pass this as test parameter if you want to make it configurable. This way, it seems user has to edit this value before running the test
There was a problem hiding this comment.
Agree. Done.
Two scenarios has been tested with the parameter of mtu and no the parameter.
passed.
ansible/roles/test/tasks/mtu.yml
Outdated
| - fail: msg="testbed_type {{testbed_type}} is invalid." | ||
| when: testbed_type not in ['t1-lag', 't1', 't1-64-lag'] | ||
|
|
||
| - set_fact: mtu=0 |
There was a problem hiding this comment.
You can make this 9100 and remove the default from python script. Else it conveys the meaning that the test is run with mtu=0. What do you think?
There was a problem hiding this comment.
I think so. I also a little bit want to keep the main flow within py for the coming pytest.
Whether you mean just make it clear on this issue?
If so. I will do it.
There was a problem hiding this comment.
Agree. To make it clear.
Done and test passed.
* [mtu] optimizing mtu for configurable in testbed * [mtu] optimizing mtu for configurable in testbed
…nic-net#902) <!-- Please make sure you've read and understood our contributing guidelines; https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md Please provide following information to help code review process a bit easier: --> ### Description of PR <!-- - Please include a summary of the change and which issue is fixed. - Please also include relevant motivation and context. Where should reviewer start? background context? - List any dependencies that are required for this change. --> Summary: The test_trap_neighbor_miss not supported on non-TOR topologies, this PR updates the skip to run on t0 only. ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [ ] Bug fix - [x] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [ ] Test case improvement ### Back port request - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [x] 202505 ### Approach #### What is the motivation for this PR? Skip the COPP trap neighbor miss test on t1 topologies. #### 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 <!-- (If it's a new feature, new test case) Did you update documentation/Wiki relevant to your implementation? Link to the wiki page? -->
[Vnet] Fix NameError for 'swsssdk' and align output (sonic-net#902) [config] Add 'interface transceiver' subgroup with 'lpmode' and 'reset' subcommands (sonic-net#904) Improved route_check tool and adopt to 20191130 image. (sonic-net#898)
Summary:
Type of change
I have added the parameter of "testbed_mtu", Users can use the default value or set their own mtu .
The parameter of self.pktlen has been added. When inputing parameter of "testbed_mtu" isn't the default of 0. It will be set with the value. otherwise. It will use the default value of DEFAULT_PACKET_LEN.
How did you verify/test it?
Any platform specific information?