TAPPaaS

debianhost

Primary audience: TAPPaaS admin.

A Debian machine TAPPaaS manages — a physical server, a mini-PC, anything with its own Debian install that is not a Proxmox guest (ADR-026). TAPPaaS keeps its operating system patched on the same schedule, and under the same reboot rules, as a cluster node. It is the first kind: machine module: one module, as many instances as you have machines, each named after its machine.

What you get

Capability How
The machine in TAPPaaS's inventory one instance per machine, config/<hostname>.json, kind: machine, os: debian
OS patching apt full-upgrade on every update — nightly with the sweep, or module-manager module update <instance>
Reboots only when authorized a reboot the upgrade needs waits for --allow-disruption, or for rebootOk: true in the scheduled pass; until then it is reported as deferred
Health checks reachable, Debian, no reboot pending, disk below 90%, clock synchronised, SSH key-only (when sshKeyOnly)
Key-only SSH password and keyboard-interactive logins over SSH refused for every user, root by key only — as on the cluster nodes (#19, #756). On by default; the console keeps the root password

What is not included

Requirements