Blue-green: a new container is created beside the old one, data is copied, the
IP is moved onto it, and the old container is kept stopped as rollback for at
least a week. Keeping the IP means only the VMID changes, and its consumers
(backup jobs, backup audit) already derive it from the registry.
Batch 1 (2026-09-02): emergency-bot 148->151, docker-test 145->152,
gitea 141->153, vaultwarden 140->154, monitoring 146->155, gyro 150->156,
grimmory 149->157.
Batch 2 (2026-09-03): adguard 144->158, mihomo 143->159, ovpn-mini 132->160.
All migratable LXC are now provisioner: tofu. hermes-ai (frozen) and pbs stay.
- tofu/services.tf + tofu/svc-*.tf: one resource per service, reproducing the
pct-config etalon. /dev/fuse -> features.fuse; /dev/net/tun ->
device_passthrough (first live use on mihomo and ovpn-mini); gitea bind mount
-> datastore volume (data finally reaches PBS); console { type = "shell" }
declared explicitly (provider tracks cmode there).
- services.yml: vmid + provisioner: tofu for every migrated service; features
strings and device notes updated to the tofu representation; also drops the
memoir-bot entry and adds homelab_reverse_proxy_image/_unit.
- pve-*.yml: configuration play target is `{{ pve_config_target | default(...) }}`
so it can run against <name>-new on a temp address (a bare --limit zeroes the
play instead of retargeting it). Container-creation plays are gated behind
`provisioner != 'tofu'` / `pve_provisioning_enabled` (meta: end_play), so a
stray run cannot pct start a stopped OLD VMID on a live IP. Override for
intentional legacy rollback: -e pve_<svc>_legacy_provisioning_enabled=true.
- ssh_config: drop memoir-bot; ovpn-mini gets ProxyJump none (a jump via ru-vps
would route through the very tunnel ovpn-mini terminates).
- gyro.yml / uptime-kuma.yml: same pve_config_target override.
- roles/uptime_kuma: only freeze homelab-monitoring when the unit actually
exists (a fresh blue-green container never had it).
- offsite-restic-yadisk.yml: the gitea restic profile now runs inside the LXC
(hosts: gitea), since the bind-mount host path is gone after the volume move;
lost+found excluded (unreadable in an unprivileged LXC, restic exit 3).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012uoq5AVK8mkBgg83Mq6o5V
Роли Ansible
| Роль | Назначение |
|---|---|
backup_audit |
Аудит бэкапов PBS и restic, метрики в node-exporter |
bash_config |
Единый bash-конфиг для shell-хостов |
compose_service |
(новая) Docker Compose стек под systemd oneshot-юнитом |
emergency_access |
Аварийный доступ |
emergency_bot |
Telegram-бот аварийного доступа |
gyro |
Сервис gyro в изолированном LXC |
lxc_docker_host |
(новая) Подготовка непривилегированного LXC под Docker |
monitoring_blackbox |
Внешние HTTP-пробы с ru-vps |
monitoring_exporter |
node-exporter / smartctl-exporter |
monitoring_server |
Prometheus + Alertmanager + Grafana |
openvpn_gateway |
OpenVPN сервер/клиент |
pve_lxc |
Создание LXC через Proxmox API |
uptime_kuma |
Uptime Kuma |
base, docker, ufw |
Пустые каталоги, оставшиеся от ранней структуры |
Новые роли
lxc_docker_host
Пакеты, проверка /dev/fuse, daemon.json со storage-driver: fuse-overlayfs, запуск docker, базовые правила UFW (SSH из LAN и OpenVPN,
node-exporter 9100 с 192.168.1.30, deny incoming), проверка эффективного
драйвера хранилища. Вынесено из восьми pve-*.yml — около 350 строк
копипасты. Подробности и пример: lxc_docker_host/README.md.
compose_service
compose.yml + .env (генерация секретов один раз, no_log, 0600) +
systemd-юнит Type=oneshot с docker compose up -d --remove-orphans,
daemon-reload через handler, валидация docker compose config --quiet,
рестарт только при изменениях, health-check по URL с retries/until.
Подробности и пример плейбука Gitea на новых ролях:
compose_service/README.md.
Статус: роли созданы и проверены синтаксически, но пока не подключены ни
к одному живому сервису. Перевод pve-*.yml на них — отдельный этап.
Источник данных
Факты о сервисах (vmid, узел, адрес, порты, домен, образы с digest, ресурсы,
бэкап, мониторинг, порядок автозапуска) собраны в реестре
ansible/inventory/group_vars/all/services.yml (homelab_services).
Его уже потребляет playbooks/reverse-proxy.yml.