メニュー
Use when starting a new ovstorage session or recovering from NoRoute, NotConfigured, or Unsupported errors by inspecting configured backends and routes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | ovstorage-user-getting-started |
| description | Use when starting a new ovstorage session or recovering from NoRoute, NotConfigured, or Unsupported errors by inspecting configured backends and routes. |
| license | CC-BY-4.0 |
| version | 0.1.0 |
| author | NVIDIA Omniverse |
| tags | ["ovstorage","onboarding","discovery"] |
| tools | ["Read"] |
| compatibility | Requires ovstorage MCP tools or equivalent library calls. |
Goal: Find out what ovstorage knows about — versions, loaded backends, configured connections, addressable prefixes — before attempting any real work.
When to use this: As the first call in any new session, or when an
operation has failed with NoRoute / NotConfigured / Unsupported
and you need to understand what's actually available.
Call ovstorage_doctor with no arguments.
{
"tool": "ovstorage_doctor",
"arguments": {}
}
The envelope's result field is a DoctorReport:
{
"v": "0.1",
"ok": true,
"operation": "ovstorage_doctor",
"result": {
"ovstorage_version": "0.1.0",
"backend_kinds": [
{"kind": "file", "display_name": "Local files", "supports_runtime_add": false},
{"kind": "s3", "display_name": "Amazon S3", "supports_runtime_add": true}
],
"connections": [
{
"id": "01H...",
"backend_kind": "s3",
"display_name": "my-bucket",
"addresses": ["s3://my-bucket/"],
"auth_state_kind": "Authenticated"
}
],
"address_roots": [
{"address": "s3://my-bucket/", "backend_kind": "s3", "visibility": "User"}
],
"aliases": []
}
}
backend_kinds — every backend type the library can speak to. If the kind you need is missing, no plugin is loaded for it; you can't proceed until one is.connections — backends the user has configured. Authenticated and Anonymous connections are ready to use; AwaitingAuth, AuthFailed, or other non-ready states mean operations against that connection's addresses need credentials or configuration work first.address_roots — the URL prefixes that resolve. If you're about to operate on an address, confirm a prefix here matches it.aliases — convenience name remappings; safe to ignore unless you're working with the alias surface specifically.This call is essentially read-only library state — it doesn't usually fail. If you get an envelope with ok: false, the failure is in the MCP server itself (e.g., server can't start, plugin loading panicked at boot). The error message should explain.
NoRoute / NotConfigureddocs/public/agent/mcp-tools.md — full DoctorReport shape