| commit | c7dffdee2c3f592b37ac17d0accb1bdfbcc345e1 | [log] [tgz] |
|---|---|---|
| author | Geoffrey Corey <geoffcorey7@gmail.com> | Thu Nov 12 08:29:08 2015 -0800 |
| committer | Geoffrey Corey <geoffcorey7@gmail.com> | Thu Nov 12 08:29:08 2015 -0800 |
| tree | 6eb8253f4dfb3fbd0a2e77e778a923d8a64c73b4 | |
| parent | 09622affb0ce0749acbdcd332e46b8f7de37d9c6 [diff] | |
| parent | c381b11bd22fe3a80fb10300572099702b46b6c7 [diff] |
Merge pull request #1 from rubys/patch-1 Mostly editorial changes
Test Kitchen + Puppet
git clone https://github.com/stumped2/puppet-kitchen git clone https://github.com/apache/infrastructure-puppet
gem install bundler cd <path to infra puppet repo> 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 export ipr=<path to infra-puppet repo> for i in $(ls $ipr/3rdParty); do ln -s $ipr/3rdParty/$i ./; done for i in $(ls $ipr/modules); do ln -s $ipr/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