ovstorage

Deploy and develop against NVIDIA Omniverse Storage APIs on any Kubernetes cluster (MicroK8s, EKS, AKS, GKE, bare metal). Two storage adapters: (1) Example Storage Adapter — Python filesystem reference implementation + Discovery for learning and custom adapter development; (2) S3/Azure Production Storage Adapter — NVIDIA pre-built S3/Azure adapter + Discovery as minimum, expandable with Event Aggregation, Event Consumer, RabbitMQ, Envoy Auth Extension, Storage Navigator, and Contour ingress. Can deploy on the developer's behalf (generating scripts + .env) or guide manual deployment. Custom adapter development covers three APIs: Storage, Notifications, and Permissions. Use when a developer asks about deploying, configuring, validating, troubleshooting, or building any component of the Omniverse Storage APIs stack.

Use when adding or reviewing an authz plugin for ovstorage-broker or ovstorage-rest - covers the AuthzPlugin trait, the 21 operations, the policy-epoch model, and the cdylib cancellation contract.

Use when adding or reviewing a storage backend plugin for ovstorage.

Use when Rust changes affect ovstorage C or C++ headers and checked-in generated headers must be refreshed.

Use when starting an ovstorage-broker locally for development or integration testing - covers a minimal TOML, the cdylib plugin path, and how to hit the listener with broker-client or curl.

Use when checking the Storage API wire contract that ovstorage-plugin-services-client depends on.

Use before opening or merging an ovstorage PR to run the project verification gate and inspect risky diffs.

Use when authoring or rotating the broker's authz policy - covers the [authz] TOML block, plugin selection, policy-epoch advance/invalidate, and grace-window freshness mode.

Use when triaging a misbehaving ovstorage-broker - covers startup failures, authz denies, listener authn mismatches, streaming write aborts, reload misfires, and drain hangs.

Use when deploying the ovstorage-broker daemon to production - covers TOML config, listener authn modes, TLS, policy plug-in, and state directory layout.

Use when wiring observability for a running ovstorage-broker - covers the Prometheus /metrics surface, the 11 metric families, the tracing span fields, and the audit-safe diagnostic shape.

Use when configuring credentials or driving interactive authentication for a direct ovstorage backend connection.

Use when selecting the right ovstorage backend plugin for a task or deciding which route to configure.

Use when connecting an agent client to ovstorage over MCP stdio and mapping common CLI workflows to MCP tools.

Use when removing objects safely, especially recursive directories or targets that need a dry-run first.

Use when starting a new ovstorage session or recovering from NoRoute, NotConfigured, or Unsupported errors by inspecting configured backends and routes.

Use when an ovstorage tool returns ok false and you need to interpret the envelope error and choose the next action.

Use when enumerating objects under a prefix without buffering the whole result set into memory.

Use when an object is large, needs random access, or must be handed to a tool as a stable local path.

Use when loading one bounded object into memory to parse, inspect, hash, or hand its bytes to another tool.

Use when writing a new object without clobbering or updating an existing object with optimistic concurrency.