Skip to Content
Self HostingSelf-Hosted VM Console

Self-Hosted VM Console

OpenFactory включає self-hosted однохостову VM console для оцінки ISO, KVM, VNC, network-topology, monitoring і benchmark workflows на Linux-машині під вашим контролем. Публічне Compose deployment , lab/evaluation path. Це не hosted OpenFactory build service і не production-ready або air-gapped Enterprise control plane.

Оберіть правильний шлях

NeedSupported path
Build custom ISO from chat or recipeUse hosted OpenFactory builder
Manage local KVM guests and uploaded ISOsUse self-hosted VM console described here
Evaluate benchmarks against local guestsUse self-hosted VM console
Run private production deploymentAgree topology, release artifacts, identity, support, and runbook with OpenFactory before deployment
Claim air-gapped deploymentDo not infer from Compose file; offline dependencies and update procedures require separately qualified deployment

Що містить публічне Compose deployment

Checked-in docker-compose.self-hosted.yml запускає два services:

  • privileged backend, підключений до host libvirt socket і /dev/kvm;
  • frontend на host port 80.

Також монтує host libvirt image directory, read-only source-ISO directory, read-only promoted-golden-image directory і named volume для test state і cleanup journals.

Результуюча console підтримує local VM lifecycle operations, ISO upload, browser VNC, network management і topology, benchmarks і live-machine monitoring. Mode endpoint вимикає hosted image builds, AI conversations, scheduling і policy-document workflows. Feature flags running console , authority для цього deployment.

Важливі межі

  • Default frontend , plain HTTP on port 80.
  • Self-hosted mode розрахований на trusted local evaluation network і сам по собі не дає production identity perimeter.
  • Backend privileged і може reach host libvirt daemon. Treat host access as administrative access.
  • Compose file , single-host. Не дає high availability, external database replication, managed TLS, centralized secrets або automated backup service.
  • Uploaded або promoted images , operator-supplied inputs. Licensing, integrity, patch status і suitability залишаються відповідальністю operator.

Evaluation sequence

  1. Read Prerequisites.
  2. Follow Installation on non-production KVM host.
  3. Check Configuration before changing paths or exposure.
  4. Complete Running and verification.
  5. Read Production boundaries before involving real users or data.

Repository-level cto-gui/SELF-HOSTING.md лишається command-level source of truth для checked-in Compose deployment.

Інтеграція ServiceNowКонфігурація