# Deploy the Demo The demo builds on a clean Scenescape deployment by adding two things: the bundled Retail and Queuing sample video sources, and the corresponding preloaded demo scenes. This lets you explore the UI without connecting your own cameras. Before you begin, complete [Preparation](./preparation.md). ## Docker ### Deploy ```bash export SUPASS='' make demo ``` `make demo` builds the core images (unless `DEMO_REBUILD_IMAGES=false`), starts the `controller` profile, starts the separate demo video-source stack, and uploads the two demo scenes by running `make demo-scenes`. `make demo-scenes` creates a local Python virtual environment at `tools/upload_scenes/.venv` the first time it runs; no system-wide package installation is required. To use prebuilt images instead of building locally, after following the prebuilt option in [Preparation](./preparation.md): ```bash SUPASS='' DEMO_REBUILD_IMAGES=false make demo ``` ### Docker Demo Targets The Docker demo targets start the common sample video sources and upload the standard demo scenes, then select these services or overlays: | Target | Services / behavior | | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `demo` | Controller + Analytics; no ReID. | | `demo-reid` | `demo` plus the selected ReID backend and ReID pipeline override. | | `demo-all` | `demo-reid` plus Mapping and Cluster Analytics. | | `demo-cluster-analytics` | `demo` plus Cluster Analytics; no Mapping or ReID override. | | `demo-tracker` | Tracker + Analytics instead of the Scene Controller. | | `demo-lidar` | `demo` plus the LiDAR/camera intersection fusion overlay. It requires a manually downloaded dataset and first-run model setup; see [Run the LiDAR-Intersection Fusion Demo](../run-lidar-intersection-demo.md). | The `demo-all`, `demo-cluster-analytics`, and `demo-tracker` targets build all service images by default. `demo-lidar` builds the dedicated LiDAR variant. Set `DEMO_REBUILD_IMAGES=false` to skip building when the required images already exist. The ReID targets use VDMS by default. Set `REID_BACKEND=qdrant` to use Qdrant: ```bash make demo-reid make demo-reid REID_BACKEND=qdrant ``` See [Docker Compose Profiles](./deploy-docker.md#docker-compose-profiles) for the underlying profiles, including `demo-tracker` (Tracker + Analytics, no Scene Controller) and `demo-cluster-analytics`. ### Verify Connect and sign in as described in [Deploy on Docker](./deploy-docker.md#verify-a-successful-deployment). Scenescape provides two scenes, Retail and Queuing, that you can explore running from stored video data. ### Uploading Your Own Scenes For scene hierarchies, UUID restoration, and supplying remote MQTT credentials, see [Exporting and Restoring a Hierarchy](../build-a-scene/configure-hierarchy-of-scenes.md#exporting-and-restoring-a-hierarchy). The Manager image includes the `upload-scenes` CLI for batch imports and automation; no host-side Python setup is needed. It runs only when explicitly invoked and does not change Manager startup. Existing standalone scenes are not re-imported by default; their calibration markers are reconciled, so re-running the uploader or `make demo-scenes` is safe. Use `--reuse-existing` when importing overlapping hierarchies or retrying an import. Existing scenes are kept unchanged while missing scenes and hierarchy links are restored; conflicting identities or links are rejected. Without this option, existing hierarchies or imports using `--restore-ids` are rejected. Prepare a directory of per-scene subdirectories, each containing its own `.zip` as produced by the **Export Scene** button of the Web UI. For a local hierarchy, the parent ZIP includes its local descendants, so importing only that ZIP creates the scenes and their links in one invocation. For large maps or hierarchies, pass `--import-timeout 600` to allow a longer response wait for each scene import. The default is 60 seconds; the value must be a positive integer. This is a read timeout, not a total import deadline. Other API requests retain their 60-second timeout. `--wait` controls startup readiness only. A timeout does not cancel or roll back the server-side import: check Manager logs and the imported resources before retrying. While importing, the Manager calls its own REST API to apply scene settings and create cameras, regions, and other resources. Applying the settings of a scene with a `.glb` map re-renders its thumbnail, which can take minutes for large meshes. Each of these internal requests may take up to 300 seconds by default; on Docker Compose deployments, set the `SCENE_IMPORT_REST_TIMEOUT_S` environment variable (positive integer seconds) on the `web` service to change it. The Kubernetes Helm chart does not expose this setting and uses the default. If it is exceeded, the import stops before the cameras and other resources are created and reports `Scene settings update failed (ReadTimeout)`. #### Using the Manager Image For an already-running Docker Compose deployment, run a one-off uploader container using the web service's image, network, and mounted credentials: ```bash docker compose run --rm --no-deps --entrypoint upload-scenes \ --volume "$PWD/my-scenes:/scenes:ro" \ web \ --restauth /run/secrets/controller.auth \ --rootcert /run/secrets/certs/scenescape-ca.pem \ --reuse-existing \ --import-timeout 600 \ https://web.scenescape.intel.com/api/v1 /scenes ``` Without Compose, use the same Manager image version as your deployment and mount the scene directory, auth file, and CA certificate read-only. For example, with `controller.auth` and `scenescape-ca.pem` securely provisioned in the current directory: ```bash export MANAGER_IMAGE='intel/scenescape-manager:' export SCENESCAPE_API_URL='https:///api/v1' docker run --rm --entrypoint upload-scenes \ --mount "type=bind,src=$PWD/my-scenes,dst=/scenes,readonly" \ --mount "type=bind,src=$PWD/controller.auth,dst=/run/secrets/controller.auth,readonly" \ --mount "type=bind,src=$PWD/scenescape-ca.pem,dst=/run/secrets/scenescape-ca.pem,readonly" \ "$MANAGER_IMAGE" \ --restauth /run/secrets/controller.auth \ --rootcert /run/secrets/scenescape-ca.pem \ --reuse-existing \ "$SCENESCAPE_API_URL" /scenes ``` Replace the image version and deployment hostname above. The API URL must be reachable from inside the uploader container and match the server certificate. The image's default non-root user must be able to read the mounted files. This command can target either a Docker or Kubernetes deployment with a reachable API endpoint. #### Host-Side Alternative The standalone uploader remains available in a repository checkout. `make demo`/`make demo-scenes` create and reuse a virtual environment at `tools/upload_scenes/.venv`; create or reuse it directly if you have not run either target yet, since the system Python on the supported Ubuntu setup is externally managed and rejects a bare `pip install`: ```bash python3 -m venv tools/upload_scenes/.venv tools/upload_scenes/.venv/bin/pip install -r tools/upload_scenes/requirements.txt ``` Point the tool at your scene directory: ```bash tools/upload_scenes/.venv/bin/python3 tools/upload_scenes/upload-scenes \ --restauth manager/secrets/controller.auth \ --rootcert manager/secrets/certs/scenescape-ca.pem \ https://web.scenescape.intel.com/api/v1 ./my-scenes ``` `--restauth` also accepts a `user:password` string, and `--insecure` skips certificate verification when the deployment is reached under a name the certificate was not issued for, such as `https://localhost`. The server imports each scene synchronously before it replies, which can take minutes for scenes with large maps. `upload-scenes` waits up to 60 seconds for each import by default; if uploads fail with `Read timed out`, raise the limit with `--import-timeout ` (for example, `--import-timeout 600`). If the deployment is reached through a reverse proxy or a Kubernetes ingress, make sure its read timeout (for example, the NGINX Ingress `nginx.ingress.kubernetes.io/proxy-read-timeout` annotation, which defaults to 60 seconds) is at least as long. Scenes can also be imported through the Web UI: sign in, navigate to **Import Scene**, then select and upload the scene ZIP. ### Stopping the Demo `make demo-close` remembers the selected override and stops the matching deployment, removing all volumes: ```bash make demo-close ``` ## Kubernetes For the standard demo on a new local Kind cluster, build the core images and invoke the Kubernetes demo target from the repository root: ```bash export SUPASS='' export PGPASS='' make build-core demo-k8s ``` The `build-core` goal prepares secrets, builds the core images, and installs models. `demo-k8s` installs the local Kind prerequisites, creates the cluster, loads the images, deploys the Helm chart, starts the demo video sources, and uploads the demo scenes. Use `DEPLOY_PROFILES` to select optional services. For profiles that need Tracker, Mapping, or Cluster Analytics images, use `build-all` instead of `build-core`. For example, to run Controller + ReID + Mapping + Cluster Analytics: ```bash export SUPASS='' export PGPASS='' make build-all demo-k8s DEPLOY_PROFILES='controller mapping cluster-analytics reid' ``` `DEPLOY_PROFILES` accepts `controller`, `tracker`, `mapping`, `cluster-analytics`, and `reid`; the default is `controller`. Tracker replaces the Scene Controller, so do not select both `tracker` and `reid`. ### Existing Cluster For an existing Kubernetes cluster, follow [Deploy on Kubernetes](./deploy-kubernetes.md) and then add the two demo-only pieces below. ### Wire Up the Demo Video Sources The chart does not run a media server itself. Start the bundled Retail and Queuing sample-video stack and point the cluster's `mediaserver` Service at it: see [Video Source (sample/demo camera feeds)](https://github.com/open-edge-platform/scenescape/blob/release-2026.3.0/kubernetes/README.md#video-source-sampledemo-camera-feeds). ### Upload the Demo Scenes Install the upload tool's dependencies once, as shown in [Uploading Your Own Scenes](#uploading-your-own-scenes) above. Then, with `kubectl` access to the cluster and the web service reachable (for example, through the port-forward from [Deploy on Kubernetes](./deploy-kubernetes.md#verify)): ```bash ( set -euo pipefail NAMESPACE="${NAMESPACE:-scenescape}" AUTH_FILE=$(mktemp) trap 'rm -f "$AUTH_FILE"' EXIT AUTH_SECRET_NAMES=$(kubectl get secrets --namespace "$NAMESPACE" \ -o custom-columns=:metadata.name --no-headers | grep -E 'controller[.]auth$' || true) AUTH_SECRET_COUNT=$(printf '%s\n' "$AUTH_SECRET_NAMES" | sed '/^$/d' | wc -l) if [ "$AUTH_SECRET_COUNT" -ne 1 ]; then echo "Expected exactly one controller.auth Secret in namespace $NAMESPACE; found $AUTH_SECRET_COUNT." >&2 exit 1 fi AUTH_SECRET_NAME=$(printf '%s\n' "$AUTH_SECRET_NAMES" | sed -n '1p') kubectl get secret "$AUTH_SECRET_NAME" --namespace "$NAMESPACE" \ -o jsonpath='{.data.controller\.auth}' | base64 -d > "$AUTH_FILE" tools/upload_scenes/.venv/bin/python3 tools/upload_scenes/upload-scenes \ --restauth "$AUTH_FILE" --insecure --wait 300 \ https://localhost:8443/api/v1 sample_data/demo_scenes ) ``` Running this as a subshell with an `EXIT` trap ensures the temporary credential file is removed even if a command fails or the snippet is interrupted. Adjust the host and port to match however you reach the web service. Scenes that already exist are skipped, so re-running this is safe.