DASH Workgroup Meeting Minutes 5/18/2022

69 views
Skip to first unread message

Kristina Moore

unread,
May 20, 2022, 3:30:31 PM5/20/22
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, Sandeep Balani, Ariff Premji, White, Joseph L, Madhavan, Sandeep, Rita Hui, Singhai, Anjali, Matty Kadosh, Sanders, Mark, Oleksandr Kholodnyi

Hello DASH Community – thanks for your time on Wednesday.   And thank you to NVIdia for a great SONiC on DPU demo!

 

The notes from Wednesday are below, along with the recording links.  See you on 5/25/2022   

 

Meeting Title:  SONiC-DASH-Workgroup Community Meeting #22

May 18, 2022

Attendees (32):

 

Alberto Villarreal - Keysight

Fingerhut, John Andy - Intel

Kristina Moore -MSFT

Matty Kadosh - Nvidia

Pourya Shahmaleki - MSFT

Baldi  Mario - Pensando

Gerald Degrace - MSFT

Liat Grozovik - Nvidia

Mel Tsai - Cisco

Prince Sunny - MSFT

Bud Grise - XSightLabs

Guohan Lu - MSFT

Lisa Nguyen - Broadcom

Mircea Dan Gheorghe - Keysight

Roop Mukherjee - Nvidia

Chris Sommers - Keysight

James Grantham - MSFT

Mahalinga, Venkatesan - Dell

Mohammad Hanif - Broadcom

Shah, Shitanshu - Intel

Cummins, Paul - Intel

james_lo 駱正雄 - Accton

Manodipto Ghose - Keysight

Oleksandr Ivantsiv - Nvidia

Sudarshan, Reshma - Intel

Diana Galan - Keysight

John C Carney - XSightLabs

Marian Pritsak - Nvidia

Oleksandr Kholodnyi - PLVision

Xin Liu - MSFT

Ezra Yosef - XSightLabs

Keshav Gupta - Fungible

 

 

 

 

Discussion
 

Nvidia presentation and Demo - SONiC on DPU - Oleksandr Ivantsiv

Each vendor has its own SAI implementation and SDK

NASA - Nvidia SDN Application

Python plugins in PMON container

Implementation details; reduced amount of components
 

 

 

Features:
 

 

 

Memory consumption:  No docker daemon running.  Includes kernel drivers for Nvidia.  Base Debian plus additional kernel drivers.
 

 

Debian memory usage example:
 

 

SONiC base OS w/docker, no containers running:
 

 

 

SONiC OS memory w/all docker containers running:
 

 

 

Docker containers memory usage depends upon how many applications are running inside

 

Commands shown

Show platform summary

Docker ps

Show feature status

Docker exec -it syncd bash -c "ps -ax'

Show interfaces status

Config interface shutdown Ethernet4 (example)

Config interface mtu Ethernet4 1518

Config interface

Show interfaces transceiver status

Show interfaces transceiver eeprom Ethernet4

 

Upcoming

When SWSS is completed, we will know more about memory consumption

Changes for SONiC running on ARM and on top of Bluefield, with a fully aligned interface configuration

There are additional phases in progress

Next is to show traffic such as BGP peering

Later based on DASH HLD, we will see how the Overlay will be integrated into SONiC

Another API coming, to configure the DPU

 

Plan to upstream? 

@john carney - will there be a new target build image for DASH?  @liat - Eventually the plan is to have it upstreamed.

 

Learnings?

@hanif - what were the learnings re: SONiC and the DPU?  @liat - learning what exactly is needed from the large list of features and SAI APIs, and the priority for them, and how to integrate onto a working supplier

 

@lisanguyen - 1st time seeing SONiC on ARM, is this a smooth transition going from x86 to ARM64?  @liat - cross compilation is slower, bring up of equipment is better to bring up a server with a native compilation

 

@xin - once SAI DASH is standardized and matured, we may take to the broader SAI community and place into the SAI releases

 

@venkat mahalinga - need to come up with differences re: syncd container, enabling DPU for SONiC there will be more considerations.  Please join behavioral model meeting. 

 

@hanif - original vision for SONiC on DPU regardless of scenario.  When it comes to SmartSwitch, does it make sense to run multiple instances of SONiC?  Yes, see Gerald's comments at the beginning of the meeting.  Update HLDs as to where the containers run.  We can move containers to DPUs. 

 

 

 

 

Upcoming Action Items for

May 25th, 2022

Status/Date

Notes

1

MSFT/Nvidia to present/discuss progress

May 18th - Complete

See Sticky Notes below for recording links

2

Draft .json uploaded to GitHub PR93

Complete

Community please review

3

SONiC DASH Northbound YANG definitions PR106

Posted

Community please review

4

Refreshed DASH HLD posted

Posted

Community please review

5

Behavioral Model volunteers needed

Many items have volunteers, just a few left

 

Skills needed: ability to dig into the P4 compiler, software switch, and software simulation tool 

Andy hosts P4 tool sessions - please see email in SONiC-DASH email group

6

Michal Zygmunt to present NB interface

TBD

 

7

Community please Review PRs and comment

PRs filed for review/comment

https://github.com/Azure/DASH/pulls

8

Issues list for tracking & resolution

 

https://github.com/Azure/DASH/issues

 

 

Sticky for Links/Data:

 

 

Link to Recording 

Teams/Sharepoint:
​mp4 icon SONiC-DASH Workgroup Community Meeting-20220518_090350-Meeting Recording.mp4

YouTubehttps://youtu.be/GIRbsQxqFzE

5/18/2022 Community Call; please request access via the link if you are not able to view/listen

 

 

 


 

Azure DASH GitHub Repo:                     

https://github.com/Azure/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

Principal PM, Azure Core – DASH

Phone 425-722-7720  Cell 425-876-2040

Email kri...@microsoft.com

One Microsoft Way  Redmond, WA 98052

 

Title: LinkedIn - Description: image of LinkedIn iconTitle: Twitter - Description: image of Twitter icon 

 

 

Reply all
Reply to author
Forward
0 new messages