Download as PDF, PPTX
Uploaded byPuppet
Building and Testing from Scratch a Puppet Environment with Docker - PuppetConf 2014
This document discusses using Docker containers to build and test Puppet code. It describes setting up a Docker container to mimic a production environment by specifying hostname, custom facts, and operating system. Tests can be run on this container to validate Puppet code works as expected before deploying changes. Future enhancements proposed include supporting more operating systems and Puppet versions, linking multiple test nodes, and using an existing Puppet master.
More Related Content
Similar to Building and Testing from Scratch a Puppet Environment with Docker - PuppetConf 2014
![Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day3-cfd-251120170304-ddef8112-thumbnail.jpg?width=640&height=640&fit=bounds)
Building and Testing from Scratch a Puppet Environment with Docker - PuppetConf 2014
- 1. Building and Testing Puppet with Docker Carla Souza
- 2. Carla Souza Softwareengineer for Reliant Puppet user since 2010 Container virtualization user since 2008
- 3. Our environment ~15knodes Redboxes Amazon EC2 Instances Virtual machines OpenVZ containers KVM
- 5.
- 6.
- 7. Check your syntax puppet parse validate puppet-lint yaml syntax checker erb syntax checker
- 8. Variable data typevalidation validate_absolute_path validate_array validate_augeas validate_bool validate_cmd validate_hash validate_ipv4_address validate_ipv6_address validate_re validate_slength validate_string
- 9. Smoke testing #tests/test.pp class { 'apt': } puppet apply --noop --modulepath=".." tests/test.pp
- 10.
- 11.
- 12.
- 13.
- 15. No errors onthe puppet run != Correctly configured
- 17. Mimic the production environment
- 18.
- 20. 1. Target node'shostname 2. Use custom facts* 3. Specify OS 4. Thats all * not required
- 21. Step 2: Facts Write your own custom facts # myserver-facts.txt domain=reliantsecurity.com ipaddress=172.17.42.1 ipaddress_docker0=172.17.42.1 ipaddress_lo=127.0.0.1 ipaddress_wlan0=172.16.3.218 is_virtual=false
- 22. Step 2: Facts Steal facts from an existing node
- 23. Step 2: Facts $ mystique fetch-facts myserver $ mystique fetch-facts --hostname myserver --user carla myserver.company # myserver-facts.txt domain=reliantsecurity.com ipaddress=172.17.42.1 ipaddress_docker0=172.17.42.1 ipaddress_lo=127.0.0.1 ipaddress_wlan0=172.16.3.218 is_virtual=false (...)
- 24. Step 3: SpecifyOS --os ubuntu14.04 --os debian-wheezy
- 25. # mystique run--os ubuntu14.04 --hostname myserver
- 26. # mystique run--facts /path/to/facts.txt --hostname myserver
- 27.
- 28. FROM tianon/debian:wheezy RUNapt-get -qq -y install puppet puppetmaster ONBUILD ADD puppet.tar.gz /etc/puppet/
- 29. $ ls . ./ ../ .git/ .gitignore files/ templates/ manifests/ modules/ auth.conf autosign.conf fileserver.conf namespaceauth.conf
- 30. FROM mystique/debian:latest ADDmyserver-facts.txt /etc/facter/facts.d/ RUN puppet apply --modulepath=/etc/puppet/modules master.pp CMD puppet agent --no-daemonize
- 31. # mystique run--facts /path/to/facts.txt --hostname myserver Report for myserver 12 resources created 2 warnings 0 errors
- 32. # mystique run--facts /path/to/facts.txt --hostname myserver --verbose
- 34. Why using theexisting tools?
- 35. What can Ido with all this?
- 36. Future steps ●Mimic existing resources from nodes ● Extend supported OS ● Specify puppet version ● Multiple node testing ○ Linking containers ● User an existing Puppet Master
- 37. Thank you! carlasouza@reliantsecurity.com https://github.com/carlasouza/mystique* Twitter: @carlaas * not yet available