split testbed readme into multiple sections#217
Conversation
7dfa259 to
d1cb065
Compare
| - List of currently defined topologies in veos inventory file | ||
| ``` | ||
| [servers:vars] | ||
| topologies=[‘t1', ‘t1-lag', 't0', 'ptf32', 'ptf64'] |
There was a problem hiding this comment.
It was changed. Latest list is: 't1', 't1-lag', 't0', 'ptf32', 'ptf64', 't0-64', 't0-64-32'
see sonic-mgmt\ansible\veos
There was a problem hiding this comment.
the main change is to split the document into several sections. will address new topology later.
| - Uses VM with physical name VM0100 | ||
| - Ethernet1 is connected to vlan 102 | ||
| - Ethernet2 is connected to vlan 103 | ||
| - Ethernet9 is connected to Ethernet9 of ARISTA02T1 |
There was a problem hiding this comment.
Need an explanation why? I don't see any '9'-s in the example above. We need a statement that VMs in every topology has a backplane.
There was a problem hiding this comment.
added statement in the overview.
| The VMs use Arista vEOS. They are using to setup protocol test such as BGP, LACP, LLDP. They are created using ```testbed-cli.sh start-vms``` command. Each VM uses 2G of RAM and has 10 network interfaces: | ||
|
|
||
| 1. 8 front panel ports. These ports are connected to openvswitch bridges, which are connected to vlan interfaces. The vlan interfaces are connected to the fanout switch (through physical port). | ||
| 2. 1 back panel port. All testbed VMs connected to each other using this port (it isn't shown on the figure above). |
There was a problem hiding this comment.
not all VMs are connection through the backplane.
Each topology has its own backplane
| - t1-lag: 24 VMs + PTF container for injected ports. 8 VMs has two ports each in LAG | ||
| - ptf32: classic PTF container with 32 ports connected directly to DUT ports | ||
| - ptf64: as ptf32, but with 64 ports | ||
| - t0: 4 VMs + ptf. PTF container has 4 injected ports + 28 directly connected ports |
There was a problem hiding this comment.
not all topologies are described here. t0-64 and t0-64-32 have to be describer
There was a problem hiding this comment.
will ad new topology in separate cr.
* split testbed into multiple sections
<!-- 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: Fixes issues in isolated v6 topo. ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [ ] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [ ] Test case improvement ### Back port request - [ ] 202012 - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 ### Approach #### What is the motivation for this PR? Fix the following error - ipv6 address pattern - 'route-id' typo - remove template dependencies for `nhipv4` and `host['interfaces']['Loopback0']['ipv4']` #### 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? -->
…ate (sonic-net#8864) * [202012][sonic-platform-daemons] submodule update 3d14066 [xcvrd][y_cable] refactor xcvrd to listen to port probe without locks; fix the get_firmware_version API to sync with download_firmware (sonic-net#216) Signed-off-by: vaibhav-dahiya <vdahiya@microsoft.com> * update sonic-platform-common 93244bf [Y-Cable][Broadcom] upgrade to support Broadcom Y-Cable API to release 1.2 (sonic-net#217) Signed-off-by: vaibhav-dahiya <vdahiya@microsoft.com>
No description provided.