diff --git a/releases/abstraction/opi-release-notes.html b/releases/abstraction/opi-release-notes.html new file mode 100644 index 0000000..6744c96 --- /dev/null +++ b/releases/abstraction/opi-release-notes.html @@ -0,0 +1,1378 @@ + + + + + +OPI "Abstraction" Release — v0.1.0 + + + + + + + + + + +
+
+
+
+ OPI Logo +
Open Programmable Infrastructure  /  Release Notes
+
+
v0.1.0  ·  2026-05-08
+
First Release
+
+

+ OPI + Abstraction +

+

+ The first coordinated release of the OPI Project — establishing a vendor-neutral, hardware-agnostic API abstraction layer across all DPU/IPU capabilities. Any workload, orchestrator, or platform can program any DPU without hardware-specific code. +

+
+ ↗ GitHub Org + { } Release Manifest JSON + ↗ opiproject.org +
+
+
+
22
+
Repositories
+
+
+
4
+
Areas
+
+
+
4
+
Vendors
+
+
+
+
+ + +
+
+
+
Capability Areas
+

Functional Domain Coverage

+

+ Each repository in this release is mapped to one or more capability areas — the functional domains it technically enables. These are not OPI Blueprints; they are classification tags that describe what each repo does. See the OPI Blueprints section below for what an official Blueprint is. +

+
+ +
+ + +
+
Area 01
+ 💾 +
Storage Offload
+
Portable, vendor-neutral NVMe-oF storage offload from host to DPU/IPU using a single gRPC API (opi_api.storage.v1). Covers frontend NVMe & VirtIO, middleend encryption & QoS, remote controllers, and CSI for Kubernetes.
+ +
API
+
+ opi-api +
+ +
Reference Implementations
+
+ opi-spdk-bridge v0.1.1 + spdk v24.01 + gospdk +
+ +
Vendor Implementations
+
+ opi-nvidia-bridge v0.1.2 + opi-intel-bridge v0.2.0 + opi-marvell-bridge v0.1.2 + opi-mangoboost-bridge +
+ +
Clients & Testing
+
+ godpu v0.2.0 + pydpu v0.2.1 + opi-poc +
+
+ + +
+
Area 02
+ 🌐 +
Secure Networking
+
Multi-vendor EVPN gateway with hardware-offloaded IPsec, programmable via OPI networking and security APIs — with full Kubernetes CNI integration. Combines EVPN (evpn_gw.v1alpha1), IPsec IKE (security.v1), and ESP datapath offload (sessionOffload).
+ +
API
+
+ opi-api + sessionOffload v1 +
+ +
Reference Implementations
+
+ opi-evpn-bridge v0.2.0 + opi-strongswan-bridge v0.1.1 + opi-gateway-evpn-cni + opi-cni +
+ +
Vendor Implementations
+
+ opi-nvidia-bridge v0.1.2 + opi-intel-bridge v0.2.0 + opi-marvell-bridge v0.1.2 +
+ +
Clients & Testing
+
+ godpu v0.2.0 + pydpu v0.2.1 + opi-poc +
+
+ + +
+
Area 03
+ 📡 +
DPU Inventory & Telemetry
+
Unified, vendor-neutral view of DPU/IPU hardware inventory and live telemetry using opi_api.inventory.v1 and OpenTelemetry. Enables platform management systems to discover and monitor DPUs across vendors without vendor-specific tooling.
+ +
API
+
+ opi-api +
+ +
Reference Implementations
+
+ opi-smbios-bridge v0.1.2 + otel +
+ +
Vendor Implementations
+
+ opi-nvidia-bridge v0.1.2 + opi-intel-bridge v0.2.0 + opi-marvell-bridge v0.1.2 +
+ +
Clients & Testing
+
+ godpu v0.2.0 + pydpu v0.2.1 + smbios-validation-tool +
+
+ + +
+
Area 04
+ 🚀 +
DPU Provisioning & Lifecycle
+
Fully automated, zero-touch DPU onboarding and lifecycle management using Secure Zero Touch Provisioning (sZTP, RFC 8572) — from factory-fresh hardware to a fully configured, OPI-ready DPU without manual intervention.
+ +
Reference Implementation
+
+ sztp v0.2.0 +
+ +
Infrastructure
+
+ sztpd 0.0.15 +
+ +
Automation & Specification
+
+ ansible-opi-dpu v1.0.0 + opi-prov-life +
+ +
Integration Testing
+
+ opi-poc +
+
+ +
+
+
+ + +
+
+
+
Repository Manifest
+

All 22 Repositories

+

+ Complete list of repositories included in the Abstraction release, with pinned tags, commit SHAs, types, and blueprint participation. Filter by type or blueprint area below. +

+
+ +
+ + + + + + + + +
+ +
+ + + + + + + + + + + + + +
RepositoryTagCommitTypeCapability Areas
+
+ + +
+
+ + +
+
+
+
Vendor Support Matrix
+

DPU / IPU Hardware Coverage

+

Which functional capability areas each vendor bridge covers in this release.

+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
VendorHardwareBridge RepoStorage OffloadSecure NetworkingInventory & TelemetryProvisioning
NVIDIABlueField DPUopi-nvidia-bridge v0.1.2✓✓✓—
IntelMEV / IPUopi-intel-bridge v0.2.0✓✓✓—
MarvellOCTEON DPUopi-marvell-bridge v0.1.2✓✓✓—
MangoBoostDPUopi-mangoboost-bridge✓———
+
+
+
+ + + +
+
+
+
OPI Blueprints
+

What is an OPI Blueprint?

+

+ An OPI Blueprint is more than a demo — it is a fully documented, partner-attributed, production-grade deployment pattern that an enterprise customer or systems integrator could replicate in their own data center. +

+
+ +
+ +
+
Blueprint vs Demo
+
Production-Ready Patterns
+
A Technical Demo proves a technology works. A Blueprint shows how to put it into production. Blueprints are aimed at solutions architects and IT decision-makers — not just developers — and answer "how do I deploy this at my company?"
+
+ +
+
Required Deliverables
+
Six Components
+
Every OPI Blueprint must include: a reference architecture diagram, a validated bill of materials (BOM), a deployment guide with IaC artifacts (Terraform, Ansible, Helm), a use case narrative, validated test results, and clear partner/integrator attribution with a path to professional services.
+
+ +
+
Multi-Vendor by Design
+
Vendor-Neutral Interop
+
Blueprints are built on OPI's open standards, so customers aren't locked into a single vendor's stack. They demonstrate real multi-vendor interoperability — e.g. Dell chassis + Intel IPU + F5 BIG-IP Next + Red Hat OpenShift — all programmed through unified OPI APIs.
+
+ +
+
Have a Blueprint Idea?
+
How to Contribute
+
Draft a one-pager (use case, target audience, OPI components, hardware/software stack, contributing partners), bring it to the TSC, get resource alignment, then build, document, validate and publish. Blueprints live in the OPI Lab and OPI GitHub, and are showcased at events like OCP Global Summit and GTC.
+
+ +
+ +
+ OPI Blueprints are actively being developed for the Abstraction release and beyond. The blueprint_url fields in opi-release.json will link to each official Blueprint document as it is published. Interested in contributing a Blueprint? Reach out via the OPI main repo or bring it to the TSC. +
+
+
+ + +
+
+
+
Getting Started
+

