Skip to main content

Overview

Open Programmable Infrastructure (OPI) is a Linux Foundation project that defines a standard interface for DPUs/IPUs. As an OPI member, MangoBoost provides a gRPC bridge that drives the Mango SDK through the OPI API. It covers the storage APIs today; networking and security are planned.

mango-cli is still the recommended way to configure MangoBoost devices. The OPI API reaches the same capabilities in a vendor-neutral way, which suits automation and mixed-vendor fleets.

OPI MangoBoost Storage Bridge​

opi-mangoboost-bridge is a gRPC server on the DPU (or host). It translates OPI commands from a management client such as grpc_cli or godpu into Mango SDK and SPDK calls, and reports current state — subsystems, controllers, namespaces and paths. It is control plane only: once a resource is provisioned, the NVMe-oF data path runs entirely in hardware, with no host or SoC CPU in the I/O path.

Using OPI together with the Mango SDK, you can enable the NVMe-oF initiator offload and NVMe-oF target offload features through a single vendor-neutral API:

  • Target offload — BoostX™ NRT serves locally attached SSDs as NVMe-oF subsystems over RDMA. Any standard initiator can connect.
  • Initiator offload — the DPU attaches a remote NVMe-oF target and presents it to its own host as a local NVMe device.

OPI-ARCH

Both control paths end at the same SPDK calls. The OPI bridge receives commands over an OOB channel and translates them; mango-cli calls SPDK directly on the target, and reaches it from the host over the in-band channel on the initiator.

The User Guide demonstrates how these NVMe-oF features are configured through the Mango SDK using the OPI API.

Supported Features​

  • NVMe-oF target offload over RDMA
  • NVMe-oF initiator offload