Add Vagrantfile for easy testing and provisioning

[lenada]

I added a vagrant configuration & ansible provisioning. Can be tested with $ vagrant up

• [x] bootstrap box for ansible
• [x] install dependencies with ansible
• [x] add instructions for vagrant and provisioning to README

Please provide some feedback wether some of the following things would make sense

Provision / run integration tests

• [x] copy config file
• [x] run jetpack init / jetpack integration

[mpasternacki]

Thanks for the contribution! Vagrantfile will certainly make it easier to try Jetpack out and to run tests. A couple remarks:

Please rename the provision/ directory to contrib/vagrant/. I expect there will be more helper scripts in the future (at least a port Makefile to build a package, at least until Jetpack makes it into /usr/ports), and I'd like to avoid too many directories in the repository root. If the Ansible configuration is intended to be a general one rather than tied to the Vagrantfile, contrib/ansible/ may be a better name.

• I'm not sure hardcoding IP in config.vm.private_network is a good approach for a Vagrantfile in a public repository. Does anything break if you delete that line and go with the defaults (or whatever user set as default in ~/.vagrant.d/Vagrantfile?
• I'm not convinced that Ansible is needed (especially that installing Ansible needs a shell provisioning script anyway - can it go inline rather than be a separate script? That would make it a bit more straightforward to read). The provisioning is quite simple, it should be possible to just use the file provisioner to copy files, and then a shell script to set it up. I could be convinced otherwise, though.
• Can Python symlink go to /usr/local/bin/python, to avoid polluting system directories, or is /usr/bin/python hardcoded into Ansible?
• Besides immediate ifconfig and kldload, the interface and modules should also go to /etc/rc.conf to work after restart (the settings are cloned_interfaces + ipv4_addrs_lo1, kld_list). Maybe it is possible to just set it in rc.conf, and then use some rc script to bring the interface up and load modules?
• Debootstrap is not required: as images/debootstrap/README.md says, one should run debootstrap to create a rootfs tarball on a Linux system (unless you intend to add support for a cross-platform debootstrap, which would be nice).

Shell nitpick: in provision/bootstrap_freebsd.sh you could use set -e at the beginning (fail whole script on non-zero exit code from command) rather than &&ing the whole thing.

[mpasternacki]

Just checked: if you add interface and modules to /etc/rc.conf, you can run service netif start lo1 and service kld start to configure it without a restart.

[lenada]

move to contrib

done

I'm not sure hardcoding IP in config.vm.private_network is a good approach

to get the NFS mount from the host os into the guest os working I found no other way then specifiying config.vm.private_network. 10.0.1.10 gets assigned to em1, em0 is assigned "dynamically"

I'm not convinced that Ansible is needed (especially that installing Ansible needs a shell provisioning script anyway

I managed to get rid of the shell provisioning to pre-bootstrap ansible. the Python symlink is now also obsolete.

The big advantage of ansible - it is very easy to provision tasks in an idempotent fashion. I have restructured and split up the tasks for better readability and later reuse for other environments then the vagrant box.

Besides immediate ifconfig and kldload

went from the one-off approach to proper rc.conf

Debootstrap is not required

removed

[mpasternacki]

Other than adding Ansible requirement to README, this is good to go.

[mpasternacki]

Thank you!