بنقرة واحدة
ovstorage-contributor-author-storage-plugin
Use when adding or reviewing a storage backend plugin for ovstorage.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when adding or reviewing a storage backend plugin for ovstorage.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | ovstorage-contributor-author-storage-plugin |
| description | Use when adding or reviewing a storage backend plugin for ovstorage. |
| license | CC-BY-4.0 |
| version | 0.1.0 |
| author | NVIDIA Omniverse |
| tags | ["ovstorage","plugin","storage"] |
| tools | ["Read","Bash"] |
| compatibility | Requires an ovstorage checkout, Rust toolchain, and storage plugin ABI docs. Backend SDK credentials are user-supplied when applicable. |
Implement a backend plugin that advertises truthful capabilities, streams bytes without buffering whole objects, maps errors into ovstorage codes, and passes the plugin conformance harness.
docs/public/plugin-development/README.md
for the shared C ABI, manifest, loader, and build loop.docs/public/plugin-storage/README.md
for the storage-specific Factory and Backend contract.ovstorage-plugin-file
before introducing vendor SDK complexity.make verify before merge.Unsupported and do not advertise the matching
capability.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 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.