Files
infra/ansible/playbooks/pve-vaultwarden.yml
T
DmitryandClaude Sonnet 5 a3fe8031fe feat: migrate all managed LXC provisioning to OpenTofu (blue-green)
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
2026-09-03 07:05:46 +03:00

243 lines
8.7 KiB
YAML

---
- name: Guard Vaultwarden VMID before API updates
hosts: mini-pc
gather_facts: false
pre_tasks:
- name: Skip legacy Vaultwarden provisioning for runtime-only calls
ansible.builtin.meta: end_play
when: not (pve_provisioning_enabled | default(true) | bool)
tasks:
- name: Read existing VMID 140 configuration
ansible.builtin.command: pct config 140
register: vaultwarden_existing_vmid
changed_when: false
failed_when: false
- name: Refuse to modify a foreign VMID 140
ansible.builtin.assert:
that:
- vaultwarden_existing_vmid.rc != 0 or vaultwarden_existing_hostname == 'vaultwarden'
fail_msg: VMID 140 already exists and is not the Vaultwarden container.
vars:
vaultwarden_existing_hostname: >-
{{ vaultwarden_existing_vmid.stdout_lines
| select('match', '^hostname: ')
| map('regex_replace', '^hostname: ', '')
| first
| default('') }}
- name: Create Vaultwarden LXC on mini-pc
hosts: mini-pc
gather_facts: false
pre_tasks:
- name: Skip legacy Vaultwarden provisioning for runtime-only calls
ansible.builtin.meta: end_play
when: not (pve_provisioning_enabled | default(true) | bool)
vars:
vaultwarden_vmid: 140
vaultwarden_hostname: vaultwarden
vaultwarden_ip: 192.168.1.24/24
vaultwarden_gateway: 192.168.1.1
vaultwarden_bridge: vmbr0
vaultwarden_rootfs: local-lvm:16
vaultwarden_ostemplate: local:vztmpl/debian-13-standard_13.1-2_amd64.tar.zst
vaultwarden_pubkey_file: ~/.ssh/id_ed25519_homelab.pub
handlers:
- name: restart vaultwarden lxc
ansible.builtin.shell: "pct stop {{ vaultwarden_vmid }} || true; pct start {{ vaultwarden_vmid }}"
changed_when: true
tasks:
- name: Check if Vaultwarden LXC exists
ansible.builtin.command: "pct config {{ vaultwarden_vmid }}"
register: vaultwarden_pct_config
changed_when: false
failed_when: false
- name: Install Vaultwarden LXC SSH public key on PVE host
ansible.builtin.copy:
dest: /tmp/vaultwarden-lxc.pub
owner: root
group: root
mode: "0600"
content: "{{ lookup('file', vaultwarden_pubkey_file) }}\n"
when: vaultwarden_pct_config.rc != 0
- name: Create Vaultwarden LXC
ansible.builtin.command: >-
pct create {{ vaultwarden_vmid }} {{ vaultwarden_ostemplate }}
--hostname {{ vaultwarden_hostname }}
--rootfs {{ vaultwarden_rootfs }}
--cores 2
--memory 1024
--swap 512
--net0 name=eth0,bridge={{ vaultwarden_bridge }},gw={{ vaultwarden_gateway }},ip={{ vaultwarden_ip }},firewall=1
--nameserver 1.1.1.1
--unprivileged 1
--features nesting=1,keyctl=1
--onboot 1
--startup order=40
--cmode shell
--ssh-public-keys /tmp/vaultwarden-lxc.pub
when: vaultwarden_pct_config.rc != 0
- name: Start Vaultwarden LXC
ansible.builtin.command: "pct start {{ vaultwarden_vmid }}"
register: vaultwarden_pct_start
changed_when: vaultwarden_pct_start.rc == 0
failed_when: vaultwarden_pct_start.rc not in [0, 255]
- name: Allow FUSE device in Vaultwarden LXC config
ansible.builtin.lineinfile:
path: "/etc/pve/lxc/{{ vaultwarden_vmid }}.conf"
line: "lxc.cgroup2.devices.allow: c 10:229 rwm"
state: present
notify: restart vaultwarden lxc
- name: Bind mount FUSE device in Vaultwarden LXC config
ansible.builtin.lineinfile:
path: "/etc/pve/lxc/{{ vaultwarden_vmid }}.conf"
line: "lxc.mount.entry: /dev/fuse dev/fuse none bind,create=file"
state: present
notify: restart vaultwarden lxc
- name: Apply pending LXC config changes
ansible.builtin.meta: flush_handlers
- name: Wait for Vaultwarden SSH through ru-vps
ansible.builtin.wait_for_connection:
timeout: 120
delegate_to: vaultwarden
vars:
ansible_become: false
- name: Configure Docker and Vaultwarden inside LXC
# Таргет переопределяем ради blue-green переезда на OpenTofu: во время
# миграции этот play нужно прогнать против нового контейнера на временном
# адресе. Просто `--limit vaultwarden-new` для этого НЕ годится — лимит
# пересекается с паттерном play и даёт ноль хостов, а не перенацеливание
# (проверено 2026-09-02 через --list-hosts на всех плейбуках).
# Использовать вместе с --limit, чтобы play создания контейнера отсеялся:
# ansible-playbook playbooks/pve-vaultwarden.yml \
# -e pve_config_target=vaultwarden-new --limit vaultwarden-new
# По умолчанию поведение не меняется.
hosts: "{{ pve_config_target | default('vaultwarden') }}"
gather_facts: true
vars:
ansible_become: false
vaultwarden_data_dir: /opt/vaultwarden/data
vaultwarden_image: vaultwarden/server:1.37.1@sha256:e9efdf001bf0d68c21f2cbfb8e1d9b5961a7ca9c85e0a7e58bf51a13b997d744
vaultwarden_container_name: vaultwarden
vaultwarden_http_port: 80
tasks:
- name: Install Docker packages
ansible.builtin.apt:
name:
- docker.io
- fuse-overlayfs
- sqlite3
- ca-certificates
- curl
state: present
update_cache: true
- name: Ensure Docker config directory exists
ansible.builtin.file:
path: /etc/docker
state: directory
owner: root
group: root
mode: "0755"
- name: Configure Docker storage driver for unprivileged LXC
ansible.builtin.copy:
dest: /etc/docker/daemon.json
owner: root
group: root
mode: "0644"
content: |
{
"storage-driver": "fuse-overlayfs"
}
register: docker_daemon_config
- name: Ensure Docker service is enabled and running
ansible.builtin.systemd:
name: docker
state: "{{ 'restarted' if docker_daemon_config.changed else 'started' }}"
enabled: true
- name: Ensure Vaultwarden data directory exists
ansible.builtin.file:
path: "{{ vaultwarden_data_dir }}"
state: directory
owner: root
group: root
mode: "0750"
- name: Check if the configured Vaultwarden image is present
ansible.builtin.command: "docker image inspect {{ vaultwarden_image }}"
register: vaultwarden_image_inspect
changed_when: false
failed_when: false
- name: Pull the configured Vaultwarden image
ansible.builtin.command: "docker pull {{ vaultwarden_image }}"
when: vaultwarden_image_inspect.rc != 0
register: vaultwarden_image_pull
changed_when: true
- name: Install Vaultwarden systemd unit
ansible.builtin.copy:
dest: /etc/systemd/system/vaultwarden.service
owner: root
group: root
mode: "0644"
content: |
[Unit]
Description=Vaultwarden container
After=docker.service
Requires=docker.service
[Service]
Restart=always
RestartSec=10
ExecStartPre=-/usr/bin/docker rm -f {{ vaultwarden_container_name }}
ExecStart=/usr/bin/docker run --rm \
--name {{ vaultwarden_container_name }} \
--pull never \
-p {{ vaultwarden_http_port }}:80 \
-v {{ vaultwarden_data_dir }}:/data \
-e WEBSOCKET_ENABLED=true \
{{ vaultwarden_image }}
ExecStop=/usr/bin/docker stop {{ vaultwarden_container_name }}
[Install]
WantedBy=multi-user.target
register: vaultwarden_unit
- name: Reload systemd when Vaultwarden unit changes
ansible.builtin.systemd:
daemon_reload: true
when: vaultwarden_unit.changed
- name: Enable and start Vaultwarden
ansible.builtin.systemd:
name: vaultwarden
state: "{{ 'restarted' if vaultwarden_unit.changed or vaultwarden_image_pull.changed else 'started' }}"
enabled: true
- name: Wait for Vaultwarden HTTP endpoint
ansible.builtin.uri:
url: "http://127.0.0.1:{{ vaultwarden_http_port }}/"
status_code: 200
register: vaultwarden_health
retries: 24
delay: 5
until: vaultwarden_health.status == 200
- name: Verify Docker storage driver
ansible.builtin.command: docker info --format '{{ "{{" }}.Driver{{ "}}" }}'
register: vaultwarden_docker_driver
changed_when: false
failed_when: vaultwarden_docker_driver.stdout != 'fuse-overlayfs'