BEGIN:VCALENDAR
VERSION:2.0
X-WR-CALNAME:opisummit2026
X-WR-CALDESC:Event Calendar
METHOD:PUBLISH
CALSCALE:GREGORIAN
PRODID:-//Sched.com OPI Summit on DPUs/IPUs 2026//EN
X-WR-TIMEZONE:UTC
BEGIN:VEVENT
DTSTAMP:20260912T214806Z
DTSTART:20261015T153000Z
DTEND:20261015T154500Z
SUMMARY:Welcome & Opening Remarks - Venkat Pullela\, CTO of Networking\, Keysight Technologies
DESCRIPTION:\n
CATEGORIES:KEYNOTE SESSIONS
LOCATION:Bowsers Institute Room\, San Jose\, CA\, USA
SEQUENCE:0
UID:df0e6a9694d184bb66a5952c78afb2ef
URL:http://opisummit2026.sched.com/event/df0e6a9694d184bb66a5952c78afb2ef
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260912T214806Z
DTSTART:20261015T154500Z
DTEND:20261015T161000Z
SUMMARY:From Factory State To Platform Handoff: Automating DPU Onboarding With SZTP - Anssi Söderena\, Fusionlayer\, Inc
DESCRIPTION:A DPU is not ready for use simply because it has booted or received an IP address. It still needs a trusted identity\, compatible software\, network configuration\, credentials\, and evidence that it has reached the expected state. This session presents an OPI Blueprint that uses FusionLayer’s RFC 8572 sZTP server and client to prepare an NVIDIA BlueField-3 from a factory-default or reinitialized state. The workflow establishes trust\, verifies onboarding artifacts\, applies initial configuration\, runs bootstrap scripts\, reports progress\, handles failures\, and performs readiness checks. OpenShift and F5-specific tools then complete the platform integration. An existing Red Hat OpenShift and F5 BIG-IP Next environment serves as the integration target. The project aims to validate traffic flowing from a virtual IP address through the BIG-IP Next traffic-processing component on the DPU to application pods. We will share the resulting workflow\, validation results\, compatibility constraints\, and the boundary between repeatable sZTP onboarding and platform-specific integration.
CATEGORIES:SESSION PRESENTATION
LOCATION:Bowsers Institute Room\, San Jose\, CA\, USA
SEQUENCE:0
UID:431a384343880e17cce62bab225fc3f4
URL:http://opisummit2026.sched.com/event/431a384343880e17cce62bab225fc3f4
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260912T214806Z
DTSTART:20261015T161500Z
DTEND:20261015T164000Z
SUMMARY:Reimagining DPUs for Storage Control and End-to-End Confidential AI - Jitendra Singh & Anshuman Ghosh\, Microsoft
DESCRIPTION:AI infrastructure is rapidly exposing new limitations in traditional cloud architectures. As models scale\, the challenge is no longer limited to computation. Model checkpoints\, embeddings\, vector indexes\, prompts\, KV caches\, and inference data must move efficiently and securely across storage\, networks\, processors\, and accelerators. \n Historically\, DPUs have been used to offload networking\, storage\, and security functions from host CPUs. However\, the next evolution of programmable infrastructure is far more significant. DPUs are emerging as intelligent infrastructure components that can actively participate in storage control\, data movement\, policy enforcement\, tenant isolation\, attestation\, and trusted execution workflows. \n This session explores how DPUs are evolving from infrastructure accelerators into foundational building blocks for AI-native and security-first platforms. We examine emerging architectures where DPUs enable disaggregated storage\, optimize storage-to-accelerator data paths\, and establish verifiable trust across AI infrastructure. The talk explores how emerging DPU architectures can provide a common control and security layer across storage\, networking\, and AI infrastructure\, enabling more trusted and scalable AI platforms. Attendees will gain insight into the future role of DPUs in storage architectures\, confidential AI deployments\, trusted data movement\, along with key challenges and opportunities shaping the next generation of programmable infrastructure.
CATEGORIES:SESSION PRESENTATION
LOCATION:Bowsers Institute Room\, San Jose\, CA\, USA
SEQUENCE:0
UID:a1873f44466d25f2cce71284b44fbc4d
URL:http://opisummit2026.sched.com/event/a1873f44466d25f2cce71284b44fbc4d
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260912T214806Z
DTSTART:20261015T164500Z
DTEND:20261015T171000Z
SUMMARY:Keep the SDK on the Card: Programming SONiC DASH Through OPI - Sridhar Rao\, The Linux Foundation & Mounire El Houmaidi
DESCRIPTION:SONiC DASH programs tenant overlay objects — ENI\, VNET\, routes\, ACL — through the SAI C ABI that dashorch already uses. On a DPU/IPU those objects must land in hardware tables on the card\, not in a software switch on the host. \n The default path today is a vendor SAI library loaded into syncd. That library talks a proprietary SDK from the host. The SONiC image\, the SAI .so\, and the DPU firmware become a single-vendor stack. Swap a BlueField for an Intel IPU and you rebuild the NOS. \n This talk presents a different seam: SAI northbound\, and OPI southbound. libsai_opi_adapter.so is dlopened as libsai.so — the same path every SONiC ASIC backend uses. sai_create_eni becomes CreateInterface + CreateVnic. sai_get_eni_stats becomes GetVnicMetrics. The vendor’s closed SDK stays behind an OPI bridge on the DPU SoC. The host never opens a DOCA or IPDK handle. \n \n We will show\, through a working demo\, \n 1. The object mapping contract as a published\, vendor-neutral dictionary \n 2\, An end-to-end lab: gNMI Set (SAI-Challenger / gnmic) → APPL_DB → dashorch → in-process SAI → OPI :50051 on the DPU \n 3. What is live in the .so today (ENI create + stats). \n 4. Why this split matters for multi-vendor racks
CATEGORIES:SESSION PRESENTATION
LOCATION:Bowsers Institute Room\, San Jose\, CA\, USA
SEQUENCE:0
UID:b3a78aef2eeefeba3a6375fd3269dbe6
URL:http://opisummit2026.sched.com/event/b3a78aef2eeefeba3a6375fd3269dbe6
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260912T214806Z
DTSTART:20261015T171500Z
DTEND:20261015T174000Z
SUMMARY:Extending Host Storage to DPUs: Lessons in Architecture\, Identity\, and Fleet Management - Yash Bhatnagar & Tom Leibu IL\, NVIDIA
DESCRIPTION:NVMesh is an open source distributed storage system that pools NVMe drives across many servers into one shared\, high-performance pool. It was originally designed as a Linux kernel module - and while kernel mode is highly performant\, what pulled us to the DPU was offloading storage software off the host\, isolating it in its own secure domain\, and decoupling it from whatever the host happens to be running.\n\nThis talk is a field-tested case study in building a userspace version of that same storage client. We'll cover why kernel mode wasn't the right fit for the DPU environment\, what building that userspace path took\, & the tradeoffs between the two. We'll cover the nuances of providing identity & configuration to your applications on the DPU - problems shaped less by the DPU than by the automated\, fleet-managed environment it's almost always part of - such as k8s.\n\nEverything we discuss is vendor-neutral - any team moving host software onto a DPU or IPU will recognize these same lessons & gain the same benefits we did. So whether you're thinking\, planning or already undergoing a migration - this talk should save you from re-learning these lessons the hard way.\n\n
CATEGORIES:SESSION PRESENTATION
LOCATION:Bowsers Institute Room\, San Jose\, CA\, USA
SEQUENCE:0
UID:4b9634ae0e3c5342d1cb3e3cb5506005
URL:http://opisummit2026.sched.com/event/4b9634ae0e3c5342d1cb3e3cb5506005
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260912T214806Z
DTSTART:20261015T174000Z
DTEND:20261015T181000Z
SUMMARY:Break
DESCRIPTION:\n
CATEGORIES:BREAKS
LOCATION:Foyer\, San Jose\, CA\, USA
SEQUENCE:0
UID:1c1f5f7bcb807ce5dd6b413d347c1bf2
URL:http://opisummit2026.sched.com/event/1c1f5f7bcb807ce5dd6b413d347c1bf2
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260912T214806Z
DTSTART:20261015T181000Z
DTEND:20261015T183500Z
SUMMARY:How Open Hardware Access Builds the Next Generation of Infrastructure Engineers - Sam Dasilva\, Red Hat
DESCRIPTION:DPUs and SuperNICs sit at the center of AI factories\, HPC and hyperscaler networking\, but the hardware is still mostly locked behind vendor employment. Open-source software solved contributor access decades ago. Hardware has not. That leaves the infrastructure-acceleration contributor pipeline artificially narrow when the industry needs it wide. \n \n This talk follows one path through OPI's open model: CS student with no STEM pipeline\, Red Hat intern on DPU/SmartNIC work\, then OPI LFX mentee who brought the DPU Operator into OPI as upstream. We cover the technical work of that handoff (decoupling OpenShift-specific dependencies\, supporting vanilla Kubernetes\, validating Fedora/CentOS Stream/AlmaLinux via bootable containers\, and standing up multi-vendor community CI) and show how open labs and mentorship produce both working code and working engineers. From there\, OPI steers the project. \n \n Attendees leave with a concrete model for growing the DPU/IPU contributor base by solving the hardware access problem\, as well as the software one.
CATEGORIES:SESSION PRESENTATION
LOCATION:Bowsers Institute Room\, San Jose\, CA\, USA
SEQUENCE:0
UID:22bc1ed677315b4b091e204b5b2d8e96
URL:http://opisummit2026.sched.com/event/22bc1ed677315b4b091e204b5b2d8e96
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260912T214806Z
DTSTART:20261015T184000Z
DTEND:20261015T190500Z
SUMMARY:Network Engine's Hardware Matrix Problem\, and Why DPUs Solve What NICs Can't - Josh Brooks\, WorldTech IT/Network Engine
DESCRIPTION:WorldTech IT builds Network Engine\, a purpose-built hypervisor for network virtual appliances\, on an open-source foundation. Today we don't ship with OVS. Our supported NICs span Intel E823 and X710\, but only E823 supports switchdev offload\, so there's no consistent path across the matrix. OVS-DPDK covers X710\, but most of our NVAs already run their own DPDK fast path\, so stacking DPDK in the host OVS just burns CPU cores twice. Instead we lean on Linux bridges with NIC hardware acceleration\, virtio multi-queue tuning\, and SR-IOV/IOMMU passthrough where NVAs need maximum performance. \n I'm sponsoring OPI Blueprint 003: OVS offload on a DPU\, starting with NVIDIA BlueField-3 since it's already largely packaged there\, with the goal of bringing that pattern to the rest of the ecosystem for both KVM and KubeVirt. Move OVS to the DPU and switching stops costing host CPU cores at all. I'll cover what we've hit in product engineering\, where the blueprint stands\, and why turning one vendor's example into an ecosystem standard is the whole point of OPI.
CATEGORIES:SESSION PRESENTATION
LOCATION:Bowsers Institute Room\, San Jose\, CA\, USA
SEQUENCE:0
UID:3b79dcab82f0f8b896bf7dff2b0b2970
URL:http://opisummit2026.sched.com/event/3b79dcab82f0f8b896bf7dff2b0b2970
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260912T214806Z
DTSTART:20261015T191000Z
DTEND:20261015T193500Z
SUMMARY:Demonstrating Open DSE Through Vendor-Neutral OPI Control - Sridhar Rao\, The Linux Foundation & Serey Kong\, Intel Corporation
DESCRIPTION:DPUs and IPUs can move networking\, security\, storage\, telemetry\, and other infrastructure services away from host CPUs. The operational challenge is that different devices expose different discovery\, lifecycle\, endpoint\, forwarding\, and evidence models. \n This session introduces Open DSE (open variant of vSphere's DSE)\, a demo-ready open-source framework for expressing\, executing\, and validating DPU/IPU infrastructure-offload workflows. . Users express the required outcome through one control point\, while Open DSE validates the topology\, applies readiness gates\, maps VFs and representors or equivalent endpoints\, configures forwarding\, runs traffic\, collects evidence\, generates a report\, and safely removes only the state created by the experiment. \n The session includes a live hardware demonstration of two KVM/QEMU virtual machines communicating through a DPU-controlled forwarding path\, followed by evidence showing whether the flow was configured in software or offloaded to hardware. The talk will also share where attempted abstraction succeeds\, where it fails\, and what those results suggest for OPI APIs\, operators\, blueprints\, and interoperability testing
CATEGORIES:SESSION PRESENTATION
LOCATION:Bowsers Institute Room\, San Jose\, CA\, USA
SEQUENCE:0
UID:9ef8149a996e40b61afdfdcdd734079e
URL:http://opisummit2026.sched.com/event/9ef8149a996e40b61afdfdcdd734079e
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260912T214806Z
DTSTART:20261015T201500Z
DTEND:20261015T210000Z
SUMMARY:Panel Session To Be Announced
DESCRIPTION:\n
CATEGORIES:SESSION PRESENTATION
LOCATION:Bowsers Institute Room\, San Jose\, CA\, USA
SEQUENCE:0
UID:1b5acb2f2f6536b078030c8984683f05
URL:http://opisummit2026.sched.com/event/1b5acb2f2f6536b078030c8984683f05
END:VEVENT
BEGIN:VEVENT
DTSTAMP:20260912T214806Z
DTSTART:20261015T210000Z
DTEND:20261015T220000Z
SUMMARY:Lunch
DESCRIPTION:\n
CATEGORIES:BREAKS
LOCATION:Foyer\, San Jose\, CA\, USA
SEQUENCE:0
UID:77700f01133d295b73f00068313bb2cf
URL:http://opisummit2026.sched.com/event/77700f01133d295b73f00068313bb2cf
END:VEVENT
END:VCALENDAR