raft / docs
Release notes

Raft 0.6.0

  • Disposable by default. raft config set disposable true makes raft new create disposable boxes, which are deleted with their snapshots when they stop or expire. raft new --persistent keeps one box anyway, and --disposable still works the other way. The default also applies to new --from; a fork stays persistent unless you pass --disposable. raft config shows the setting.
  • Delete boxes left stopped. raft policy LOCATION --delete-stopped-after 48 makes a host delete boxes, with their snapshots, once they have been stopped for 48 hours. The host applies it every 15 seconds and on raft gc, even with no controller online, logs each deletion to its journal (journalctl -t raft) and never touches running boxes. A new or shorter policy never deletes a box sooner than its hours after the change, and resuming a box resets its clock. raft list shows each stopped box's deleteAt. --delete-stopped-after never turns it off.
  • Stop times for every stopped box. The host now records a stop time for boxes stopped outside raft stop, such as a poweroff inside the box, a native incus stop or a recovered backup, when it first sees them. raft prune can therefore select them later; before, it skipped them forever.
  • raft policy changes. --require and --delete-stopped-after can be set together or alone, and each changes only its own policy. --require none replaces --clear, which is gone. In raft config, each location's changed field is now requireChanged, beside the new deleteStoppedAfterHours, deleteStoppedAfterSince and deleteStoppedAfterChanged.

Install on Linux with Python 3.11.8+ using npm install -g @microck/raft@0.6.0, or install the attached Python wheel; existing installs can run raft self-update.

Redeploy each host with this release's deploy/deploy.py. The host expiry worker changed, and until a host is redeployed raft doctor reports it, while new --disposable (including a disposable default), fork --disposable, raft prune and raft policy --delete-stopped-after HOURS fail on it with redeploy guidance. Redeploying changes nothing else on the host and sets no retention policy.

ARM64 and AMD64 development images accompany this release. Verify SHA256SUMS before importing an image for your host architecture.

On this page