Start Building with OPI

+

Four entry points depending on what you want to do — from consuming APIs to running full integration tests.

+
+ +
+
+
Step 01
+
API Definitions
+
Clone opi-api or consume the protobuf schemas directly from the Buf Schema Registry.
+
buf dep update
buf generate
+
+
+
Step 02
+
Reference PoC Stack
+
Clone opi-poc and spin up a full local OPI stack backed by SPDK, FRR, and strongSwan.
+
git clone github.com/opiproject/opi-poc
docker compose up
+
+
+
Step 03
+
CLI Clients
+
Install godpu (Go) or pydpu (Python) to drive any OPI-compliant bridge from the command line.
+
go install github.com/opiproject/godpu@latest

pip install pydpu
+
+
+
Step 04
+
Pick a Vendor Bridge
+
Choose the bridge matching your DPU hardware — NVIDIA, Intel, Marvell, or MangoBoost — and follow its README.
+
docker pull ghcr.io/opiproject/
opi-<vendor>-bridge:main
+
+
+
Step 05
+
Capability Areas & Blueprints
+
Browse the capability areas above to see which repos cover which functional domain. Official OPI Blueprints (end-to-end, partner-attributed production patterns) are actively being developed — see the Blueprint section for details.
+
cat opi-release.json | jq '.release.repositories[].blueprints'
+
+
+
Step 06
+
Zero-Touch Provisioning
+
Use sztp + sztpd to provision a DPU from scratch via RFC 8572 sZTP, then automate configuration with ansible-opi-dpu.
+
docker pull ghcr.io/opiproject/sztp:main
docker pull ghcr.io/opiproject/sztpd:main
+
+
+
+
+ + + + + + + diff --git a/releases/abstraction/opi-release-notes.md b/releases/abstraction/opi-release-notes.md new file mode 100644 index 0000000..58e0dce --- /dev/null +++ b/releases/abstraction/opi-release-notes.md @@ -0,0 +1,297 @@ +# OPI Project — "Abstraction" Release (v0.1.0) + +**Date:** 2026-05-08 +**Codename:** Abstraction +**Release Manifest:** [`opi-release.json`](./opi-release.json) +**GitHub Org:** [github.com/opiproject](https://github.com/opiproject) +**Website:** [opiproject.org](https://opiproject.org) + +--- + +## Overview + +This is the first coordinated release of the +**Open Programmable Infrastructure (OPI) Project**, +codenamed **"Abstraction"**. + +The name reflects the core mission of this release: to establish a +vendor-neutral, hardware-agnostic API abstraction layer across all DPU/IPU +capabilities — so that any workload, orchestrator, or platform can program +any DPU without hardware-specific code. + +This release pins a specific tag and commit across 22 participating +repositories, spanning API definitions, reference bridge implementations, +vendor bridges, client tooling, Kubernetes integrations, provisioning +infrastructure, and observability tooling. + +--- + +## What is OPI? + +OPI defines open, portable gRPC/protobuf APIs that abstract DPU/IPU hardware +capabilities across vendors. An application or orchestration platform targeting +OPI APIs can work with any compliant DPU — NVIDIA BlueField, Intel MEV, Marvell +OCTEON, or MangoBoost — without hardware-specific code. + +--- + +## A Note on Terminology: Capability Areas vs. Blueprints + +This release uses two distinct concepts that are intentionally kept separate: + +### Capability Areas + +A **Capability Area** describes which OPI functional domain a repository +contributes to — what it technically enables. The four capability areas in +this release are: + +- **Storage Offload** — NVMe-oF frontend/backend, VirtIO, encryption, + QoS, AIO volumes, CSI +- **Secure Networking** — EVPN gateway, IPsec IKE + ESP datapath offload, + CNI/Kubernetes integration +- **DPU Inventory & Telemetry** — SMBIOS-based hardware inventory, + OpenTelemetry metrics and traces +- **DPU Provisioning & Lifecycle** — sZTP (RFC 8572), Redfish, + Ansible lifecycle automation + +Every repository in this release manifest carries a `keywords` field in +[`opi-release.json`](./opi-release.json) describing its technical domain. + +### OPI Blueprints + +An **OPI Blueprint** is something much more specific. Per the +[OPI Blueprint Framework](https://github.com/opiproject/opi/blob/main/Docs/blueprint_framework.md), +a Blueprint is a **fully documented, partner-attributed, production-grade +deployment pattern** that an enterprise customer or systems integrator could +replicate. It must include: + +- A reference architecture diagram +- A validated bill of materials (BOM) with specific hardware and software versions +- A deployment guide with IaC artifacts (Terraform, Ansible, Helm, etc.) +- A use case narrative aimed at IT decision-makers, not just developers +- Validated test results +- Clear partner/integrator attribution and a path to professional services + +A Blueprint answers *"how do I deploy this at my company?"* — not just +*"does it work?"*. Repos that have been validated as part of an official +Blueprint carry a `blueprints` field in the release manifest. Repos that have +not are listed with an empty `blueprints` array, regardless of how capable +they are technically. + +**OPI currently has one official Blueprint** — see below. + +--- + +## Official Blueprint: Kubernetes Network Function Offload + +**Partners:** Intel · Marvell · Red Hat · F5 / NGINX +**Hardware:** Intel IPU E2100, Marvell OCTEON DPU +**Software:** Red Hat OpenShift, F5 NGINX +**Status:** Official + +This Blueprint demonstrates end-to-end Kubernetes-native network function +offload to DPU/IPU hardware using OPI APIs, with Red Hat OpenShift as the +orchestration layer and F5 NGINX as the application delivery controller. +It is the first OPI Blueprint to meet the full framework requirements: +reference architecture, BOM, deployment guide, IaC artifacts, and validated +test results with multi-vendor partner attribution. + +The following repositories from this release have been validated as part +of this Blueprint: + +| Repository | Tag | Role in Blueprint | +| --- | --- | --- | +| [opi-api](https://github.com/opiproject/opi-api) | v1.0.0 | Defines the EVPN and networking gRPC API contracts | +| [opi-evpn-bridge](https://github.com/opiproject/opi-evpn-bridge) | v0.2.0 | EVPN gateway reference implementation (FRR) | +| [opi-intel-bridge](https://github.com/opiproject/opi-intel-bridge) | v0.2.0 | Intel IPU E2100 vendor implementation | +| [opi-marvell-bridge](https://github.com/opiproject/opi-marvell-bridge) | v0.1.2 | Marvell OCTEON vendor implementation | +| [opi-gateway-evpn-cni](https://github.com/opiproject/opi-gateway-evpn-cni) | v1.0.0 | Kubernetes CNI plugin connecting pods to EVPN gateway | +| [opi-cni](https://github.com/opiproject/opi-cni) | v1.0.0 | Generic OPI CNI integration for Kubernetes | +| [sessionOffload](https://github.com/opiproject/sessionOffload) | v1 | Session offload API for datapath acceleration | +| [godpu](https://github.com/opiproject/godpu) | v0.2.0 | Go CLI used for Blueprint validation | +| [pydpu](https://github.com/opiproject/pydpu) | v0.2.1 | Python CLI used for Blueprint validation | +| [opi-poc](https://github.com/opiproject/opi-poc) | v1.0.0 | Integration test suite and CI PoC compose stack | + +--- + +## Repository Summary Table + +| Repository | Tag | Commit | Capability Area(s) | Type | In Blueprint | +| --- | --- | --- | --- | --- | --- | +| [opi-api](https://github.com/opiproject/opi-api) | v1.0.0 | `0b58e48b` | Storage Offload, Secure Networking, DPU Inventory & Telemetry | API Definitions | ✅ | +| [opi-poc](https://github.com/opiproject/opi-poc) | v1.0.0 | `3118ff80` | All | Integration Testing | ✅ | +| [opi-smbios-bridge](https://github.com/opiproject/opi-smbios-bridge) | v0.1.2 | `85e800cf` | DPU Inventory & Telemetry | Bridge | — | +| [opi-mangoboost-bridge](https://github.com/opiproject/opi-mangoboost-bridge) | v1.0.0 | `c086acf5` | Storage Offload | Vendor Bridge | — | +| [spdk](https://github.com/opiproject/spdk) | v24.01 | `0b102908` | Storage Offload | Container Packaging | — | +| [opi-spdk-bridge](https://github.com/opiproject/opi-spdk-bridge) | v0.1.1 | `88edfc9e` | Storage Offload | Bridge | — | +| [opi-intel-bridge](https://github.com/opiproject/opi-intel-bridge) | v0.2.0 | `83a34699` | Storage Offload, Secure Networking, DPU Inventory & Telemetry | Vendor Bridge | ✅ | +| [opi-evpn-bridge](https://github.com/opiproject/opi-evpn-bridge) | v0.2.0 | `5440fb9f` | Secure Networking | Bridge | ✅ | +| [sztp](https://github.com/opiproject/sztp) | v0.2.0 | `8ae1e7d5` | DPU Provisioning & Lifecycle | Provisioning | — | +| [godpu](https://github.com/opiproject/godpu) | v0.2.0 | `eb709487` | Storage Offload, Secure Networking, DPU Inventory & Telemetry | Client Tooling | ✅ | +| [opi-strongswan-bridge](https://github.com/opiproject/opi-strongswan-bridge) | v0.1.1 | `98602d8c` | Secure Networking | Bridge | — | +| [otel](https://github.com/opiproject/otel) | v1.0.0 | `d7b81b0b` | DPU Inventory & Telemetry | Observability | — | +| [pydpu](https://github.com/opiproject/pydpu) | v0.2.1 | `3f4b838a` | Storage Offload, Secure Networking, DPU Inventory & Telemetry | Client Tooling | ✅ | +| [ansible-opi-dpu](https://github.com/opiproject/ansible-opi-dpu) | v1.0.0 | `42d5399b` | DPU Provisioning & Lifecycle | Automation | — | +| [opi-nvidia-bridge](https://github.com/opiproject/opi-nvidia-bridge) | v0.1.2 | `16632dfb` | Storage Offload, Secure Networking, DPU Inventory & Telemetry | Vendor Bridge | — | +| [opi-marvell-bridge](https://github.com/opiproject/opi-marvell-bridge) | v0.1.2 | `a2338007` | Storage Offload, Secure Networking, DPU Inventory & Telemetry | Vendor Bridge | ✅ | +| [opi-gateway-evpn-cni](https://github.com/opiproject/opi-gateway-evpn-cni) | v1.0.0 | `a2207f82` | Secure Networking | CNI Plugin | ✅ | +| [gospdk](https://github.com/opiproject/gospdk) | v1.0.0 | `98d71122` | Storage Offload | Shared Library | — | +| [opi-prov-life](https://github.com/opiproject/opi-prov-life) | v1.0.0 | `c18ec9e1` | DPU Provisioning & Lifecycle | Working Group Docs | — | +| [opi-cni](https://github.com/opiproject/opi-cni) | v1.0.0 | `8751c724` | Secure Networking | CNI Plugin | ✅ | +| [sztpd](https://github.com/opiproject/sztpd) | 0.0.15 | `40c371ea` | DPU Provisioning & Lifecycle | Container Packaging | — | +| [sessionOffload](https://github.com/opiproject/sessionOffload) | v1 | `8708e583` | Secure Networking | API Definitions | ✅ | + +> **Note:** Repositories showing `—` for tag/commit have not yet cut a +> formal release tag. They participate in this release at their current HEAD. +> Future releases will require all repositories to carry a tag. + +--- + +## Highlights by Capability Area + +### Storage Offload + +The OPI Storage API (`opi_api.storage.v1`) defines a comprehensive set of +gRPC services covering the full NVMe-oF stack: frontend NVMe, VirtIO block +and SCSI, middleend encryption and QoS, remote NVMe controllers, and generic +AIO/Null volumes. + +- **`opi-spdk-bridge` v0.1.1** is the reference implementation, translating + all storage gRPC services to SPDK JSON-RPC. It is the canonical backend + used in CI and PoC validation. +- **`spdk` v24.01** provides the containerized SPDK engine used by the bridge + and integration tests. +- **`gospdk`** provides the reusable Go SPDK JSON-RPC client library, + covering NVMf, LVol, BDev, Crypto, and Accel subsystems. +- Vendor storage bridges: **`opi-nvidia-bridge` v0.1.2**, + **`opi-intel-bridge` v0.2.0**, **`opi-marvell-bridge` v0.1.2**, + **`opi-mangoboost-bridge`**, and + each implement the same storage gRPC surface against + their respective DPU SDKs. + +### Secure Networking + +The OPI Networking API (`opi_api.network.evpn_gw.v1alpha1`) models an EVPN +gateway with VRFs, Logical Bridges, Bridge Ports, and SVIs. The complementary +`sessionOffload` API covers ESP datapath offload. + +- **`opi-evpn-bridge` v0.2.0** is the reference implementation backed by + FRRouting (FRR). v0.2.0 adds pagination, TLS options, Redis-backed state + persistence, and richer integration tests. +- **`opi-strongswan-bridge` v0.1.1** bridges the OPI IPsec gRPC API to the + strongSwan IKE daemon via the vici protocol. The combined strongSwan + + sessionOffload pattern is the recommended OPI IPsec architecture: + strongSwan manages the control plane; the DPU handles the data plane. +- **`opi-gateway-evpn-cni`** is a Kubernetes CNI plugin (Multus-compatible) + that calls the EVPN bridge gRPC to create BridgePorts for xPU VFs attached + to pods. +- **`opi-cni`** provides a broader Kubernetes CNI integration layer for + OPI-managed DPU/IPU network functions. +- **`sessionOffload` v1** defines the session offload API for + hardware-accelerating TCP/UDP/IPsec ESP datapath flows directly on DPU + hardware. + +### DPU Inventory & Telemetry + +The OPI Inventory API (`opi_api.inventory.v1`) exposes DPU/IPU hardware +information (CPU, memory, PCIe, firmware) via a standard gRPC interface. + +- **`opi-smbios-bridge` v0.1.2** is the reference implementation, reading + SMBIOS tables via dmidecode and the ghw Go library. +- **`otel`** extends inventory with live telemetry — collecting CPU usage, + memory, storage I/O, network throughput, and Redfish thermal sensor data via + the OpenTelemetry collector pipeline, with traces exported to Zipkin/Jaeger. + +### DPU Provisioning & Lifecycle + +- **`sztp` v0.2.0** implements RFC 8572 Secure Zero Touch Provisioning + end-to-end: a Go agent, a wn-sztpd-1 bootstrap server client, and a DHCP + option 143 redirect mechanism for zero-touch DPU onboarding. +- **`sztpd` 0.0.15** packages the wn-sztpd-1 bootstrap server daemon as a + container for use in OPI lab and production sZTP deployments. +- **`ansible-opi-dpu` v1.0.0** provides Ansible roles and playbooks for + automating DPU/IPU provisioning, configuration, and lifecycle management at + scale. +- **`opi-prov-life`** serves as the working group documentation hub, + covering sZTP, PXE, Redfish, and lifecycle management blueprints and + architecture specs. + +--- + +## Client Libraries + +OPI provides first-class client libraries in two languages so that +orchestration platforms and test frameworks can interact with any OPI-compliant +bridge without writing raw gRPC boilerplate: + +- **`godpu` v0.2.0** — Go CLI and library. Supports `storage`, `evpn`, + `ipsec`, and `inventory` sub-commands. Used in all OPI CI pipelines. +- **`pydpu` v0.2.1** — Python client library and CLI. Python equivalent of + godpu. Published to PyPI. + +--- + +## Vendor DPU/IPU Support Matrix + +| Vendor | Hardware | Bridge Repo | Storage Offload | Secure Networking | DPU Inventory | Provisioning | +| --- | --- | --- | :---: | :---: | :---: | :---: | +| NVIDIA | BlueField DPU | opi-nvidia-bridge v0.1.2 | ✅ | ✅ | ✅ | — | +| Intel | MEV / IPU | opi-intel-bridge v0.2.0 | ✅ | ✅ | ✅ | — | +| Marvell | OCTEON DPU | opi-marvell-bridge v0.1.2 | ✅ | ✅ | ✅ | — | +| MangoBoost | DPU | opi-mangoboost-bridge | ✅ | — | — | — | +| Reference (SPDK) | Software | opi-spdk-bridge v0.1.1 | ✅ | — | — | — | +| Reference (FRR) | Software | opi-evpn-bridge v0.2.0 | — | ✅ | — | — | +| Ref (strongSwan) | Software | opi-strongswan-bridge v0.1.1 | — | ✅ | — | — | +| Reference (SMBIOS) | Software | opi-smbios-bridge v0.1.2 | — | — | ✅ | — | + +--- + +## Repositories Without a Release Tag + +The following repositories participate in this release at their current +HEAD but have not yet cut a formal tag. The OPI TSC recommends these repos +establish a release tagging process before v0.2.0: + +`otel`, `opi-gateway-evpn-cni`, `gospdk`, `opi-prov-life`, `opi-cni`, +`smbios-validation-tool`, `spdk-csi` + +--- + +## Excluded Repositories + +The following repositories are part of the `opiproject` GitHub organization +but are intentionally excluded from this release manifest (infrastructure, +governance, and website repos): + +`dpu-operator`, `opi`, `lab-private`, `actions`, `lab`, `artwork`, `opiproject.org` + +--- + +## Getting Started + +To get started with OPI, the recommended entry points are: + +1. **API definitions** — clone [`opi-api`](https://github.com/opiproject/opi-api) + or consume from the [Buf Schema Registry](https://buf.build/opiproject/opi-api) +2. **Reference PoC** — clone [`opi-poc`](https://github.com/opiproject/opi-poc) + and run `docker compose up` to spin up a full local OPI stack backed by + SPDK, FRR, and strongSwan +3. **CLI client** — install [`godpu`](https://github.com/opiproject/godpu) + (`go install github.com/opiproject/godpu@latest`) or + [`pydpu`](https://github.com/opiproject/pydpu) (`pip install pydpu`) +4. **Vendor bridge** — pick the bridge matching your DPU hardware and + follow its README +5. **Blueprint** — see the + [Kubernetes Network Function Offload](#official-blueprint-kubernetes-network-function-offload) + section above for the first end-to-end, production-grade OPI deployment + pattern + +--- + +## Links + +- Website: [https://opiproject.org](https://opiproject.org) +- GitHub: [https://github.com/opiproject](https://github.com/opiproject) +- Blueprint Framework: [opi/Docs/blueprint_framework.md](https://github.com/opiproject/opi/blob/main/Docs/blueprint_framework.md) +- Mailing list / community: see [opi](https://github.com/opiproject/opi) main repo +- Release manifest (machine-readable): [`opi-release.json`](./opi-release.json) diff --git a/releases/abstraction/opi-release.json b/releases/abstraction/opi-release.json new file mode 100644 index 0000000..bf101eb --- /dev/null +++ b/releases/abstraction/opi-release.json @@ -0,0 +1,694 @@ +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "$id": "https://github.com/opiproject/opi/releases/opi-release-schema.json", + "release": { + "version": "v0.1.0", + "date": "2026-03-07", + "description": "OPI Project \"Abstraction\" Release (v0.1.0) — the first coordinated OPI release manifest. Lists each participating repository with its pinned tag/commit, the OPI APIs it implements, the OPI blueprints it belongs to, and other metadata useful for integration and verification.", + "repositories": [ + { + "name": "opi-api", + "github_url": "https://github.com/opiproject/opi-api", + "description": "Open Programmable Infrastructure API and Behavioral Model — protobuf/gRPC definitions for all OPI services, published to Buf Schema Registry (BSR)", + "tag": "v1.0.0", + "commit": "0b58e48b3c91095621ffb1124b89094c6eac3ec7", + "language": "Protobuf / Python", + "type": "api-definitions", + "opi_apis_implemented": [ + "opi_api.storage.v1", + "opi_api.network.evpn_gw.v1alpha1", + "opi_api.security.v1", + "opi_api.inventory.v1" + ], + "container_image": "", + "notes": "Source of truth for all OPI protobuf definitions. Every bridge and client library depends on this repo.", + "blueprints": [ + { + "name": "Kubernetes Network Function Offload", + "status": "official", + "partners": [ + "Intel", + "Marvell", + "Red Hat", + "F5 / NGINX" + ], + "hardware": [ + "Intel IPU E2100", + "Marvell OCTEON DPU" + ], + "software": [ + "Red Hat OpenShift", + "F5 NGINX" + ], + "description": "End-to-end Blueprint demonstrating Kubernetes-native network function offload to DPU/IPU hardware using OPI APIs, Red Hat OpenShift as the orchestration layer, and F5 NGINX as the application delivery controller.", + "blueprint_url": "" + } + ], + "keywords": [ + "Storage", + "Networking", + "Security", + "Inventory" + ] + }, + { + "name": "opi-poc", + "github_url": "https://github.com/opiproject/opi-poc", + "description": "Developer Platform and Proof of Concept — integration test suite, reference Docker Compose stacks, and CI PoCs covering all OPI working group areas", + "tag": "v1.0.0", + "commit": "3118ff80f39b5a364451ef2c7e3580abddcd02bf", + "language": "Shell / Docker Compose", + "type": "integration-testing", + "opi_apis_implemented": [], + "container_image": "", + "notes": "Every new OPI API must be covered by an integration test added here. Used as the primary CI PoC validation environment.", + "blueprints": [ + { + "name": "Kubernetes Network Function Offload", + "status": "official", + "partners": [ + "Intel", + "Marvell", + "Red Hat", + "F5 / NGINX" + ], + "hardware": [ + "Intel IPU E2100", + "Marvell OCTEON DPU" + ], + "software": [ + "Red Hat OpenShift", + "F5 NGINX" + ], + "description": "End-to-end Blueprint demonstrating Kubernetes-native network function offload to DPU/IPU hardware using OPI APIs, Red Hat OpenShift as the orchestration layer, and F5 NGINX as the application delivery controller.", + "blueprint_url": "" + } + ], + "keywords": [ + "Storage", + "Networking", + "Security", + "Inventory", + "Platform Management", + "Provisioning & Lifecycle" + ] + }, + { + "name": "opi-smbios-bridge", + "github_url": "https://github.com/opiproject/opi-smbios-bridge", + "description": "OPI gRPC to SMBIOS bridge — exposes DPU/IPU hardware inventory via OPI Inventory gRPC APIs using dmidecode and the ghw Go library", + "tag": "v0.1.2", + "commit": "85e800cf8cfaf958368974533eb5cacf7180a276", + "language": "Go", + "type": "bridge", + "opi_apis_implemented": [ + "opi_api.inventory.v1.InventorySvc" + ], + "container_image": "ghcr.io/opiproject/opi-smbios-bridge:main", + "notes": "Reference implementation of the OPI Inventory API. Uses dmidecode and ghw to read SMBIOS data from the DPU/IPU.", + "blueprints": [], + "keywords": [ + "Inventory", + "Platform Management" + ] + }, + { + "name": "opi-mangoboost-bridge", + "github_url": "https://github.com/opiproject/opi-mangoboost-bridge", + "description": "OPI gRPC to MangoBoost DPU bridge — NVMe/TCP initiator and target hardware offload via MangoBoost SDK (vendor implementation)", + "tag": "v1.0.0", + "commit": "c086acf5e0fa61cbb4c077b06da7b0f7643d5e6d", + "language": "Go", + "type": "vendor-bridge", + "vendor": "MangoBoost", + "opi_apis_implemented": [ + "opi_api.storage.v1.FrontendNvmeService", + "opi_api.storage.v1.NvmeRemoteControllerService" + ], + "container_image": "ghcr.io/opiproject/opi-mangoboost-bridge:main", + "notes": "Targets MangoBoost DPUs with focus on NVMe/TCP hardware offload.", + "blueprints": [], + "keywords": [ + "Storage" + ] + }, + { + "name": "spdk", + "github_url": "https://github.com/opiproject/spdk", + "description": "OPI-maintained Dockerfile and CI wrapper for upstream SPDK (Storage Performance Development Kit)", + "tag": "v24.01", + "commit": "0b102908e908330e8f033a2691bc01de83b8e8d9", + "language": "Dockerfile", + "type": "container-packaging", + "opi_apis_implemented": [], + "container_image": "ghcr.io/opiproject/spdk:main", + "notes": "Reproducible SPDK container image used as the backend for opi-spdk-bridge and opi-poc integration tests.", + "blueprints": [], + "keywords": [ + "Storage" + ] + }, + { + "name": "opi-spdk-bridge", + "github_url": "https://github.com/opiproject/opi-spdk-bridge", + "description": "OPI Storage gRPC to SPDK JSON-RPC bridge — reference implementation of all OPI storage services backed by SPDK", + "tag": "v0.1.1", + "commit": "88edfc9eb5de0c3e011a543098976d753820792b", + "language": "Go", + "type": "bridge", + "opi_apis_implemented": [ + "opi_api.storage.v1.FrontendNvmeService", + "opi_api.storage.v1.FrontendVirtioBlkService", + "opi_api.storage.v1.FrontendVirtioScsiService", + "opi_api.storage.v1.MiddleendEncryptionService", + "opi_api.storage.v1.MiddleendQosVolumeService", + "opi_api.storage.v1.NvmeRemoteControllerService", + "opi_api.storage.v1.AioVolumeService", + "opi_api.storage.v1.NullVolumeService" + ], + "container_image": "ghcr.io/opiproject/opi-spdk-bridge:main", + "notes": "Canonical storage reference bridge. Translates OPI gRPC to SPDK JSON-RPC. Released v0.1.1 in February 2025.", + "blueprints": [], + "keywords": [ + "Storage" + ] + }, + { + "name": "opi-intel-bridge", + "github_url": "https://github.com/opiproject/opi-intel-bridge", + "description": "OPI gRPC to Intel IPU/MEV bridge (vendor implementation)", + "tag": "v0.2.0", + "commit": "83a34699bf6dd0e69787fe3217cbc1c29a561287", + "language": "Go", + "type": "vendor-bridge", + "vendor": "Intel", + "opi_apis_implemented": [ + "opi_api.storage.v1.FrontendNvmeService", + "opi_api.storage.v1.AioVolumeService", + "opi_api.storage.v1.NvmeRemoteControllerService", + "opi_api.security.v1.IPsec", + "opi_api.inventory.v1.InventorySvc" + ], + "container_image": "ghcr.io/opiproject/opi-intel-bridge:main", + "notes": "Targets Intel MEV (Mount Evans) IPU devices.", + "blueprints": [ + { + "name": "Kubernetes Network Function Offload", + "status": "official", + "partners": [ + "Intel", + "Marvell", + "Red Hat", + "F5 / NGINX" + ], + "hardware": [ + "Intel IPU E2100", + "Marvell OCTEON DPU" + ], + "software": [ + "Red Hat OpenShift", + "F5 NGINX" + ], + "description": "End-to-end Blueprint demonstrating Kubernetes-native network function offload to DPU/IPU hardware using OPI APIs, Red Hat OpenShift as the orchestration layer, and F5 NGINX as the application delivery controller.", + "blueprint_url": "" + } + ], + "keywords": [ + "Storage", + "Security", + "Inventory" + ] + }, + { + "name": "opi-evpn-bridge", + "github_url": "https://github.com/opiproject/opi-evpn-bridge", + "description": "OPI gRPC to EVPN Gateway FRR bridge — implements OPI network APIs using FRRouting (FRR) and vtysh", + "tag": "v0.2.0", + "commit": "5440fb9f85ed80d74658412a0cf3ff352b8d29dd", + "language": "Go", + "type": "bridge", + "opi_apis_implemented": [ + "opi_api.network.evpn_gw.v1alpha1.VrfService", + "opi_api.network.evpn_gw.v1alpha1.LogicalBridgeService", + "opi_api.network.evpn_gw.v1alpha1.BridgePortService", + "opi_api.network.evpn_gw.v1alpha1.SviService" + ], + "container_image": "ghcr.io/opiproject/opi-evpn-bridge:main", + "notes": "Released v0.2.0 in June 2025, adding pagination, TLS options, Redis integration, and richer tests.", + "blueprints": [ + { + "name": "Kubernetes Network Function Offload", + "status": "official", + "partners": [ + "Intel", + "Marvell", + "Red Hat", + "F5 / NGINX" + ], + "hardware": [ + "Intel IPU E2100", + "Marvell OCTEON DPU" + ], + "software": [ + "Red Hat OpenShift", + "F5 NGINX" + ], + "description": "End-to-end Blueprint demonstrating Kubernetes-native network function offload to DPU/IPU hardware using OPI APIs, Red Hat OpenShift as the orchestration layer, and F5 NGINX as the application delivery controller.", + "blueprint_url": "" + } + ], + "keywords": [ + "Networking" + ] + }, + { + "name": "sztp", + "github_url": "https://github.com/opiproject/sztp", + "description": "Secure Zero Touch Provisioning (sZTP) — Go agent, bootstrap server client (wn-sztpd-1), and simulator implementing RFC 8572", + "tag": "v0.2.0", + "commit": "8ae1e7d5aa79d2d07cfad0c035e66fbfcb16ce10", + "language": "Go", + "type": "provisioning", + "opi_apis_implemented": [ + "ietf-sztp-bootstrap-server (RFC 8572 RESTCONF)" + ], + "container_image": "ghcr.io/opiproject/sztp:main", + "notes": "Implements RFC 8572 Secure ZTP. Agent connects to bootstrap server via DHCP option 143 redirect, fetches and applies onboarding information.", + "blueprints": [], + "keywords": [ + "Platform Management", + "Provisioning & Lifecycle" + ] + }, + { + "name": "godpu", + "github_url": "https://github.com/opiproject/godpu", + "description": "Go CLI and library for communicating with DPUs and IPUs via all OPI gRPC APIs — the standard integration test client across all bridges", + "tag": "v0.2.0", + "commit": "eb709487adb3b92d5229b89c33e6a7070acabf31", + "language": "Go", + "type": "client-tooling", + "opi_apis_implemented": [], + "container_image": "ghcr.io/opiproject/godpu:main", + "notes": "Supports storage, evpn, ipsec, and inventory sub-commands. Used in CI and referenced from every bridge README.", + "blueprints": [ + { + "name": "Kubernetes Network Function Offload", + "status": "official", + "partners": [ + "Intel", + "Marvell", + "Red Hat", + "F5 / NGINX" + ], + "hardware": [ + "Intel IPU E2100", + "Marvell OCTEON DPU" + ], + "software": [ + "Red Hat OpenShift", + "F5 NGINX" + ], + "description": "End-to-end Blueprint demonstrating Kubernetes-native network function offload to DPU/IPU hardware using OPI APIs, Red Hat OpenShift as the orchestration layer, and F5 NGINX as the application delivery controller.", + "blueprint_url": "" + } + ], + "keywords": [ + "Storage", + "Networking", + "Security", + "Inventory" + ] + }, + { + "name": "opi-strongswan-bridge", + "github_url": "https://github.com/opiproject/opi-strongswan-bridge", + "description": "OPI IPsec gRPC to strongSwan vici API bridge — bridges OPI Security API to the strongSwan IKE daemon", + "tag": "v0.1.1", + "commit": "98602d8c52671b3dd95a81490634ab0dc3d5806b", + "language": "Go", + "type": "bridge", + "opi_apis_implemented": [ + "opi_api.security.v1.IPsec" + ], + "container_image": "ghcr.io/opiproject/opi-strongswan-bridge:main", + "notes": "Works in tandem with sessionOffload APIs to provide full IPsec experience: IKE session creation via strongSwan vici, ESP session offload via sessionOffload.", + "blueprints": [], + "keywords": [ + "Security" + ] + }, + { + "name": "otel", + "github_url": "https://github.com/opiproject/otel", + "description": "OPI Monitoring and Telemetry via OpenTelemetry (OTEL) — PoC for collecting DPU/IPU metrics (CPU, memory, storage I/O, network, Redfish thermal) and traces via the OTEL collector", + "tag": "v1.0.0", + "commit": "d7b81b0bdfcdea999819ad1e3a33b9dbfe8475b1", + "language": "Go / Shell", + "type": "observability", + "opi_apis_implemented": [ + "OpenTelemetry Collector (OTEL) metrics and tracing pipeline" + ], + "container_image": "ghcr.io/opiproject/otel:main", + "notes": "Collects DPU metrics including mem_free, cpu_usage, dpu_num_blocks, net_bytes_recv, redfish_thermal_fans_reading_rpm. Streams traces to Zipkin/Jaeger. Mandates a common set of metrics across NVIDIA, Intel, and Marvell DPUs.", + "blueprints": [], + "keywords": [ + "Platform Management", + "Inventory" + ] + }, + { + "name": "pydpu", + "github_url": "https://github.com/opiproject/pydpu", + "description": "Python client library and CLI for communicating with DPUs and IPUs via OPI gRPC APIs — Python equivalent of godpu", + "tag": "v0.2.1", + "commit": "3f4b838ac93f4336056931b8f2df8fb8321f659d", + "language": "Python", + "type": "client-tooling", + "opi_apis_implemented": [], + "container_image": "ghcr.io/opiproject/pydpu:main", + "notes": "Python gRPC client for OPI APIs. Referenced alongside godpu in opi-api storage README as an official client.", + "blueprints": [ + { + "name": "Kubernetes Network Function Offload", + "status": "official", + "partners": [ + "Intel", + "Marvell", + "Red Hat", + "F5 / NGINX" + ], + "hardware": [ + "Intel IPU E2100", + "Marvell OCTEON DPU" + ], + "software": [ + "Red Hat OpenShift", + "F5 NGINX" + ], + "description": "End-to-end Blueprint demonstrating Kubernetes-native network function offload to DPU/IPU hardware using OPI APIs, Red Hat OpenShift as the orchestration layer, and F5 NGINX as the application delivery controller.", + "blueprint_url": "" + } + ], + "keywords": [ + "Storage", + "Networking", + "Security", + "Inventory" + ] + }, + { + "name": "ansible-opi-dpu", + "github_url": "https://github.com/opiproject/ansible-opi-dpu", + "description": "Ansible roles and playbooks for automating DPU/IPU provisioning, configuration, and lifecycle management in OPI lab environments", + "tag": "v1.0.0", + "commit": "42d5399b59b1b9dfa0485510850c8b19fc6469d9", + "language": "Ansible / YAML", + "type": "automation", + "opi_apis_implemented": [], + "container_image": "", + "notes": "Part of the OPI Lab automation tooling alongside Grafana dashboards and sZTP workflows. Used for DPU bring-up and configuration automation.", + "blueprints": [], + "keywords": [ + "Platform Management", + "Provisioning & Lifecycle" + ] + }, + { + "name": "opi-nvidia-bridge", + "github_url": "https://github.com/opiproject/opi-nvidia-bridge", + "description": "OPI gRPC to NVIDIA BlueField DPU bridge via SNAP and DOCA (vendor implementation)", + "tag": "v0.1.2", + "commit": "16632dfb215fb39d7409b63813a43c23052a0904", + "language": "Go", + "type": "vendor-bridge", + "vendor": "NVIDIA", + "opi_apis_implemented": [ + "opi_api.storage.v1.FrontendNvmeService", + "opi_api.storage.v1.FrontendVirtioBlkService", + "opi_api.storage.v1.FrontendVirtioScsiService", + "opi_api.storage.v1.MiddleendService", + "opi_api.storage.v1.NvmeRemoteControllerService", + "opi_api.storage.v1.AioVolumeService", + "opi_api.storage.v1.NullVolumeService", + "opi_api.security.v1.IPsec", + "opi_api.inventory.v1.InventorySvc" + ], + "container_image": "ghcr.io/opiproject/opi-nvidia-bridge:main", + "notes": "Requires NVIDIA SNAP service and /var/tmp/spdk.sock. Communicates with BlueField DPU via DOCA SDK. Requires Redis and Jaeger before starting bridge.", + "blueprints": [], + "keywords": [ + "Storage", + "Security", + "Inventory" + ] + }, + { + "name": "opi-marvell-bridge", + "github_url": "https://github.com/opiproject/opi-marvell-bridge", + "description": "OPI gRPC to Marvell OCTEON DPU bridge (vendor implementation)", + "tag": "v0.1.2", + "commit": "a2338007b42d5bc281f90209d5fdaf927467209c", + "language": "Go", + "type": "vendor-bridge", + "vendor": "Marvell", + "opi_apis_implemented": [ + "opi_api.storage.v1.FrontendNvmeService", + "opi_api.storage.v1.FrontendVirtioBlkService", + "opi_api.storage.v1.FrontendVirtioScsiService", + "opi_api.storage.v1.NvmeRemoteControllerService", + "opi_api.security.v1.IPsec", + "opi_api.inventory.v1.InventorySvc" + ], + "container_image": "ghcr.io/opiproject/opi-marvell-bridge:main", + "notes": "Targets Marvell OCTEON DPU family.", + "blueprints": [ + { + "name": "Kubernetes Network Function Offload", + "status": "official", + "partners": [ + "Intel", + "Marvell", + "Red Hat", + "F5 / NGINX" + ], + "hardware": [ + "Intel IPU E2100", + "Marvell OCTEON DPU" + ], + "software": [ + "Red Hat OpenShift", + "F5 NGINX" + ], + "description": "End-to-end Blueprint demonstrating Kubernetes-native network function offload to DPU/IPU hardware using OPI APIs, Red Hat OpenShift as the orchestration layer, and F5 NGINX as the application delivery controller.", + "blueprint_url": "" + } + ], + "keywords": [ + "Storage", + "Security", + "Inventory" + ] + }, + { + "name": "opi-gateway-evpn-cni", + "github_url": "https://github.com/opiproject/opi-gateway-evpn-cni", + "description": "OPI Kubernetes CNI plugin — bridges Multus/SR-IOV VFs on DPU/IPU to the OPI EVPN gateway via gRPC BridgePort calls", + "tag": "v1.0.0", + "commit": "a2207f8230bec1495e7a044daf43e2649e2cc568", + "language": "Go", + "type": "cni-plugin", + "opi_apis_implemented": [ + "opi_api.network.evpn_gw.v1alpha1.BridgePortService" + ], + "container_image": "ghcr.io/opiproject/opi-gateway-evpn-cni:main", + "notes": "Called by Multus when a pod is scheduled. Creates BridgePorts in opi-evpn-bridge for xPU VFs. Supports kernel and userspace (DPDK/VFIO) drivers.", + "blueprints": [ + { + "name": "Kubernetes Network Function Offload", + "status": "official", + "partners": [ + "Intel", + "Marvell", + "Red Hat", + "F5 / NGINX" + ], + "hardware": [ + "Intel IPU E2100", + "Marvell OCTEON DPU" + ], + "software": [ + "Red Hat OpenShift", + "F5 NGINX" + ], + "description": "End-to-end Blueprint demonstrating Kubernetes-native network function offload to DPU/IPU hardware using OPI APIs, Red Hat OpenShift as the orchestration layer, and F5 NGINX as the application delivery controller.", + "blueprint_url": "" + } + ], + "keywords": [ + "Networking" + ] + }, + { + "name": "gospdk", + "github_url": "https://github.com/opiproject/gospdk", + "description": "Go library implementing the SPDK JSON-RPC protocol — shared client library used by opi-spdk-bridge and other bridges that communicate with SPDK", + "tag": "v1.0.0", + "commit": "98d71122a73b2e5eb0eb8b2a277a5c34bb997a6b", + "language": "Go", + "type": "shared-library", + "opi_apis_implemented": [ + "SPDK JSON-RPC (https://spdk.io/doc/jsonrpc.html)" + ], + "container_image": "", + "notes": "Provides JSONRPC interface with unix socket and TCP transport. Covers NVMf, LVol, BDev, Crypto, and Accel SPDK subsystems. Used as a dependency by opi-spdk-bridge.", + "blueprints": [], + "keywords": [ + "Storage" + ] + }, + { + "name": "opi-prov-life", + "github_url": "https://github.com/opiproject/opi-prov-life", + "description": "Provisioning, Lifecycle and Platform Management working group hub — specs, architecture docs, and PoCs for sZTP, PXE, Redfish, and lifecycle workflows", + "tag": "v1.0.0", + "commit": "c18ec9e1d6db357af18c0884e49b564ca5e07337", + "language": "Markdown / Shell", + "type": "working-group-docs", + "opi_apis_implemented": [], + "container_image": "", + "notes": "Working group documentation hub. Covers sZTP (RFC 8572), Redfish, PXE, and DPU/IPU lifecycle management patterns and blueprints.", + "blueprints": [], + "keywords": [ + "Platform Management", + "Provisioning & Lifecycle" + ] + }, + { + "name": "opi-cni", + "github_url": "https://github.com/opiproject/opi-cni", + "description": "OPI CNI plugin — generic Kubernetes CNI integration for OPI-managed DPU/IPU network functions", + "tag": "v1.0.0", + "commit": "8751c724cc5fc11e2d50d9bbef7cf4bdf70a4c67", + "language": "Go", + "type": "cni-plugin", + "opi_apis_implemented": [ + "opi_api.network.evpn_gw.v1alpha1" + ], + "container_image": "ghcr.io/opiproject/opi-cni:main", + "notes": "Companion to opi-gateway-evpn-cni. Provides broader CNI integration for OPI-managed DPU/IPU network functions in Kubernetes environments.", + "blueprints": [ + { + "name": "Kubernetes Network Function Offload", + "status": "official", + "partners": [ + "Intel", + "Marvell", + "Red Hat", + "F5 / NGINX" + ], + "hardware": [ + "Intel IPU E2100", + "Marvell OCTEON DPU" + ], + "software": [ + "Red Hat OpenShift", + "F5 NGINX" + ], + "description": "End-to-end Blueprint demonstrating Kubernetes-native network function offload to DPU/IPU hardware using OPI APIs, Red Hat OpenShift as the orchestration layer, and F5 NGINX as the application delivery controller.", + "blueprint_url": "" + } + ], + "keywords": [ + "Networking" + ] + }, + { + "name": "sztpd", + "github_url": "https://github.com/opiproject/sztpd", + "description": "OPI-maintained container packaging for sztpd (wn-sztpd-1) — the RFC 8572 SZTP bootstrap server daemon used in OPI provisioning workflows", + "tag": "0.0.15", + "commit": "40c371ea48ecf257fdf1a6080b8166a871158403", + "language": "Dockerfile / Shell", + "type": "container-packaging", + "opi_apis_implemented": [ + "ietf-sztp-bootstrap-server (RFC 8572 RESTCONF)" + ], + "container_image": "ghcr.io/opiproject/sztpd:main", + "notes": "Packages the wn-sztpd-1 bootstrap server used by the sztp agent repo. Provides the server side of the RFC 8572 sZTP flow.", + "blueprints": [], + "keywords": [ + "Provisioning & Lifecycle", + "Platform Management" + ] + }, + { + "name": "sessionOffload", + "github_url": "https://github.com/opiproject/sessionOffload", + "description": "OPI Session Offload API — gRPC API definitions and reference implementation for offloading network sessions (TCP/UDP/IPsec ESP) to DPU/IPU hardware", + "tag": "v1", + "commit": "8708e583e2a376a9ba0229d21ca26d48c182a240", + "language": "Go / Protobuf", + "type": "api-definitions", + "opi_apis_implemented": [ + "opi_api.network.session_offload.v1alpha1" + ], + "container_image": "", + "notes": "Used in tandem with opi-strongswan-bridge: strongSwan handles IKE session negotiation, sessionOffload handles ESP datapath offload to DPU hardware accelerators.", + "blueprints": [ + { + "name": "Kubernetes Network Function Offload", + "status": "official", + "partners": [ + "Intel", + "Marvell", + "Red Hat", + "F5 / NGINX" + ], + "hardware": [ + "Intel IPU E2100", + "Marvell OCTEON DPU" + ], + "software": [ + "Red Hat OpenShift", + "F5 NGINX" + ], + "description": "End-to-end Blueprint demonstrating Kubernetes-native network function offload to DPU/IPU hardware using OPI APIs, Red Hat OpenShift as the orchestration layer, and F5 NGINX as the application delivery controller.", + "blueprint_url": "" + } + ], + "keywords": [ + "Networking", + "Security" + ] + } + ], + "codename": "Abstraction" + }, + "_metadata": { + "schema_version": "1.0.0", + "generated_by": "OPI Release Working Group", + "total_repos": 22, + "excluded_repos": [ + "dpu-operator", + "opi", + "lab-private", + "actions", + "lab", + "artwork", + "opiproject.org" + ], + "field_guide": { + "tag": "Semantic version tag for this release, e.g. v0.1.0. Set per-repo at release time.", + "commit": "Full 40-character Git commit SHA corresponding to the tag. Set per-repo at release time.", + "type": "One of: api-definitions | bridge | vendor-bridge | cni-plugin | csi-driver | client-tooling | shared-library | integration-testing | container-packaging | provisioning | working-group-docs | observability | automation | testing-tool", + "opi_apis_implemented": "Fully-qualified gRPC service names from opi-api protobuf definitions, or standard identifiers (e.g. RFC number) for non-gRPC APIs.", + "vendor": "Present only on vendor-bridge repos. Identifies the hardware vendor.", + "container_image": "Primary GHCR or Docker Hub image for this repo, if published.", + "notes": "Human-readable context, constraints, dependencies, or integration notes.", + "capability_areas": "Array of OPI functional capability areas this repo contributes to. Each entry has: area (the OPI capability domain: Storage Offload | Secure Networking | DPU Inventory & Telemetry | DPU Provisioning & Lifecycle), role (one of: api | reference-implementation | vendor-implementation | client | infrastructure | automation | specification | integration-testing | testing-tool), description (how this repo contributes technically to that capability area). NOTE: capability_areas describes what a repo CAN do technically. It is distinct from blueprints, which are official validated production deployments.", + "blueprints": "Array of official OPI Blueprints this repo has been validated in. Per the OPI Blueprint Framework, a Blueprint is a fully documented, partner-attributed, production-grade deployment pattern with BOM, architecture diagram, deployment guide, IaC artifacts, and validated test results. Empty array means the repo has not yet been included in an official Blueprint. Each entry has: name, status (official | draft | proposed), partners (list of contributing vendors/integrators), hardware, software, description, blueprint_url.", + "keywords": "Functional area tags describing what this repo does. Used for filtering and discovery. Values: Storage | Networking | Security | Inventory | Platform Management | Provisioning & Lifecycle. These are NOT OPI Blueprints — see the 'blueprints' array for blueprint participation." + } + } +} \ No newline at end of file