Files
spektr 8ed62ec978 Doku-Abgleich 2026-11-09: Staende, Widersprueche und CT-103-Referenzen
- GNAI-000: Stand 09.11., Belegter-Stand-Tabelle um Monitoring-Zeile und
  aktualisierte KI-Host/GPU/LLM-Serving/Deployment-Zeilen ergaenzt,
  Ansible-Projekt-Tabelle um LLM-Stack, Monitoring und CT-103 ergaenzt,
  Reverse-Proxy-/DNS-Zeilen um Ansible-Import bzw. mon-Record ergaenzt,
  Leitentscheidungen (Production via ai_environment_switch, Monitoring
  host-lokal) aufgenommen, bereits erledigte Entscheidungstore
  (Backupziel, 64k/128k, M2/M3) aus der Offenen-Liste genommen
- GNAI-001: Ausführungsstand 09.11.2026 (M2 abgenommen, M3 beschlossen
  05.11., M4 abgenommen 06.11. und nach Neustart 09.11. erneut verifiziert);
  M1-Hinweis: CT-100/CT-103 besitzen inzwischen Ansible-Sollzustand
- GNAI-008: Stand 09.11., Abgrenzung Planung vs. belegter Stand (Abschnitt 14),
  Changelog 0.19/0.20, Abschnitt 15 an M4-Realitaet angepasst, Frage 6 als
  umgesetzt markiert, Re-Verifikation nach Host-Neustart 09.11. inkl. Befund
  gnai-ai-backup Exit 21 nach Boot (fehlende Mount-Reihenfolge; offen:
  RequiresMountsFor in ai_backup), gnai-experimental UID 983 -> 985
- GNAI-009/010: Statuszeilen an Betreiberbeschluss 05.11. bzw. umgesetzte
  Sollkonfiguration angepasst, Changelog 0.11
- GNENC-000/001/002: state/system.json als entfallen markiert (GNMON-001 v2.0),
  Flask -> Blazor, Monitoring-Status aktualisiert
- GNMON-001 v2.1 und planning-Snapshot: Umsetzungsabweichungen nachgefuehrt
- GNAI-002/003: gpu_fan_control bzw. Konten gn-download/gn-dashboard/
  gn-monitor/gn-media ergaenzt (live per getent verifiziert 09.11.)
- GNAI-006 v3.0: Ansible-Sollzustand importiert/adoptiert, Verifikation 09.11.
- GNAI-013, proxmox-server/README.md: CT-103-Automation-Referenz
- AGENTS.md: CT-103 nicht mehr "root-only" (ghost-agent/ghost seit 22.09.2026,
  ansible-deploy seit 07.11.2026; live geprueft 09.11.2026)
- llm-server/README.md: Doku-Spiegel um monitoring/ ergaenzt

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
2026-11-09 05:40:57 +01:00

