Vizrt Asset Management (VAM) is a media asset management platform that runs as a set of containerized services on a Kubernetes cluster. You install it once on a Windows host using the vamctl installer. The installer brings up the cluster, deploys the VAM services and hands you a web UI for ongoing operation.
The installer makes substantial changes to the host and needs Administrator rights throughout. Before you run it on a machine you care about, understand that it:
- Uses Hyper-V, which must already be enabled, creates virtual switches, and creates, reconfigures and deletes virtual machines. An install onto a host that already has VAM VMs re-provisions them, which destroys their contents.
- Runs a rootful Podman machine on WSL 2, see Prerequisites > Podman and WSL 2. While configuring it, the installer issues
wsl --shutdown. That stops every WSL distribution on the host, so save any other WSL work first. - Formats the disks you assign to cluster storage. The Deployment Configuration step names each drive it will format before you confirm.
- Installs command-line tooling (kubectl, Helm, talosctl, Podman and others) onto the host.
Use a dedicated host for production. Read Prerequisites first.
What Gets Installed
A single VAM installation consists of:
Component | What it is |
|---|---|
Kubernetes cluster | A small Kubernetes cluster (one or more nodes) that hosts VAM. |
VAM core services | The asset-management services (ingest, search, storage backends). |
Configuration Service | Web UI for managing the installation after setup is complete. |
Supporting infrastructure | Object storage, document store and message broker. |
| The installer and lifecycle tool, kept on disk for upgrades. |
A system that keeps metrics, logs and traces is not part of VAM. Use your own monitoring system, see Prerequisites > Monitoring and Log Storage.
You interact with the installation in these ways:
- The
vamctlinstaller on Windows is used for the first-time install, backup and restore, upgrading the platform to a new VAM version and upgrading Talos Linux on the cluster nodes. - The Configuration Service, a web UI, is used for day-to-day operation, including installing optional packages, changing platform settings, taking backups and viewing cluster health.
- The end-user VAM applications are the actual asset management apps your editors and journalists use. These are out of scope for this document.
Installation Modes
After you accept the terms and conditions, the installer opens on the Prepare Installer step to install and update the local tools. The Choose Workflow step follows, with the workflows Installation, Prepare Offline Bundle, Offline Installation, Backup & Restore, Manage Existing Cluster, Manage Cluster Contexts and Settings. What each one does is in Running the Installer > Choose a Workflow. There is no uninstall workflow. See Uninstalling.
Cluster Topologies
You can install VAM in one of these topologies:
- Single-node: one machine runs everything. Recommended for evaluation and small productions.
- Multi-node: one or more control plane nodes plus worker nodes, for redundancy and capacity. Recommended for production.
The installer supports Hyper-V (the default on Windows) and VMware vSphere for provisioning the nodes. You can also point the installer at an existing Kubernetes cluster instead of letting it create one. See Prerequisites > Deployment Target for what each option requires, and VMware vSphere Deployment for the vSphere path.
Where to Go Next
- For a first-time install, read Prerequisites, then follow Running the Installer.
- For a VMware vSphere target, see VMware vSphere Deployment.
- For your own Kubernetes cluster, see Existing Kubernetes Cluster.
- For a site without internet access, see Offline (Air-Gapped) Installation.
- For day-to-day operation of an existing install, see Configuration Service Overview.
- To upgrade an existing install, see Upgrading.