| commit | 5062dc84ff5fa4444a4eba318b84e7c276f38e3f | [log] [tgz] |
|---|---|---|
| author | Geoffrey Corey <geoffcorey7@gmail.com> | Thu Nov 05 11:10:53 2015 -0800 |
| committer | Geoffrey Corey <geoffcorey7@gmail.com> | Thu Nov 05 11:10:53 2015 -0800 |
| tree | 7a7c83c8e78b6191a5b2750e61af0eb2d63b87a9 | |
| parent | ec62cc88f5036df5deb6c5dc7ad75e4f26cac8cc [diff] |
fix up bootstrapping
Test Kitchen + Puppet
git clone https://github.com/apache/infrastructure-puppet
gem install bundler bundle install
cd <path to infra puppet repo> ./bin/pull # this will pull in all the 3rd party modules at the specified versions we use in production
cd <path to puppet-kitchen repo> 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-ubuntu1464.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