doca-urom-svc

Operate the DOCA UROM Service container on BlueField Arm for host-offloaded remote memory operations.

3.2k|370|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/NVIDIA/skills --skill doca-urom-svc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doca-urom-svc
Source: https://github.com/NVIDIA/skills/tree/main/skills/doca-urom-svc
Command: npx skills add https://github.com/NVIDIA/skills --skill doca-urom-svc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying and operating the DOCA UROM Service on BlueField DPUs involves a paired host-library/service version contract, UCX component and collective configuration, queue sizing, and Comch/RDMA access boundaries that are easy to misconfigure and hard to debug.

Core Features & Use Cases

  • Deployment guidance: Pull the NGC container, set daemon CLI flags and UROM_PLUGIN_PATH, and start the service under the BlueField container runtime.
  • Configuration and version pairing: Choose the UCX component/collective surface, size enqueue queues, wire DOCA Comch endpoint pairing, and align host doca-urom library versions with the service container tag per the DOCA Compatibility Policy.
  • Layered debugging and observability: Diagnose failures across container runtime, service-side resources, RDMA substrate, and paired-version mismatch layers using logs and substrate counters.
  • Use Case: An HPC platform team offloading MPI/UCX collectives from host CPUs to BlueField DPUs uses this Skill to deploy the service, verify a single-operation smoke test, and troubleshoot NOT_PERMITTED or stalled-completion errors.

Quick Start

Ask your agent to deploy and configure the DOCA UROM Service container on a BlueField paired with hosts using the doca-urom library.

Frequently Asked Questions about doca-urom-svc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy the DOCA UROM Service on a BlueField DPU?

Pull the service container from NGC at the tag matching your paired host doca-urom library version, set the daemon's SERVICE_ARGS flags and UROM_PLUGIN_PATH, mount the plugins directory, and start it under the BlueField container runtime per the public Container Deployment Guide.

When should I use DOCA UROM Service for MPI or UCX workloads?

Deploy it when host nodes use the doca-urom library and host CPU cost of posting RDMA communication is the bottleneck. Do not deploy it when hosts do not use doca-urom, when the stack is neither MPI nor UCX, or when the BlueField generation cannot expose the intended collectives.

Why does doca-urom enqueue return NOT_PERMITTED on my host?

DOCA_ERROR_NOT_PERMITTED is a DOCA Comch pairing, RDMA permission, or host-side doca_dev access signal, not a service-side authorization rejection. The shipped UROM service binary has no standalone authorization list; verify the Comch endpoint pairing and RDMA permissions.

Why do UROM operations enqueue but never complete?

Stalled completions usually come from a saturated service-side queue, a stuck handler, or an unhealthy underlying RDMA substrate. Check container state and service logs first, then inspect RDMA substrate counters before changing any service configuration.

Does the host doca-urom library version need to match the service container?

Yes. The host-side doca-urom library version and the DPU-side service container tag are a paired contract governed by the DOCA Compatibility Policy. A mismatch fails subtly as NOT_SUPPORTED errors or silent stalls rather than a loud refusal.

Can I run multiple UROM service containers on one BlueField?

No. One service container owns the BlueField's UROM execution state; running two competing containers on the same BlueField is a configuration error. Redundancy is achieved with multiple BlueFields each running their own service instance.