DASH Workgroup Meeting Minutes 8/16 and 8/23/2023

1 view
Skip to first unread message

Kristina Moore

unread,
Aug 28, 2023, 11:48:58 PM8/28/23
to sonic-dash-t...@googlegroups.com, sonic...@googlegroups.com, Sudarshan, Reshma, Marian Pritsak, Chris Sommers, Michal Zygmunt, Fingerhut, John Andy, James Grantham, Mircea Dan Gheorghe, John C Carney, Prince Sunny, Guohan Lu, rmukh...@nvidia.com, Mohammad Hanif, Jae Park, Pranjal Shrivastava, Neeraj Motwani, Anton Putrya, Srinivasan, Vijay, Veerappan, Senthilnathan, Kumaresh Perumal, amith.prabha...@keysight.com, Kristina Moore, Kamil Cudnik, Sandeep Balani, Ariff Premji, White, Joseph L, Madhavan, Sandeep, Rita Hui, Singhai, Anjali, Matty Kadosh, Sanders, Mark, Oleksandr Kholodnyi, Ivan Lee, sonic smartswitch leads

Hello DASH Community –thank you for contributing your time this month. 

In summary, this week we have a reminder that the High Availability high level design / initial proposal documents are published for consumption/review if you would like to take a look.  Please reach out to @Riff Jiang via lists.sonicfoundation.dev with any feedback or questions:

We merged PR404 to have a starting point for underlay routing, and also performed a follow-up for PR360 (SAI attributes for ACL rules should include list of IP prefixes for the Bmv2 compile); the potential solution here may be complex.  Detailed PRs and weekly meeting notes follow below…

As always, with respect to any of our DASH meetings High Availability (Tuesdays), Community (Wednesdays), or Behavioral Model (Thursdays) – please let me know if there are PRs, Q&A, or items you would like to discuss or present. 

The DASH YouTube channel link is here to subscribe / access WG content (and click the bell to receive notifications). 

See you on 8/30/2023


Meeting Title:  SONiC-DASH-Workgroup Community Meeting #80 & 81

Attendees (35):

DASH Group to join: https://groups.google.com/g/sonic-dash     

DASH-Test-Workgroup Group to join: https://groups.google.com/g/sonic-dash-test-workgroup

 

Agrawal, Ashutosh - Intel

Jeevan - Arista

Mircea Dan Gheorghe - Keysight

Narayanan, Swaminathan - AMD

Sunil Kumar C Suvarneshwar - Arista

Amith GSPN - at large

Kamil Cudnik - MSFT

Muhammad Naveed Mozaffar - Arista

Oleksandr Ivantsiv - NVidia

Thyamagundalu, Sanjay - AMD

Andriy Kokhan - PLVision

Kristina Moore - MSFT

Mukesh MV - AMD

Riff Jiang - MSFT

Urvish - Arista

Bud Grise - XSightLabs

Kumaresh Perumal - MSFT

murali Venkateshaiah - Cisco

Rob Murphy - Cisco

Veerappan, Senthilnathan - MSFT

Chris Sommers - Keysight

Marian Pritsak - NVidia

mxiao - Arista

Saad Mazhar - DreamBig Semi

Vijay Srinivasan - AMD

Fingerhut, John Andy - Intel

McCollum, Macy - Intel

Narasimha Rao Vadrevu - NapaTech

Srinivasan, Vijay - AMD

Vincent Legrand - XSightLabs

Harris, David M - Intel

Megha Sinha - Arista

Mohammad Hanif - Broadcom

Sudharsan Dhamal Gopalarathnam - NVidia

Yakiv Huryk - NVidia

 

Discussion - PRs/Issues/Documentation for review, comments, suggestions

 

DASH Community Upcoming Project Action Items

 

 

A screenshot of a computer

Description automatically generated

 

 

Discuss:


ACL rule API is not generating the correct output (via P4code)

PR360 - SAI attributes for ACL rules should include list of IP prefixes for the Bmv2 compile  (follow up)

 

Discussed again in 8/16/2023 Community meeting

@Pterosaur had created a PR/fix?

1.      The current P4 code has a mismatch between the BMv2 and the SAI generation. To SAI, it’s list of prefixes, But to BMv2, it’s just a single prefix. This reason of difference is due to the limitation of BMv2 that cannot support the list of prefix as the key.

2.      We agree with using DASH_MATCH in dash_acl.p4 as default, to avoid the need to declare DASH_MATCH in other supplier pipelines.

3.                  Here are two solutions to achieve our goal:

1.      To set DASH_MATCH as default, but to remove this MACRO in BMv2 pipeline. This solution is simple enough, but isn’t perfect due to the gap between BMv2 and SAI (existing).

2.      And another solution, (possibly better) comes from @lguohan . We should keep the same declaration of list prefixes in P4 code. Although BMv2 doesn’t support list prefixes, we can expand the list of prefixes in saiapi level and input the single prefix to BMv2 one by one. This solution will be a little bit complicated but more reasonable.

 

 Other Notes:
 

Introduction/Welcome: 

None this week 

Next Week:

Cover (high level) HA slides in SmartSwitch SONiC repo

Other, please contact Kristina

 

                  

Sticky for Links/Data:

 

 

DASH Groups to join to receive Invites, Meeting Notes, and Comms

DASH: https://groups.google.com/g/sonic-dash    

 

DASH-Test-Workgroup Group: https://groups.google.com/g/sonic-dash-test-workgroup  

If anyone knows other people who would like info re: our community, please have them joins these groups for receive Comms, etc…

Links to Recording 

Teams/Sharepoint:

SONiC-DASH Workgroup Community Meeting-20230816_090340-Meeting Recording.mp4
 

​mp4 icon SONiC-DASH Workgroup Community Meeting Aug 23 2023.mp4

 

YouTube:

Wed Aug 16 2023
https://youtu.be/mdKESULkYUM
 

Wed Aug 23 2023
https://youtu.be/tc63wmTLGKQ

HA Calls suspended

Thursday Aug 24 Behavioral Model Call
https://youtu.be/N47hlAmwh9Y

8/16/2023  and 8/23/2023 Community Call(s); please request access via the link if you are not able to view/listen

 

 

Azure DASH GitHub Repo:                     

https://github.com/sonic-net/DASH

 


Test/Docs folder:

https://github.com/Azure/DASH/blob/main/test/docs/dash-test-workflow-saithrift.md

Ideal test workflow is here, converted to .md

SAI Thrift     

SAI Thrift PR

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

https://opennetworking.org/pins/

 

PNA consortium spec

https://p4.org/p4-spec/docs/PNA-v0.5.0.html

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.

Describes the structure and capabilities of the pipeline, and a user program, which specifies the functionality of the programmable blocks within that pipeline. For more information, see the P4 Language Consortium specifications

IPDK

Infrastructure Programmer Development Kit (ipdk.io) and

https://github.com/ipdk-io/ipdk-io.github.io

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

https://github.com/p4lang/behavioral-model

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

https://www.dpdk.org/

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 MBA, M.S., CISSP - Azure Core Principal PM / DASH
Office: 425-722-7720     Mobile: 425-876-2040     Email: kri...@microsoft.com
DASH Group to join: https://groups.google.com/g/sonic-dash    
DASH-Test-Workgroup Group to join: https://groups.google.com/g/sonic-dash-test-workgroup

ImageTitle: LinkedIn - Description: image of LinkedIn icon

 

 

Reply all
Reply to author
Forward
0 new messages