Build images for Vagrant

[n-rodriguez]

Hi there! It would be nice to have auto-generated Vagrant images to test with Kitchen Vagrant.

Some formulas are almost impossible to test with Docker (at least nfs and syslog-ng) so we should use Vagrant to test them. I've read that Vagrant don't work on Travis but works on Cirrus.

I'm working on a full Vagrant Kitchen file for syslog-ng formula

cc @myii

[myii]

Thanks @n-rodriguez. Just linking in a related issue and PR for the time being:

• Implement semantic-release for this formula saltstack-formulas/openssh-formula#165
• feat(freebsd): add FreeBSD support saltstack-formulas/vault-formula#32

[daks]

Packer is the way to go! :)

[n-rodriguez]

https://github.com/netmanagers/salt-image-builder#requirements

[n-rodriguez]

I've read that Vagrant don't work on Travis but works on Cirrus.

Well... it doesn't work on Cirrus... Cirrus provides VMs but doesn't seem to support nested virtualization :/

[myii]

@n-rodriguez They're responsive to e-mail contact (support+ci@cirruslabs.org, support@cirruslabs.org); that's how we eventually got it running with our Docker-based images. The person I was in contact with responded on this long issue:

• Resolve Travis concurrent jobs or consider Azure pipelines saltstack-formulas/template-formula#118

Might even be worth continuing the discussion there with fkorotkov.

In the meantime, I'm leaning towards a local solution of .kitchen.yml => kitchen.vagrant.yml, via. the KITCHEN_YAML or KITCHEN_LOCAL_YAML environment variable:

• feat(semantic-release): implement for this formula saltstack-formulas/openssh-formula#166 (comment)

---

Note: I used both e-mail address because the website displays one but links to the other: support@cirruslabs.org => support+ci@cirruslabs.org.