docs: update architecture to reflect Proxmox migration and correct network configurations
Revised multiple documents to align with the migration from Incus to Proxmox VE 8.4.10. Updated hypervisor, IP ranges, subnet details, and NAT configurations across all relevant files. Marked Incus sections as historical for clarity. Added AI-Stack setup guide for Proxmox LXC.
This commit is contained in:
@@ -0,0 +1,74 @@
|
||||
---
|
||||
type: Journal
|
||||
status: ACTIVE
|
||||
owner: Curator
|
||||
date: 2026-03-06
|
||||
session: Immich & Pangolin — Konfiguration dokumentiert
|
||||
---
|
||||
|
||||
# Session Log — 2026-03-06: Immich & Pangolin Konfiguration
|
||||
|
||||
## 📋 Kontext
|
||||
|
||||
Ergänzungssession zur Proxmox-Korrektursession vom selben Tag.
|
||||
10 neue Screenshots wurden geliefert, die die vollständige Konfiguration von
|
||||
CT 100 (pangolin-client) und CT 103 (immich) sowie die detaillierten Hardware-Specs
|
||||
von VM 102 (gitea-runner) dokumentieren.
|
||||
|
||||
---
|
||||
|
||||
## 🛠️ Änderungen
|
||||
|
||||
### `SSoT_Konfigurations-Masterplan_Zora.md`
|
||||
|
||||
**Neue Daten aus Screenshots (06.03.2026, 13:25–13:27):**
|
||||
|
||||
#### CT 100 — pangolin-client (LXC)
|
||||
- IP ergänzt: `10.0.0.21/24`
|
||||
- Ressourcen dokumentiert: 4 Cores, 512 MiB RAM, 512 MiB Swap, 8 GB Disk
|
||||
- OS: Ubuntu arm64, Unprivileged, nesting=1
|
||||
- Autostart: order=1, up=30
|
||||
|
||||
#### CT 101 — gitea (LXC)
|
||||
- Ressourcen ergänzt: 4 Cores, 1 GiB RAM, 512 MiB Swap, 20 GB Disk
|
||||
- OS: Ubuntu arm64, Unprivileged, nesting=1
|
||||
- Autostart: order=2, up=30
|
||||
|
||||
#### CT 103 — immich (LXC) ← NEU vollständig dokumentiert
|
||||
- IP: `10.0.0.24/24`
|
||||
- Ressourcen: 8 Cores, 10 GiB RAM, 512 MiB Swap
|
||||
- Root Disk: 200 GB (`local:103/vm-103-disk-0.raw`)
|
||||
- Mount Point mp0: `/mnt/immich_gross` → `/mnt/fotos` (externe Foto-Bibliothek)
|
||||
- OS: Ubuntu arm64, Unprivileged
|
||||
- Features: `nesting=1, keyctl=1, fuse=1` (Docker-in-LXC kompatibel)
|
||||
- Autostart: order=3, up=30
|
||||
|
||||
#### VM 102 — gitea-runner (QEMU/KVM) ← Hardware-Details ergänzt
|
||||
- IP: `10.0.0.23/24` (bestätigt)
|
||||
- BIOS: OVMF (UEFI), Machine: virt (ARM64)
|
||||
- CPU: 8 Cores, 1 Socket, host-type, numa=1
|
||||
- RAM: 16 GiB (balloon=0 — kein Dynamic Memory)
|
||||
- Disk: 50 GB SSD (aio=io_uring, iothread=1 — maximale I/O-Performance)
|
||||
- EFI Disk: 64 MB, efitype=4m
|
||||
- Netzwerk: virtio, vmbr0, Firewall aktiv
|
||||
- SCSI: VirtIO SCSI single
|
||||
|
||||
#### Pangolin Tunnel Routing erweitert
|
||||
- Route `photos.mo-code.at` → CT 103 Immich (`10.0.0.24:2283`) ergänzt (intern/VPN)
|
||||
- Pangolin-Kontext-Hinweis: CT 100 (10.0.0.21) ist der Tunnel-Client
|
||||
|
||||
---
|
||||
|
||||
## 📚 Gelernt
|
||||
|
||||
- **Immich Features:** `keyctl=1` und `fuse=1` sind für Docker-in-LXC und Immich-Thumbnail-Verarbeitung notwendig.
|
||||
- **io_uring:** Der Gitea-Runner nutzt modernes async I/O für maximale Build-Performance auf NVMe.
|
||||
- **Start-Reihenfolge:** Pangolin (order=1) → Gitea (order=2) → Immich (order=3) — sinnvolle Abhängigkeitskette.
|
||||
- **balloon=0 beim Runner:** Festes RAM verhindert Memory-Ballooning-Latenzen bei intensiven CI-Builds.
|
||||
|
||||
---
|
||||
|
||||
## 🔜 Nächste Schritte
|
||||
|
||||
1. Pangolin-Route `photos.mo-code.at` im Pangolin-Dashboard anlegen (sobald Immich-Setup abgeschlossen).
|
||||
2. Immich-Setup-Anleitung erstellen (optional, eigene Session).
|
||||
Reference in New Issue
Block a user