personal_infra/ansible/infra/nodito/33_proxmox_debian_cloud_template.yml
counterweight 0f03c503c8
nodito: de-Uptime-Kuma the ZFS and NUT playbooks, extract templates
These two are host-specific by design - nodito is a pet, not cattle - so they
stay playbooks rather than becoming roles. But they had rotted.

De-Kuma, following the pattern of the six service roles:

  Both plays opened with an assert on uptime_kuma_username/password, which were
  removed from the vault, so both failed before doing anything. Dropped that,
  the two embedded Python monitor-creation scripts, and their /tmp cleanup.
  Kept every check, threshold and systemd timer - those are the durable part.

  Reporting is now generic: `healthcheck_push_url` goes into the unit as
  Environment=HEALTHCHECK_PUSH_URL and the script reads ${HEALTHCHECK_PUSH_URL:-},
  treating empty as normal rather than an error. The exit code is the real
  answer; systemd keeps it. Both scripts now also report status=down on failure
  instead of only going silent. Live push URLs harvested into the vault so
  nothing observable changes for ZFS.

Three live bugs found while check-diffing:

  1. 32_zfs would have DE-REGISTERED the Proxmox storage. `pvesm remove` was
     gated on the storage existing and `pvesm add` on it NOT existing - mutually
     exclusive - so a real run removed the proxmox-tank-1 entry backing every VM
     and never put it back. It would also have dropped `mountpoint /var/lib/vz`,
     which the live entry has and `pvesm add` does not set. Registration is now
     add-only.

  2. zfs_disk_1 named ata-...WX11TN0Z, a disk no longer in the machine. The live
     mirror is WX120LHQ + WX11TN2P; a leg was replaced and the repo never caught
     up. Inert behind `when: zfs_pool_exists.rc != 0`, but wrong on any
     disaster-recovery run. This is the seventh instance of an identifier
     written down once whose hardware later moved.

  3. 34_nut has NEVER been applied to nodito - no /etc/nut file carries the
     "Managed by Ansible" marker; they were written by hand in January 2026. The
     vault held the literal CHANGE_ME_TO_SECURE_PASSWORD, so applying it would
     have overwritten a working upsd/upsmon auth pair with a placeholder and
     restarted NUT, leaving the hypervisor's UPS unable to trigger a clean
     shutdown on mains loss. The Kuma assert was the only thing stopping that,
     so removing it without a replacement would have armed the gun: there is now
     an explicit assert that refuses to run on the placeholder. The real
     password is in the vault and `Configure upsd users` check-diffs clean.

  Templates reconciled with the live files first, so applying 34_nut is close to
  a no-op: added `maxretry = 3` to ups.conf and OFFDURATION / RBWARNTIME /
  NOCOMMWARNTIME / FINALDELAY plus quoted POWERDOWNFLAG to upsmon.conf. The only
  substantive additions left are the NOTIFYMSG/NOTIFYFLAG syslog lines.

  /usr/local/bin/ups-heartbeat.sh on the box is an orphan - mode 0644, not
  executable, referenced by no unit and no cron entry - but its push token
  belongs to a monitor that still exists and answers, so that monitor has had no
  heartbeat since January. Harvested as healthcheck_push_urls.ups; applying this
  play is what will finally feed it.

Finish the host_vars migration:

  infra/nodito/nodito_vars.yml was byte-identical to host_vars/nodito/main.yml.
  Deleted it, moved nodito_secrets.yml to host_vars/nodito/vault.yml, and
  stripped the dead vars_files entries from all three playbooks.

Extract the 13 inline `content: |` blocks to infra/nodito/templates/, pulled via
a YAML load rather than retyped. 681+582 lines become 313+344 plus templates.
Ownership parity against HEAD checked mechanically: no owner/group/mode drift on
any surviving task.

Neither playbook has been applied. ZFS play 2 check-runs failed=0 with two
changes: the script rewrite (the deployed one is a hand-edited DEBUG VERSION
with `set -x`) and the Environment line.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-13 19:07:50 +02:00

185 lines
6.9 KiB
YAML

