Skip to content

phoenix

Field Value
ID phoenix
Class host
Role llm-tracing
Status active
Primary IP 192.168.6.124
Proxmox LXC 124 on prox
Inventory inventory/hosts/phoenix.yaml

Overview

Arize Phoenix for LLM trace interrogation, RAG debugging, and experiments. Replaces retired ollama LXC 115 allocation on prox.

Hardware (inventory)

Resource Value
vCPU 2
RAM 4 GB
Disk 40 GB rootfs

Read-only pct config 124 on 2026-10-24 reports a 60G rootfs, while inventory still records 40 GB. CPU and memory match. Reconcile the storage metadata before a rebuild; this audit did not resize the guest.

Convergence load controls

Phoenix is CPU-constrained, so both ansible-pull services run at low CPU and I/O weight with a hard limit of half a vCPU. Drift-only checks run hourly; 30-minute apply convergence remains unchanged. This keeps ansible-pull from starving the Phoenix workload. Golden-shell and operator-tool convergence are disabled because this is a dedicated service guest; normal SSH administration remains available.

Access

Method Target
Web UI https://phoenix.infra.realemail.app (Traefik + Authentik)
OTLP gRPC 192.168.6.124:4317 (Servers VLAN)
SSH (operator) ssh phoenix or ssh someone@192.168.6.124
SSH (patch C&C) root@192.168.6.124 via patch-controller from infra-services

Proxmox LXC notes

Unprivileged CT 124 needs host /dev/net/tun bound into the guest for Tailscale (features: nesting=1,keyctl=1 plus the TUN cgroup/mount lines in /etc/pve/lxc/124.conf). Without that, tailscaled fails and ansible-pull stops before later roles.

Phoenix does not mount Whrrr Scans NFS; that share is infra-services only.

In-guest restic to /mnt/infra-backups is also disabled: unprivileged CT 124 cannot mount that NFS export (Operation not permitted), and a host bind-mount remaps UIDs so the guest cannot write. Until a host-side backup path exists, treat Phoenix data as covered by Proxmox vzdump / manual archive. See backup-alert-triage.md.

Runbooks