https://barn.pgsty.com/tags/vagrant/ Recent content in Vagrant on Barn Hugo en-US Wed, 11 Nov 2026 00:00:00 +0800 https://barn.pgsty.com/blog/design/pigsty-barn-migration/ Tue, 10 Nov 2026 00:00:00 +0800 https://barn.pgsty.com/blog/design/pigsty-barn-migration/ <p>Pigsty can use one inventory for Barn and Ansible. The migration needs to preserve topology selection, image matrices, resource scaling, fixed addresses, and SSH workflows while replacing the old scripts&rsquo; implicit addressing, naming, and destruction behavior.</p> <p><strong>Status (2026-11-10):</strong> <code>vm_scale</code>, the 1-vCPU / 2-GiB defaults, <code>vm_hosts</code>, <code>barn hosts install -f</code>, and Pigsty&rsquo;s <code>bin/sandbox-dns</code> are implemented in the local working trees and have passed the offline checks below. They are unreleased. Pigsty&rsquo;s Makefile still uses Vagrant; the second half of this article describes the remaining work. Released Barn 1.1.0 actually defaults to 2 vCPU / 4 GiB when parsing an inventory and does not support these additions.</p> https://barn.pgsty.com/blog/design/vagrant-workflow-boundary/ Sun, 08 Nov 2026 10:00:00 +0800 https://barn.pgsty.com/blog/design/vagrant-workflow-boundary/ <p>Barn already creates multi-node Linux labs from Pigsty-compatible inventories, manages their lifecycle, and exposes SSH and structured output. The useful lessons from Vagrant concern what happens between creating a VM and repeating an experiment: run setup steps, move source and build artifacts, record the environment, and return to a known state.</p> <p>This is a design proposal based on the Barn source reviewed on <strong>2026-11-08</strong>. The priorities below are candidates for implementation, with no assigned release or delivery date. Current commands are documented in the <a href="https://barn.pgsty.com/docs/reference/cli/">CLI reference</a>.</p>