-- mode: markdown; mode: visual-line; --
Sysadmins Puppet Module Tests with Vagrant
- Reference installation notes -- assuming you have installed Oracle's VirtualBox
- installation notes on Mac OS using Homebrew and Cask
You can list the available vagrant box as follows:
$> vagrant status Current machine states: centos-7 not created (virtualbox) debian-7 not created (virtualbox) This environment represents multiple VMs. The VMs are all listed above with their current state. For more information about a specific VM, run `vagrant status NAME`.
As suggested, you can run a debian 7 machine for instance by issuing:
$> vagrant up debian-7
Then you can ssh into the machine afterwards:
$> vagrant ssh debian-7
When you run
vagrant up <os> to boot the VM, it is configured to be provisioned with the
This script is responsible for two main tasks:
- pre-install the puppet modules listed as dependencies in
- make the appropriate symbolic link in the puppet module directory (to
/vagrant) to ensure you can directly make changes and correct your own module transparently within the box.
So you can test the manifests of the
tests/ directory within the VM:
$> vagrant ssh <os> [...] (vagrant)$> sudo puppet apply -t /vagrant/tests/init.pp
From now on, you can test (with --noop) the other manifests.
vagrant halt (or
vagrant destroy) to stop (or kill) the VM once you've finished to play with it.
Vagrantfile at the root of this repository might evolve over the time with new boxes. To automatically get the last version available:
$> bundle update falkorlib $> git commit -s -m "Upgrade falkorlib to the latest version" Gemfile.lock
Vagrantfileto the last version by issuing:
$> rake templates:upgrade:vagrant