Hello Everyone – quite a few Attendees this last call – 44! Thanks for your time on Wednesday, we had a great Test discussion and Demo provided by Keysight, really appreciate the effort and test artifacts coming together!
The notes from last Wednesday are below, along with the recording link. See you
on 3/16/2022.
Meeting Title: SONiC-DASH-Workgroup Community Meeting #14
March 9, 2022
Attendees (44):
Discussion Keysight: Testbed hardware, environment setup and best case scenario test case @Mircea from Keysight delivered a great Testing demo with a follow-up Q&A session for
PR75 - we are making progress!
Help Needed:
@Mircea would like a community contribution for a way to configure the devices (a driver in the form of a python library providing a function call)
@Mircea needs an API for configuring ACL policies Discussion of when to move test artifacts to the SONiC Mgmt test setup (framework is large, w/a learning curve)
@Guohan would rather not have 2 branches of code, and prefers to leverage the SONiC mgmt repo
NVidia update: Kristina and Marian collaborated to create a list and schedule for items in the table below. Items in Green are where help is needed from the Community.
Can we organize the Behavioral Model folders similarly to the Documentation folders? Yes, first we need to Approve/Merge PR, then can rename/rearrange. Wrap this up within 2 weeks.
|
|
Fragment paper discussion:
@John Carney performed in-depth research and feedback re: of fast removal of TCP connections from the flow table upon closing of the connection
Review this data and attempt to close this out in 4th meeting 3/14/2022
Other Discussion:
@Silvano
Q: Did we make the decision for the NIC to run SONiC-DASH?
A: Yes, this has been the plan
|
|
Upcoming Action Items for Mar 16th, 2022 |
Status/Date |
Notes |
|
1 |
Review update to SDN Transforms document |
Figure updated |
Review update in 3/16/2022 Community Meeting |
|
2 |
ENI Sizing/Scale |
TBD |
|
|
3 |
Michal Zygmunt to present NB interface |
TBD |
|
|
4 |
Nvidia will publish their code added to bmv2 for the DASH model |
New resource ramping up |
NVidia has finished the reference implementation of SAI APIs into P4 runtime, it's been working this week. Need to generalize into a template. The last step will
be to become auto-generated. Need ~ 3 weeks to do so. |
|
5 |
Nvidia -
help needed
for pipeline directory 'to-do' list; we prefer everything to be part of the P4 model, and to be emulated (Underlay is not the highest Pri)
|
Some participants have offered to help - thank you! Will work w/Marian & Kristina in smaller group.
|
Skills needed: ability to dig into the P4 compiler, software switch, and software simulation tool
XN tracking needs to be supported
Andy hosts P4 tool session - please see email in SONiC-DASH email group.
|
|
6 |
Intel - SAI Thrift (API) PTF and extension to SmartNic |
Resource procured, work started |
Discuss design in 3/16/2022 Community Meeting
The test cases have many dependencies and are geared toward testing a switch (a SmartNic - has different requirements vs. a switch, ex: port expectations are different), and some code changes will be required. |
|
7 |
Community please Review PRs and comment
|
PRs filed for review/comment |
https://github.com/Azure/DASH/pulls
|
|
8 |
Issues list for tracking & resolution
|
|
|
Sticky for Links/Data: |
|
|
|
Link to Recording |
|
3/09/2022 Community Call; please request access via the link if you are not able to view/listen |
|
Azure DASH GitHub Repo: |
Self-explanatory |
|
|
|
https://github.com/Azure/DASH/blob/main/test/docs/dash-test-workflow-saithrift.md |
Ideal test workflow is here, converted to .md |
|
SAI Thrift |
Client server needed for testing |
|
|
P4 |
https://opennetworking.org/p4/ and https://p4.org/working-groups/ |
Open source, domain-specific programming language for network devices, specifying packet processing for data plane devices (switches, routers, NICs, filters, etc.) |
|
PINS |
|
|
|
PNA consortium spec |
An architecture describing the structure and common capabilities of network interface controller (NIC) devices which process packets transiting one or more interfaces
and a host system. |
|
|
IPDK |
IPDK is an open source, vendor agnostic framework of drivers and APIs for infrastructure offload and management which runs on a CPU, IPU, DPU or switch. IPDK runs in Linux and uses a set of well-established tools such as DPDK and P4 to enable network virtualization. |
|
|
bmv2 |
The second version of the reference P4 software switch, nicknamed bmv2 (for behavioral model version 2). The software switch is written in C++11. It takes as input a JSON file generated from your P4 program by a P4 compiler and interprets it to implement the packet-processing behavior specified by that P4 program |
|
|
DPDK |
DPDK is the Data Plane Development Kit which consists of libraries to accelerate packet processing workloads running on a wide variety of CPU architectures. |
Thank you again for your participation…
|
|
Kristina Moore Principal PM, Azure Core – DASH Phone 425-722-7720 Cell 425-876-2040 Email kri...@microsoft.com One Microsoft Way Redmond, WA 98052
|