104 lines
6.4 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Ghostnet.AI project context
Before infrastructure work, read `.codex/LOCAL_MEMORY.md` if it exists. It contains dated local observations and access hints; verify live state before making system changes. Keep secrets and private key material out of that file.
For read-only access to the KI server, use the tested SSH profile `ghostnet-ai-agent`, which logs in as the unprivileged account `ghost-agent` on `10.0.0.90`. On this workstation, invoke it as `ssh -F ~/.ssh/config ghostnet-ai-agent` because the system-wide SSH client configuration currently has an ownership/permissions error. Do not assume sudo access or make server changes without an explicit user request.
The KI server at `10.0.0.90` is deliberately a fresh base system. The operator plans to install the LLM application stack in a later Ansible sprint. Do not install applications or change server configuration as part of documentation review or access checks unless the operator explicitly requests that work.
## Agent access convention: `ghost-agent`
`ghost-agent` is the standard unprivileged account for the AI agent on the
Proxmox LXCs and the KI server (operator-confirmed 2026-10-28: "on the KI
server and many other Proxmox LXCs"). It is a convention, not a per-host
exception.
- Login is key-based with a **passphrase-less** Ed25519 key kept in the
operator's `~/.ssh` (`id_ed25519_ghostnet_<host>_agent`); `~/.ssh/config`
carries the matching `ghostnet-<host>-agent` aliases, which also work with
`ssh -o BatchMode=yes`. Private keys never enter the repository.
- `ghost-agent` has **no sudo** (verified on CT 100, CT 101, CT 103 and
ghostnet-ki): treat every agent session as read-only unless the operator
explicitly authorizes a change.
- Known aliases (verify live state before use; the WireGuard LXC has no
`ghost-agent` alias and uses the legacy `admin` account via alias `lxc`):
| Alias | System | IP |
| --- | --- | --- |
| `ghostnet-ct100-agent` | CT 100, Pi-hole/Split-DNS `dns` | 10.0.0.14 |
| `ghostnet-ct101-agent` | CT 101, Samba file server | 10.0.0.9 |
| `ghostnet-ct102-agent` | CT 102, Keycloak | 10.0.0.4 |
| `ghostnet-ct103-agent` | CT 103, reverse proxy (NPM) | 10.0.0.10 |
| `ghostnet-ct104-agent` | CT 104, Keycloak | 10.0.0.16 |
| `ghostnet-ai-agent` | ghostnet-ki, LLM/AI server | 10.0.0.90 |
- Invoke ssh as `ssh -F ~/.ssh/config <alias>`: a bare `ssh` currently rejects
`/etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf` because of its
ownership/permissions; `-F` deliberately uses the local profile without
loading that broken system configuration.
- Dated per-host observations (host-key fingerprints, verified identities,
account details) live in `.codex/LOCAL_MEMORY.md`, not here.
## Account landscape and Ansible inventory paths
| Account | Role | Key (operator `~/.ssh`) | sudo |
| --- | --- | --- | --- |
| `ghost-agent` | AI agent, read-only | `id_ed25519_ghostnet_<host>_agent` (no passphrase) | no |
| `ghost` | human operator/admin | `id_ed25519_ghostnet_<host>_ghost` (passphrase-protected) | yes, password-gated |
| `ansible-deploy` | Ansible deployment; created by the project's access role during adoption | `id_ed25519_ghostnet_<host>_ansible_deploy` (no passphrase) | `NOPASSWD: ALL` (treat the key as root-equivalent) |
Each Ansible LXC project (`proxmox/lxc/<ct>/ansible/`) maps these accounts to
three inventories: `agent` (`ghost-agent`, read-only preflight), `bootstrap`
(`ghost`, `--ask-become-pass`), `production` (`ansible-deploy`, NOPASSWD).
Legacy exception: the WireGuard LXC uses `admin` — see
`.codex/LOCAL_MEMORY.md`. CT 103 was historically root-only and bootstrapped
via the Proxmox console, but has carried the standard accounts since
22.09.2026 (`ghost-agent`, `ghost`) and `ansible-deploy` since the Ansible
adoption on 07.11.2026 (GNAI-011, GNAI-006 v3.0) — verified live 09.11.2026.
## Operator-run steps
- The workstation has **no Proxmox host access** (no `pct`): PVE-side commands
(`pct exec`, `pct reboot`, `vzdump`, editing `/etc/pve/lxc/*.conf`) are run by
the operator as root@pve. The agent prepares exact commands and reviews the
pasted output.
- Interactive secret steps are operator-run: `passwd`, `smbpasswd -a`, playbook
runs with `--ask-become-pass`, and key passphrase prompts. The agent hands
over copy-paste commands; the operator executes them.
- Secrets never enter the repository, inventories, playbooks or logs: SMB
passwords, the Samba passdb, the `ghost` password, private SSH keys, Podman
secrets. Only public keys belong in the repo (`ansible/files/ssh/`).
## LXC / Proxmox conventions
- Reboot caveat (GNAI-016 section 7): in LXC, `/proc/sys/kernel/random/boot_id`
belongs to the PVE host and does **not** change on a guest reboot — never use
boot_id-based waiters; reboot via PVE and verify independently over SSH.
- Unprivileged LXCs: mask `sys-kernel-config.mount` (configfs is unavailable)
and expect `uid_map 0 100000 65536` — host UIDs outside 100000–165535
appear as 65534 (nobody) inside the guest, so guest root cannot write to
files owned by such UIDs without world-write bits. (The former empty
`lxc.seccomp.profile:` line was a Ganesha-era exception and was removed on
2026-10-30 when the NFS export moved to the PVE host; GNAI-019 decision 2.)
- In-place dist-upgrades: take a `vzdump` safety net first and use
`--force-confold` so productive configuration files survive.
## Repository conventions
- Documentation: `docs/platform/proxmox-server/lxc/<ct>/GNAI-*.md` (German;
decisions carry operator/date stamps, findings are lettered a), b), …).
Ansible project READMEs are English. The central index is
`docs/GNAI-000-DOC_Index.md`.
- Ansible projects are self-contained under `proxmox/lxc/<ct>/ansible/`
(`ansible.cfg`, `inventories/{agent,bootstrap,production}`, `playbooks/`,
`roles/`, `files/ssh/`), use the repository-wide control venv (`.venv`, built
from `shared/ansible/requirements-control.txt`) and the shared roles in
`shared/ansible/roles/`.
- Change discipline: productive changes only with explicit operator go; preview
with `--check --diff` first; convergence must be idempotent (a second run
reports `changed=0`); commit only when the operator asks.
- Communicate with the operator in German.
- Verify account/identity assumptions with the operator before declaring them
(CT 101 example: `dark2devil` turned out to be the same person as
`debugofen`; GNAI-019 decision 11 was revised accordingly).