Barn blog
Articles, design notes, release notes, and preserved development history. Older entries retain the Piglet name because they describe pre-rename artifacts, not current behavior.
Farrow 0.8.0: clearer recovery and refreshed images
Recover host preparation, isolate failed nodes, preserve VM identities, and start the September Debian and Ubuntu images.
Farrow 0.7.0: simpler test labs and automatic recovery
A shorter first run, compact progress, independent guest setup, and recovery through up.
Farrow 0.6.0: Ubuntu 24.04 and smoother local labs
Ubuntu 24.04 defaults, useful plans before setup, clearer status, and reliable expansion and recreation.
Farrow 0.5.0: explicit disposal, explicit repositories, reproducible images
A no-confirmation whole-lab purge, explicit global and China repository selection, no hidden artifact fallback, and an eight-target official-image candidate pipeline.
Farrow 0.3.0: explicit catalogs and actionable readiness
Explicit image-catalog updates, per-node bootstrap diagnostics, native guest interface names, and a smaller CLI.
Farrow 0.4.0: one command, working data disks, one voice
A first run that is one command, a default data disk that works on every image, readiness failures that name the cause, and one output style across the CLI.
Farrow 0.2.0: selected convergence and release integrity
VPN-aware network preflight, truly selected scale-out, committed-state integrations, checksum-verified multi-platform artifacts, and the 0.1.0 upgrade boundary.
repo.yaml Is Intent; catalog.json Is Evidence
Why Barn separates human-authored image policy from generated metadata that must match the actual qcow2 artifacts.
A PID Is Not a Virtual Machine
Why Barn combines QMP identity, process evidence, typed invocations, and journals before it signals or deletes anything.
Declarative Does Not Mean Destructive
How Barn uses per-node hashes and explicit operations so missing configuration can never authorize deletion.
Why Every Barn Node Has Two NICs
Why Barn separates management egress from the fixed-address network used by the host, peers, Ansible, and Pigsty.
Why Barn Has No Projects
Why Barn replaced per-directory project state with one owner-scoped deployment driven by one Pigsty Inventory.
-
Farrow 0.8.0: clearer recovery and refreshed images
Farrow 0.8.0 reduces manual work after interrupted setup and partial VM starts. It also refreshes the Debian and Ubuntu images while retaining every previous Catalog artifact and the identity of existing VMs. What changed Host preparation follows the …
Farrow 0.8.0 reduces manual work after interrupted setup and partial VM starts. It also refreshes the Debian and Ubuntu images while retaining every previous Catalog artifact and the identity of existing VMs. What changed Host preparation follows the …
-
Farrow 0.7.0: simpler test labs and automatic recovery
Farrow 0.7.0 makes local test labs easier to start and recover. Repeat farrow up to finish interrupted work, retry incomplete guest setup, and refresh older guest helpers without restarting running VMs. What changed A shorter first run. Interactive …
Farrow 0.7.0 makes local test labs easier to start and recover. Repeat farrow up to finish interrupted work, retry incomplete guest setup, and refresh older guest helpers without restarting running VMs. What changed A shorter first run. Interactive …
-
Farrow 0.6.0: Ubuntu 24.04 and smoother local labs
Farrow 0.6.0 defaults to Ubuntu 24.04 and improves the everyday loop of planning, starting, expanding, and rebuilding a local Pigsty lab. What changed Ubuntu 24.04 by default. New inventories and the embedded catalog use u24:stable. Catalog revision …
Farrow 0.6.0 defaults to Ubuntu 24.04 and improves the everyday loop of planning, starting, expanding, and rebuilding a local Pigsty lab. What changed Ubuntu 24.04 by default. New inventories and the embedded catalog use u24:stable. Catalog revision …
-
Farrow 0.5.0: explicit disposal, explicit repositories, reproducible images
Note This page describes 0.5.0. Official mirror failover was added in 0.7.0, and the unreleased 0.9 candidate removes the rm alias. Use current CLI guidance for your installed version. Farrow 0.5.0 was the public pre-1.0 release superseded by 0.6.0. …
Note This page describes 0.5.0. Official mirror failover was added in 0.7.0, and the unreleased 0.9 candidate removes the rm alias. Use current CLI guidance for your installed version. Farrow 0.5.0 was the public pre-1.0 release superseded by 0.6.0. …
-
Farrow 0.3.0: explicit catalogs and actionable readiness
Farrow 0.3.0 was the public pre-1.0 release superseded by 0.4.0. It removes implicit Catalog refreshes, turns guest bootstrap failures into actionable per-node results, and simplifies the CLI without changing the Pigsty Inventory or fixed-IP …
Farrow 0.3.0 was the public pre-1.0 release superseded by 0.4.0. It removes implicit Catalog refreshes, turns guest bootstrap failures into actionable per-node results, and simplifies the CLI without changing the Pigsty Inventory or fixed-IP …
-
Farrow 0.4.0: one command, working data disks, one voice
Farrow 0.4.0 was the public pre-1.0 release superseded by 0.5.0. It makes the first run one command, fixes the default data disk on Debian and Ubuntu images, and gives every command the same output style. The Pigsty Inventory format, the fixed-IP …
Farrow 0.4.0 was the public pre-1.0 release superseded by 0.5.0. It makes the first run one command, fixes the default data disk on Debian and Ubuntu images, and gives every command the same output style. The Pigsty Inventory format, the fixed-IP …
-
Farrow 0.2.0: selected convergence and release integrity
Farrow 0.2.0 was the public pre-1.0 release superseded by 0.3.0. It keeps the Pigsty inventory and on-disk deployment format introduced by 0.1.0 while fixing the network and selected-convergence boundaries found during the final native replay. What …
Farrow 0.2.0 was the public pre-1.0 release superseded by 0.3.0. It keeps the Pigsty inventory and on-disk deployment format introduced by 0.1.0 while fixing the network and selected-convergence boundaries found during the final native replay. What …
-
repo.yaml Is Intent; catalog.json Is Evidence
Note Renamed 2026-09-29: names now follow the unreleased Barn 0.9.0 candidate. The prior source review was on 2026-09-26: the original publication date is retained; the text below reflects the implementation reviewed on this date. See Status for …
Note Renamed 2026-09-29: names now follow the unreleased Barn 0.9.0 candidate. The prior source review was on 2026-09-26: the original publication date is retained; the text below reflects the implementation reviewed on this date. See Status for …
-
A PID Is Not a Virtual Machine
Note Renamed 2026-09-29: names now follow the unreleased Barn 0.9.0 candidate. The prior source review was on 2026-09-26: the original publication date is retained; the text below reflects the implementation reviewed on this date. See Status for …
Note Renamed 2026-09-29: names now follow the unreleased Barn 0.9.0 candidate. The prior source review was on 2026-09-26: the original publication date is retained; the text below reflects the implementation reviewed on this date. See Status for …
-
Declarative Does Not Mean Destructive
Note Renamed 2026-09-29: names now follow the unreleased Barn 0.9.0 candidate. The prior source review was on 2026-09-26: the original publication date is retained; the text below reflects the implementation reviewed on this date. See Status for …
Note Renamed 2026-09-29: names now follow the unreleased Barn 0.9.0 candidate. The prior source review was on 2026-09-26: the original publication date is retained; the text below reflects the implementation reviewed on this date. See Status for …
-
Why Every Barn Node Has Two NICs
Note Renamed 2026-09-29: names now follow the unreleased Barn 0.9.0 candidate. The prior source review was on 2026-09-26: the original publication date is retained; the text below reflects the implementation reviewed on this date. See Status for …
Note Renamed 2026-09-29: names now follow the unreleased Barn 0.9.0 candidate. The prior source review was on 2026-09-26: the original publication date is retained; the text below reflects the implementation reviewed on this date. See Status for …
-
Why Barn Has No Projects
Note Renamed 2026-09-29: names now follow the unreleased Barn 0.9.0 candidate. The prior source review was on 2026-09-26: the original publication date is retained; the text below reflects the implementation reviewed on this date. See Status for …
Note Renamed 2026-09-29: names now follow the unreleased Barn 0.9.0 candidate. The prior source review was on 2026-09-26: the original publication date is retained; the text below reflects the implementation reviewed on this date. See Status for …