https://barn.pgsty.com/tags/farrow-0.7.0/ Recent content in Farrow 0.7.0 on Barn Hugo en-US Wed, 16 Sep 2026 00:00:00 +0800 https://barn.pgsty.com/blog/release/farrow-0.7.0/ Wed, 16 Sep 2026 00:00:00 +0800 https://barn.pgsty.com/blog/release/farrow-0.7.0/ <p>Farrow 0.7.0 makes local test labs easier to start and recover. Repeat <code>farrow up</code> to finish interrupted work, retry incomplete guest setup, and refresh older guest helpers without restarting running VMs.</p> <h2 id="what-changed">What changed </h2> <ul> <li><strong>A shorter first run.</strong> Interactive <code>up</code> can create the default inventory, prepare missing host tools, and restore an intact inactive Farrow network. Short checks stay quiet; long work shows progress and a compact final result.</li> <li><strong>Usable guests stay available.</strong> Data disks, shares, guest hostnames, node-to-node SSH, and private networking initialize independently. Optional failures report specific limitations while working management SSH remains available. Healthy stages are skipped on subsequent <code>up</code> calls.</li> <li><strong>Test disks recover automatically.</strong> Working filesystems are reused; unrecognized or confirmed damaged filesystems are reset and mounted again. The result explicitly reports discarded data. Probe errors, missing devices, busy mounts, and backend I/O errors do not trigger formatting.</li> <li><strong>Fewer manual fixes.</strong> Unwritable shares fall back to read-only and retry after permissions are corrected. Occupied automatic SSH ports are reassigned for stopped guests. Interrupted image transfers resume, and official repositories can fail over without bypassing digest verification.</li> <li><strong>Clearer output and state.</strong> Successful commands show a short summary; limitations are grouped, and JSON/YAML keep structured results. Guest warnings use a disposable cache outside the schema-2 VM documents and node artifact directories, so older releases can still read and manage the deployment.</li> </ul> <h2 id="upgrade-notes">Upgrade notes </h2> <p><strong>Data disks are disposable test storage. <code>up</code> may clear a damaged filesystem, including one marked <code>persistent</code>.</strong> Persistence retains a disk across VM destroy/recreate; it does not preserve corrupt filesystem contents during recovery. Keep valuable data outside these test disks. Root disks and host shared directories are not reset by this recovery.</p>