commit | 4ff7265bfdb9885f69d52ddfc06d66149b7c6660 | [log] [tgz] |
---|---|---|
author | Geoffrey Corey <coreyg@apache.org> | Mon Oct 19 13:07:08 2015 -0700 |
committer | Geoffrey Corey <coreyg@apache.org> | Mon Oct 19 13:07:08 2015 -0700 |
tree | dddd209c1d7972209f9552e30e420eea1d568cd1 | |
parent | 44f2b786847f32699420daa51f57d2f50fd3389c [diff] |
make this folder exist
Test Kitchen + Puppet
git clone https://github.com/apache/infrastructure-puppet
gem install bundler bundle install
mkdir -p $puppet-kitchen-root/puppet/modules cd puppet/modules for i in $(ls <path to infra-pupet 3rdParty>); do ln -s <path to infra-puppet 3rdParty>/$i ./; done for i in $(ls <path to infra-puppet modules>); do ln -s <path to infra-puppet modules>/$i ./; done
Make sure to have some puppet modules in the puppet/modules/
directory. The current hiera setup assumes you have the following modules:
If using GitHub to obtain modules, make sure when you clone the module, it only has the module name on the resulting folder. Example:
git clone https://github.com/puppetlabs/puppetlabs-apt.git apt
Then edit puppet/data/node/default-ubuntu14.yaml
to start adding classes and setting class parameters.
When you're ready to test, just run:
kitchen converge default
This will bring up a vm, run puppet apply. From there, you can continue writing your puppet module (in puppet/modules/$module
) and testing by running the above command.
Most the the test-kitchen option work with puppet, however make sure to see the kitchen-puppet documentation (even though the explanations aren't nearly as detailed as it needs to be).
Most information has been taken from here