summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoberto Bertó <463349+robertoberto@users.noreply.github.com>2026-05-19 05:00:01 -0300
committerGitHub <noreply@github.com>2026-05-19 05:00:01 -0300
commit1bb0a01f845e7df4fb5ffc7dc8abf8d8c592fa06 (patch)
treee9bcccb36c639c6255bfe867974445152c5b09e8
parent5a64e952064b4e1c07019662114acbc3497498e5 (diff)
parent6786e67c809450926ef4f5a4c54afdb4c11e73a5 (diff)
downloadpyvyos-1bb0a01f845e7df4fb5ffc7dc8abf8d8c592fa06.tar.gz
pyvyos-1bb0a01f845e7df4fb5ffc7dc8abf8d8c592fa06.zip
Merge pull request #38 from vyos-contrib/docs/related-projectsHEADmain
docs: cross-reference packer-vyos as related project
-rw-r--r--README.md7
-rw-r--r--tests/pve/README.md11
2 files changed, 18 insertions, 0 deletions
diff --git a/README.md b/README.md
index 1f9ce19..8686caa 100644
--- a/README.md
+++ b/README.md
@@ -255,6 +255,13 @@ local Proxmox host and runs `tests/e2e` against the real HTTPS API.
It is not part of the default GitHub Actions workflow. See the
harness README for setup.
+## Related projects
+
+- [`vyos-contrib/packer-vyos`](https://github.com/vyos-contrib/packer-vyos)
+ — Packer builder that produces ready-to-deploy VyOS images for QEMU,
+ Proxmox, AWS, and other targets. Complementary to `pyvyos`: build the
+ image with `packer-vyos`, then drive it from Python with `pyvyos`.
+
## Contributing
Bug reports and pull requests are welcome. Please open an issue first to
diff --git a/tests/pve/README.md b/tests/pve/README.md
index b84ad05..f780475 100644
--- a/tests/pve/README.md
+++ b/tests/pve/README.md
@@ -75,6 +75,17 @@ tests/pve/ensure-template.sh # phase 2: cloud-init applies API key,
The script is a state machine on the VMID, so re-running it from any
point is safe.
+### Alternative: prebuilt images with packer-vyos
+
+If you would rather skip the interactive install entirely, you can
+build a ready-to-clone VyOS image with
+[`vyos-contrib/packer-vyos`](https://github.com/vyos-contrib/packer-vyos)
+and import it on the PVE host instead of running phase 1 here. The
+harness scripts still work — you just point `VYOS_TEMPLATE_VMID` at
+the imported image. This harness keeps the install path because it
+has no extra dependencies; `packer-vyos` is a more capable option if
+you want repeatable image builds.
+
## Per-run workflow
```bash