# STRATUM Technical Guide > Task-oriented documentation for installing STRATUM, building and operating datacenters, managing Fabrics and Arsenal, using Mission Planner, extending guests with STRATUM GPU and Guest Tools, operating STRATUM AI, and troubleshooting the platform. This map lists completed, indexable Technical Guide pages. Five future platform-deployment pages remain intentionally omitted until their customer documentation is complete. ## Start Here - [Technical Guide Overview](https://www.stratumvisor.com/guide/): Install STRATUM, build a datacenter, operate workloads, manage the fabrics, extend guests, and troubleshoot the platform from one task-oriented guide. - [Choose a Deployment Model](https://www.stratumvisor.com/guide/start/deployment-models/): Choose the deployment model that matches the environment. Docker or Podman is the normal path; Kubernetes/OpenShift and additional platform packages are separate deployment options. ## Install STRATUM with Docker or Podman - [Docker & Podman Overview](https://www.stratumvisor.com/guide/deploy/docker-podman/): STRATUM is delivered as a container image. The host supplies networking, device access, filesystem paths, and services; Host Manager (the stratum-host application) prepares that host and starts STRATUM. - [Host Requirements & Name Resolution](https://www.stratumvisor.com/guide/deploy/docker-podman/requirements/): Before installation, make sure the controller can resolve every STRATUM host. Compute and storage workers only need to resolve and reach the controller name used for enrollment and operation. - [Stage STRATUM & Launch Host Manager](https://www.stratumvisor.com/guide/deploy/docker-podman/host-manager/): Copy the STRATUM release files to the host and start Host Manager (the stratum-host application). Host Manager is where host-specific settings are reviewed and applied before STRATUM starts. - [Configure STRATUM Host Manager](https://www.stratumvisor.com/guide/deploy/docker-podman/configure-host/): Use Host Manager to define runtime, host, network, certificate, demo-data, GPU, and passthrough settings before starting STRATUM. - [Apply Host Setup](https://www.stratumvisor.com/guide/deploy/docker-podman/apply-host-setup/): Apply Host Setup once the host identity and settings are correct. This prepares the host and loads the STRATUM application image without making the application image itself the durable data store. - [Start STRATUM](https://www.stratumvisor.com/guide/deploy/docker-podman/start-stratum/): Start STRATUM from Host Manager and keep the startup output visible until the controller reports a completed start. - [Runtime, Persistent State & Logs](https://www.stratumvisor.com/guide/deploy/docker-podman/runtime-state-logs/): Know where the replaceable application image ends and persistent STRATUM state begins. These paths and logs are the first place to look when host startup is not behaving as expected. - [First Sign-In & License](https://www.stratumvisor.com/guide/deploy/first-sign-in-license/): Open the STRATUM interface, sign in, install the license, and verify the controller reaches a licensed state before building the datacenter. - [Update STRATUM](https://www.stratumvisor.com/guide/deploy/docker-podman/update-stratum/): Preserve the current image tag, load and version the new release, then replace the running container through stratum-host so upgrade-state preservation and persistent host data remain intact. ## Kubernetes and OpenShift - [Kubernetes & OpenShift Overview](https://www.stratumvisor.com/guide/deploy/kubernetes-openshift/): Kubernetes and OpenShift are an additional STRATUM deployment model. Bring up the controller first, validate it, then add compute and storage roles deliberately. - [Prepare the Kubernetes/OpenShift Host](https://www.stratumvisor.com/guide/deploy/kubernetes-openshift/prerequisites/): Select a suitable worker node and verify /dev/kvm and /dev/net/tun. - [Publish the STRATUM Image to a Registry](https://www.stratumvisor.com/guide/deploy/kubernetes-openshift/registry/): Inspect the supplied STRATUM container archive. - [Deploy the STRATUM Controller with Helm](https://www.stratumvisor.com/guide/deploy/kubernetes-openshift/controller/): Use the current controller values layer as the canonical first install. - [Validate the Deployment](https://www.stratumvisor.com/guide/deploy/kubernetes-openshift/validate/): Watch pods, verify PVC binding, inspect logs, and test the STRATUM web endpoint. - [Create the Worker Enrollment Secret](https://www.stratumvisor.com/guide/deploy/kubernetes-openshift/worker-enrollment/): Obtain the controller CA and STRATUM worker enrollment token. - [Add Compute and Storage Workers](https://www.stratumvisor.com/guide/deploy/kubernetes-openshift/workers/): Add compute workers using the worker values layer. - [OpenShift Advanced Configuration & Troubleshooting](https://www.stratumvisor.com/guide/deploy/kubernetes-openshift/troubleshooting/): OpenShift-specific hostNetwork, SCC, port-forward, same-node controller+worker labels, and debugging. ## Core Concepts - [Fabrics, Arsenal & Mission Planner](https://www.stratumvisor.com/guide/concepts/core-model/): Fabrics provide capacity, Arsenal provides versioned content, and Mission Planner is where those resources and artifacts become a running datacenter. - [Controller, Workers & the STRATUM Continuum](https://www.stratumvisor.com/guide/concepts/continuum/): The STRATUM Continuum joins controllers, compute workers, storage workers, and accelerator resources into one operational fabric without requiring every role to live on one host. - [Datacenter as an OCI Application](https://www.stratumvisor.com/guide/concepts/oci-datacenter-application/): A STRATUM datacenter can be delivered as a versioned Open Container Initiative application while its durable runtime state remains separate from the replaceable image. - [Versioning, Lineage & Portability](https://www.stratumvisor.com/guide/concepts/versioning-lineage-portability/): STRATUM keeps revisions, lineage, topology, and relationships attached to the objects they describe so a workload or datacenter can be reproduced and moved as a system rather than as disconnected files. ## Fabrics and Scaling - [Network Fabric Overview](https://www.stratumvisor.com/guide/fabrics/network-fabric/) - [Inter-Datacenter Networks](https://www.stratumvisor.com/guide/fabrics/inter-datacenter-networks/): Network Fabric shows the controller, enrolled workers, Continuum settings, and the current connectivity state of each fabric node. - [Add a Compute Worker](https://www.stratumvisor.com/guide/fabrics/add-compute-worker/): Download enrollment token and controller CA. - [Add a Storage Worker](https://www.stratumvisor.com/guide/fabrics/add-storage-worker/): Repeat enrollment for a dedicated storage worker. - [Compute Fabric](https://www.stratumvisor.com/guide/fabrics/compute-fabric/): Compute Fabric shows CPU and memory capacity across execution hosts together with active and failed VM jobs. - [High Availability & Workload Portability](https://www.stratumvisor.com/guide/fabrics/high-availability/): Restart movable workloads on compatible execution workers while distributed networking and remote storage relationships remain part of the STRATUM fabric. - [Storage Fabric Placement & Bake](https://www.stratumvisor.com/guide/fabrics/storage-fabric/): Assign or move VM image storage between storage workers by drag-and-drop. - [Encrypt & Decrypt VM Storage](https://www.stratumvisor.com/guide/fabrics/storage-encryption/): Encrypt and decrypt VM storage from Storage Fabric. - [AI Accelerator Fabric](https://www.stratumvisor.com/guide/fabrics/accelerator-fabric/): AI Accelerator Fabric shows GPU classes, inventory, leases, and provider resources that STRATUM can present to workloads across the Continuum. ## Arsenal - [STRATUM Arsenal Overview](https://www.stratumvisor.com/guide/arsenal/): Arsenal is the versioned content system behind STRATUM deployments: templates, VM images, ISO media, software, configuration, AI Skills, and files. - [Create an Arsenal Template](https://www.stratumvisor.com/guide/arsenal/create-template/): Create an Arsenal Template with reusable workload identity, VMM, firmware, CPU, memory, network, GPU, and advanced hardware defaults. - [Create and Manage VM Images](https://www.stratumvisor.com/guide/arsenal/vm-images/): Create a VM image version under a template family. - [ISO, Software & Configuration Content](https://www.stratumvisor.com/guide/arsenal/content-libraries/): Arsenal stores reusable ISO media, software, and configuration content alongside templates and VM images. - [Import an Arsenal Bundle](https://www.stratumvisor.com/guide/arsenal/import-bundle/): Import an Arsenal bundle, name it, watch transfer progress, and verify it appears in Templates. - [Promote a VM to Arsenal](https://www.stratumvisor.com/guide/arsenal/promote-vm/): Select a stopped VM, promote it to a versioned Arsenal VM image, and verify it in the image library. - [Template History, Revisions & Lineage](https://www.stratumvisor.com/guide/arsenal/history-lineage/): Revision history and lineage show how an Arsenal object changed over time and which revision is selected for deployment. - [Side-Load Workload Images](https://www.stratumvisor.com/guide/arsenal/side-load-images/): Side-load legacy/custom KVM workload images into the packaged STRATUM environment. ## Network Operations Center - [Global NOC Operations](https://www.stratumvisor.com/guide/noc/): Operate the STRATUM estate from a global view, filter datacenter state, inspect STRATUMops observations, follow Inter-Datacenter context, and open a selected datacenter directly in Mission Planner. ## Mission Planner - [Mission Planner Interface](https://www.stratumvisor.com/guide/mission-planner/interface/): Mission Planner is the construction and operations surface for a STRATUM datacenter. Learn the canvas regions first, then use the task pages for deployment, wiring, operation, and packaging. - [Create a Datacenter](https://www.stratumvisor.com/guide/mission-planner/create-datacenter/): Create a datacenter with identity, classification, placement, and coordinates. - [Deploy a Network Switch](https://www.stratumvisor.com/guide/mission-planner/deploy-switch/): Choose a switch from System Arsenal, deploy it, and adjust deployment parameters such as port count. - [Deploy a System](https://www.stratumvisor.com/guide/mission-planner/deploy-system/): Deploy a system from System Arsenal. - [Connect Systems & Ports](https://www.stratumvisor.com/guide/mission-planner/connect-systems/): Create links by clicking/dragging between endpoints. - [Groups & Multi-Selection](https://www.stratumvisor.com/guide/mission-planner/groups-multiselect/): Create a visual group container, title/lock it, drag-select multiple nodes, and execute group actions such as power-on. - [Selection Details, Node Menus & Status Pills](https://www.stratumvisor.com/guide/mission-planner/node-controls/): Selection Details and context menus expose the state and actions for the object currently selected on the Mission Planner canvas. - [System Console](https://www.stratumvisor.com/guide/mission-planner/console/): Open a VM or device console. - [Data Layers](https://www.stratumvisor.com/guide/mission-planner/data-layers/): Data Layers control which operational overlays are visible on the Mission Planner canvas. - [Link Impairment](https://www.stratumvisor.com/guide/mission-planner/link-impairment/): Open link editing, configure latency/loss/other impairment controls, apply them, and read impairment state from the canvas/Selection Details. - [Packet Capture & Traffic Visualization](https://www.stratumvisor.com/guide/mission-planner/packet-capture/): Capture live traffic, use Network Flow to separate observed relationships from topology inference, and project the resulting path back onto Mission Planner. - [Snapshots](https://www.stratumvisor.com/guide/mission-planner/snapshots/): Create and manage VM snapshots from the node context menu. - [Move a Workload to Another Execution Host](https://www.stratumvisor.com/guide/mission-planner/move-workload/): Move a VM workload from the Mission Planner context menu. - [Export & Import a Datacenter Package](https://www.stratumvisor.com/guide/mission-planner/datacenter-package/): Export an entire datacenter as a portable package and import it elsewhere. ## GPU and Guest Tools - [STRATUM GPU & Guest Tools Overview](https://www.stratumvisor.com/guide/gpu-guest-tools/): The normal STRATUM GPU path is simple: attach STRATUM GPU, install STRATUM Guest Tools, then run ordinary CUDA applications. - [Install STRATUM Guest Tools](https://www.stratumvisor.com/guide/gpu-guest-tools/install/): Install STRATUM Guest Tools inside the VM to add the guest agent and the STRATUM GPU user-mode driver/runtime integration used by CUDA and NVML applications. - [Verify STRATUM GPU in the Guest](https://www.stratumvisor.com/guide/gpu-guest-tools/verify-gpu/): After Guest Tools are installed, verify that the guest sees the STRATUM GPU device and can query the accelerator before testing CUDA applications. - [Remote GPU Across the STRATUM Continuum](https://www.stratumvisor.com/guide/gpu-guest-tools/remote-gpu-continuum/): Make a physical GPU on one STRATUM worker available to a VM executing somewhere else in the Continuum, including cloud and cross-site deployments. - [STRATUM GPU Firewall](https://www.stratumvisor.com/guide/gpu-guest-tools/gpu-firewall/): Enforce GPU attachment and lease policy at the virtual PCI GPU boundary and understand the path toward CUDA/NVML-aware inspection and automated accelerator threat response. - [CUDA & NVML Validation](https://www.stratumvisor.com/guide/gpu-guest-tools/cuda-nvml-validation/): Use the supplied CUDA and NVML validation utilities as diagnostics. They confirm the GPU path; they are not application configuration requirements. - [Run Ordinary CUDA Applications](https://www.stratumvisor.com/guide/gpu-guest-tools/cuda-applications/): Validate STRATUM GPU with llama.cpp end-to-end: synthetic PCI device and transport checks, CUDA-compatible build flags, device discovery, live inference, and optional nvidia-smi without installing an NVIDIA kernel driver. ## STRATUM AI - [STRATUM AI Overview](https://www.stratumvisor.com/guide/ai/): STRATUM AI is an operational layer for infrastructure and guest work. It is separate from GPU acceleration and expands through Skills, content, node-level operations, and AI Studio. - [Configure STRATUM AI](https://www.stratumvisor.com/guide/ai/configuration/): Configure provider endpoint/model/key and enable STRATUM AI. - [AI Skills & AI Packs](https://www.stratumvisor.com/guide/ai/skills-packs/): AI Skills add reusable operational capability to STRATUM AI. AI Packs package and distribute those capabilities through STRATUM Marketplace. - [AI Inputs: Software & Configuration Content](https://www.stratumvisor.com/guide/ai/content-inputs/): Software and Configuration libraries provide controlled, versioned content that STRATUM AI can use alongside Skills instead of relying on undocumented machine-local state. - [Node-Level AI Operations](https://www.stratumvisor.com/guide/ai/node-operations/) - [AI Mission Control](https://www.stratumvisor.com/guide/ai/mission-control/): Watch live AI guest VM and device operations, including delegated tasks, structured execution and authorized graphical console observations. - [AI Mission History & Results](https://www.stratumvisor.com/guide/ai/mission-history/): Review completed Missions, steps, outcome checks, verification evidence, activity history and optional debug bundles. - [AI TRACE](https://www.stratumvisor.com/guide/ai/trace/): Follow the structured execution path of the STRATUM AI harness through Skills, specialist Roles, planning stages and tool events. - [AI Schedule & Recurring Missions](https://www.stratumvisor.com/guide/ai/schedules/): Schedule one-time, hourly, daily, or weekly AI operations against a captured target snapshot while using the normal STRATUM Mission, policy, approval, and verification pipeline. ## STRATUM AI Studio - [AI Studio Concepts & Operator DAG](https://www.stratumvisor.com/guide/ai/studio/concepts/): Understand the directed acyclic graph (DAG) behind STRATUM AI Studio and how typed nodes compile specialist behavior, Skills, policy, authority, execution and verification into an AI infrastructure operator. - [AI Studio Interface & Canvas](https://www.stratumvisor.com/guide/ai/studio/interface/): Navigate the AI Studio DAG canvas, node palette, Operator selector, Design/Simulate/Trace modes, revision controls and viewport tools. - [Specialist Roles](https://www.stratumvisor.com/guide/ai/studio/operators/): Use specialist Role nodes to give the STRATUM AI Operator infrastructure, network, application, storage, GPU, cloud, cybersecurity, compliance, ISSM and ISSO behavior. - [Skills & Capability Nodes](https://www.stratumvisor.com/guide/ai/studio/skills-capabilities/): Understand every built-in STRATUM AI Studio Skill, how Skills add operational capability, and how typed Skill outputs connect capability into the Operator DAG. - [Context, Connections & Providers](https://www.stratumvisor.com/guide/ai/studio/connections-providers/): Feed live STRATUM context and external connection references into the Operator DAG without turning credentials into prompt text. - [Guardrails, Compliance & Operator Behavior](https://www.stratumvisor.com/guide/ai/studio/llm-prompt/): Define scope, no-go zones, change policy, maintenance windows, compliance overlays and operator behavior that constrain and shape STRATUM AI execution. - [Marketplace Extensibility & AI Packs](https://www.stratumvisor.com/guide/ai/studio/ai-packs/): Extend STRATUM AI by bringing Skills and AI Packs from Marketplace into Arsenal, instantiating them on the AI Studio canvas and configuring them for an Operator. - [Simulate, Publish, Activate & Trace](https://www.stratumvisor.com/guide/ai/studio/execution-trace/): Simulate the Operator DAG without infrastructure mutation, publish versioned Operator revisions, activate one for STRATUM AI, and trace how a Mission moved through policy, approval, execution and verification. ## STRATUM Continuum Security - [Post-Quantum Cryptography (PQC)](https://www.stratumvisor.com/guide/continuum/post-quantum-cryptography/): Enable hybrid quantum-resistant protection for Continuum communications and understand FIPS 203 ML-KEM, FIPS 204 ML-DSA, FIPS 205 SLH-DSA, and cryptographic-module validation boundaries. ## STRATUM Continuum at the Edge - [Edge & Intermittent Connectivity](https://www.stratumvisor.com/guide/continuum/edge/): Use the same STRATUM control plane across satellites, ships, submarines, aircraft, remote industrial sites, drones, and intermittent edge links with site-aware execution, local Storage Fabric, mission-specific HA policy, and tunable Continuum communications. ## Administration - [Execution Policy & CPU Share Factor](https://www.stratumvisor.com/guide/administration/execution-policy/): CPU Share Factor is a STRATUM execution-policy control for allocating CPU capacity when oversubscription is enabled. - [Login Notice](https://www.stratumvisor.com/guide/administration/login-notice/): Configure the notice presented to users before sign-in, including any acknowledgement requirement used by your organization. - [Authentication Providers](https://www.stratumvisor.com/guide/administration/authentication/): Select the identity source used for sign-in. Authentication establishes who the user is; STRATUM Groups and Roles determine what that user can do. - [Microsoft Active Directory](https://www.stratumvisor.com/guide/administration/active-directory/): Configure Microsoft Active Directory connection, directory search, attribute mapping, and save/validation. - [Sessions & Inactivity Timeout](https://www.stratumvisor.com/guide/administration/sessions/): Review active STRATUM sessions and set the inactivity timeout used to expire idle authenticated sessions. - [Users, Groups & Roles](https://www.stratumvisor.com/guide/administration/access-control/): STRATUM separates authentication from authorization. Use Users, Groups, and Roles to control what an authenticated identity is allowed to do. - [Audit Logs & CSV Export](https://www.stratumvisor.com/guide/administration/audit-logs/): Review administrative changes and authorized user activity, filter audit entries, inspect event context, and export the audit record as CSV. ## Migration and Portability - [Migrate a VMware VM into STRATUM](https://www.stratumvisor.com/guide/migration/vmware-to-stratum/): Move an existing VMware guest into STRATUM by exporting it as OVF, converting it with STRATUM Migrate, and importing the resulting Arsenal bundle. - [Promote, Package & Move Workloads](https://www.stratumvisor.com/guide/migration/portability-workflow/): Promotion, Arsenal versioning, datacenter packaging, and workload movement form one portability chain: turn running state into reusable content, preserve relationships, then place it where it should run. ## STRATUMOPS - [Network Paths & Dependencies](https://www.stratumvisor.com/guide/stratumops/network-paths/): Use STRATUMOPS path analysis to follow how systems depend on one another across network relationships instead of reading the topology as isolated nodes. - [Datacenter Lineage, Relationships & Blast Radius](https://www.stratumvisor.com/guide/stratumops/lineage-blast-radius/): STRATUMOPS turns the datacenter model into relationship intelligence: lineage, dependencies, connected objects, and blast radius. ## Tutorials - [Build Your First Datacenter](https://www.stratumvisor.com/guide/tutorials/first-datacenter/): Build the smallest useful STRATUM datacenter by creating a datacenter, deploying a switch and VM, wiring the network, and powering the workload on. - [Install Windows Server 2025](https://www.stratumvisor.com/guide/tutorials/windows-server-2025/): Build a reusable Windows Server 2025 workload from an empty template through installation, driver loading, first boot, and verification. - [Side-Load & Deploy a Network Appliance](https://www.stratumvisor.com/guide/tutorials/network-appliance/): Side-load a KVM network appliance, expose it through System Arsenal, deploy it into Mission Planner, wire it, and verify the appliance boots. ## Alternate Interfaces - [Terminal User Interface & CLI](https://www.stratumvisor.com/guide/alternate-interfaces/tui/): Operate STRATUM datacenters and workloads from a terminal, or use CLI arguments for direct, repeatable and remote infrastructure control over SSH, serial and constrained management paths. - [Legacy UI](https://www.stratumvisor.com/guide/alternate-interfaces/legacy-ui/): Enable an optional virtualization-style inventory and dashboard for Datacenters, VMs, Storage, Networking, Operations and Continuum. ## Troubleshooting - [Host & Runtime Troubleshooting](https://www.stratumvisor.com/guide/troubleshooting/host-runtime/): Troubleshoot from the outside in: host preparation, container state, persistent paths, startup output, and logs before moving deeper into STRATUM. - [VM Execution & Job Troubleshooting](https://www.stratumvisor.com/guide/troubleshooting/execution-jobs/): A failed VM start is an execution problem until proven otherwise. Begin with the job record, then correlate it with worker health, compatibility, storage, and network state. - [GPU & Guest Tools Troubleshooting](https://www.stratumvisor.com/guide/troubleshooting/gpu-guest-tools/): Validate the GPU path in layers: PCI device, Guest Tools driver and agent, control device, STRATUM inventory, CUDA/NVML validation, then the application. - [Kubernetes/OpenShift Troubleshooting](https://www.stratumvisor.com/guide/troubleshooting/kubernetes-openshift/): Keep failed Kubernetes/OpenShift objects in place long enough to inspect them. Pod state, events, PVCs, and container logs usually identify the first rejected dependency.