- name: Create Proxmox template from Debian cloud image (no VM clone)
hosts: hypervisor
become: true
vars_files:
- ../../infra_vars.yml
vars:
# Defaults (override via vars_files or --extra-vars as needed)
debian_cloud_image_url: "https://cloud.debian.org/images/cloud/trixie/20251006-2257/debian-13-genericcloud-amd64-20251006-2257.qcow2"
debian_cloud_image_filename: "debian-13-genericcloud-amd64-20251006-2257.qcow2"
debian_cloud_image_dest_dir: "/var/lib/vz/template/iso"
debian_cloud_image_dest_path: "{{ debian_cloud_image_dest_dir }}/{{ debian_cloud_image_filename }}"
proxmox_template_vmid: 9001
proxmox_template_name: "debian-13-cloud-init"
proxmox_template_memory_mb: 1024
proxmox_template_sockets: 1
proxmox_template_cores: 1
proxmox_template_bridge: "vmbr0"
proxmox_template_cpu_type: "host"
proxmox_template_disk_size_gb: 10
# Cloud-init defaults applied at template level (optional). You can override per-VM later.
proxmox_ciuser: "counterweight" # Default login user to create; distro default may already exist
proxmox_sshkey_path: "/home/{{ new_user }}/.ssh/authorized_keys" # Path to pubkey file for cloud-init injection
proxmox_ci_upgrade: true # If true, run package upgrade on first boot
# Auto-install qemu-guest-agent in clones via cloud-init snippet
qemu_agent_snippet_filename: "user-data-qemu-agent.yaml"
# Storage to import disk into; use existing storage like local-lvm or your ZFS pool name
proxmox_image_storage: "{{ zfs_pool_name }}"
tasks:
- name: Verify Proxmox VE is running
command: pveversion
register: pve_version_check
changed_when: false
failed_when: pve_version_check.rc != 0
- name: Ensure destination directory exists for cloud image
file:
path: "{{ debian_cloud_image_dest_dir }}"
state: directory
mode: '0755'
- name: Check if Debian cloud image already present
stat:
path: "{{ debian_cloud_image_dest_path }}"
register: debian_image_stat
- name: Download Debian cloud image (qcow2)
get_url:
url: "{{ debian_cloud_image_url }}"
dest: "{{ debian_cloud_image_dest_path }}"
mode: '0644'
force: false
when: not debian_image_stat.stat.exists
- name: Ensure local storage allows snippets content (used for cloud-init snippets)
command: >
pvesm set local --content images,iso,vztmpl,snippets
failed_when: false
- name: Ensure snippets directory exists on storage mountpoint
file:
path: "{{ zfs_pool_mountpoint }}/snippets"
state: directory
mode: '0755'
- name: Read SSH public key content
slurp:
src: "{{ proxmox_sshkey_path }}"
register: ssh_key_content
- name: Extract SSH keys from authorized_keys file
set_fact:
ssh_keys_list: "{{ ssh_key_content.content | b64decode | split('\n') | select('match', '^ssh-') | list }}"
- name: Write cloud-init vendor-data snippet to install qemu-guest-agent
copy:
dest: "{{ zfs_pool_mountpoint }}/snippets/{{ qemu_agent_snippet_filename }}"
mode: '0644'
content: |
#cloud-config
# Vendor-data snippet: Proxmox will automatically set hostname from VM name when using vendor-data
# User info (ciuser/sshkeys) is set separately via Terraform/Proxmox parameters
package_update: true
package_upgrade: true
packages:
- qemu-guest-agent
runcmd:
- systemctl enable qemu-guest-agent
- systemctl start qemu-guest-agent
- name: Check if VMID already exists
command: qm config {{ proxmox_template_vmid }}
register: vmid_config_check
failed_when: false
changed_when: false
- name: Determine if VM is already a template
set_fact:
vm_already_template: "{{ 'template: 1' in vmid_config_check.stdout }}"
when: vmid_config_check.rc == 0
- name: Create base VM for template (no disk yet)
command: >
qm create {{ proxmox_template_vmid }}
--name {{ proxmox_template_name }}
--numa 0 --ostype l26
--cpu cputype={{ proxmox_template_cpu_type }}
--cores {{ proxmox_template_cores }}
--sockets {{ proxmox_template_sockets }}
--memory {{ proxmox_template_memory_mb }}
--net0 virtio,bridge={{ proxmox_template_bridge }}
when:
- vmid_config_check.rc != 0
- name: Import Debian cloud image as disk to storage
command: >
qm importdisk {{ proxmox_template_vmid }}
{{ debian_cloud_image_dest_path }}
{{ proxmox_image_storage }}
register: importdisk_result
changed_when: '"Successfully imported disk" in importdisk_result.stdout'
when:
- vmid_config_check.rc != 0 or not vm_already_template
- name: Check if ide2 (cloudinit) drive exists
command: qm config {{ proxmox_template_vmid }}
register: vm_config_check
failed_when: false
changed_when: false
when:
- vmid_config_check.rc == 0
- name: Remove existing ide2 (cloudinit) drive if it exists for idempotency
command: >
qm set {{ proxmox_template_vmid }} --delete ide2
register: ide2_removed
when:
- vmid_config_check.rc == 0
- "'ide2:' in vm_config_check.stdout"
- name: Build consolidated qm set argument list (simplified)
set_fact:
qm_set_args: >-
{{
[
'--scsihw virtio-scsi-pci',
'--scsi0 ' ~ proxmox_image_storage ~ ':vm-' ~ proxmox_template_vmid ~ '-disk-0',
'--ide2 ' ~ proxmox_image_storage ~ ':cloudinit',
'--ipconfig0 ip=dhcp',
'--boot c',
'--bootdisk scsi0',
'--serial0 socket',
'--vga serial0',
'--agent enabled=1',
'--ciuser ' ~ proxmox_ciuser,
'--sshkey ' ~ proxmox_sshkey_path
]
+ (proxmox_ci_upgrade | bool
| ternary(['--ciupgrade 1'], []))
+ ['--cicustom vendor=local:snippets/' ~ qemu_agent_snippet_filename]
}}
when:
- vmid_config_check.rc != 0 or not vm_already_template | default(false) or ide2_removed.changed | default(false)
- name: Apply consolidated qm set
command: >
qm set {{ proxmox_template_vmid }} {{ qm_set_args | join(' ') }}
when:
- vmid_config_check.rc != 0 or not vm_already_template | default(false) or ide2_removed.changed | default(false)
- name: Resize primary disk to requested size
command: >
qm resize {{ proxmox_template_vmid }} scsi0 {{ proxmox_template_disk_size_gb }}G
when:
- vmid_config_check.rc != 0 or not vm_already_template
- name: Convert VM to template
command: qm template {{ proxmox_template_vmid }}
when:
- vmid_config_check.rc == 0 and not vm_already_template or vmid_config_check.rc != 0