vss-manage-video-io-storage
Installation
SKILL.md
Prerequisites
- Active VSS deployment reachable on
$HOST_IP(seevss-deploy-profileandreferences/). - NGC credentials in
$NGC_CLI_API_KEYand$NVIDIA_API_KEYfor any image pulls. curl,jq, and Docker available on the caller.
VIOS Operations
You are a VIOS API assistant. Interact with the VIOS microservice to manage cameras/sensors, RTSP streams, recordings, snapshots, and storage. Use when asked to: add a camera, add an RTSP stream, list sensors, show configured sensors/cameras/streams, check stream status, get a snapshot, download a clip, upload a video file, or manage video storage. Always query the VIOS API directly using curl — do not navigate the UI.
Reference contracts shipped with this skill
This skill bundles four reference files under references/. Read whichever applies to the task in front of you:
| File | Purpose | Audience |
|---|---|---|
references/api-reference.md |
The full VIOS REST API reference (the runtime contract) — sensor management, storage, snapshots, clip extraction, WebRTC live/replay, RTSP proxy, recorder, service configuration, service discovery. Read this when invoking any VIOS API operation. | Operational users + this skill itself |
references/nvstreamer-api-reference.md |
The NvStreamer REST API reference — version, sensor list/info/status/streams, the three upload methods (PUT v2 / PUT v1 / POST multipart) with the nvstreamer-* custom headers, delete, snapshots (frame-indexed live, timestamp-indexed storage), storage info, filesystem scan. NvStreamer (vss-vios-nvstreamer, the streamer-adaptor variant of launch_vst) is brought up by the same profiles that bring VIOS up — dev-profile-alerts, dev-profile-lvs, dev-profile-search, all warehouse profiles. See integrate-vios-service.md § Topology B for the deployment side. Read this when uploading test / sample videos to be served as synthetic RTSP, retrieving the RTSP URL NvStreamer generated for a file, or driving the canonical NvStreamer → VIOS handoff (upload to NvStreamer → read RTSP URL → register that URL with VIOS via /sensor/add). |
Operational users + skill authors composing the upload → RTSP URL → VIOS /sensor/add flow |
references/integrate-vios-service.md |
The integration contract — how VIOS plugs into other VSS microservices. Documents required peer services (RT-VLM, ELK, Kafka, Redis, sdr-controller / SDRC), the structured component_services: block consumed by the vss-build-vision-agent skill's Step 4, integration inputs/outputs (Kafka topics, REST endpoints, file paths), environment variables, network requirements, and known integration constraints (e.g. the /url-variant double-http:// bug, the VIOS + SDRC patching requirement). Read this when authoring a skill that talks to VIOS as a peer, when composing a new VSS deployment, or when debugging caption-pipeline wiring. |
Skill authors, deployment composers, pair-file maintainers |
references/deploy-vios-service.md |
The deployment contract — what it takes to bring VIOS up. Documents container images and tags (nvcr.io/nvstaging/vss-core/vss-vios-*:2.1.0-26.05.2), GPU / CPU / memory / storage requirements, startup behavior + healthcheck tuning, required environment variables (notably VST_INSTALL_ADDITIONAL_PACKAGES=true for the libav apt-install step that gates uploads), known deployment issues (volume drift, libav missing, 502 from leftover containers), prerequisites, dry-run, verify-deployment, and tear-down commands. Read this when VIOS isn't running and you (or your caller) need to deploy it standalone, when debugging container-startup failures, or when authoring a deploy skill that wraps VIOS. |
Operators, deploy-skill authors |