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.

1. Building and Testing
Puppet with Docker
Carla Souza

2. Carla Souza
Software engineer for Reliant
Puppet user since 2010
Container virtualization user since 2008

3. Our environment
~15k nodes
Redboxes
Amazon EC2 Instances
Virtual machines
OpenVZ containers
KVM

5. Code your infrastructure

6. Code QA

7. Check your syntax
puppet parse validate
puppet-lint
yaml syntax checker
erb syntax checker

8. Variable data type validation
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. rspec-puppet
https://github.com/puppetlabs/puppetlabs-apt/blob/master/spec/unit/puppet/type/apt_key_spec.rb#L75

11. beaker

12. beaker
https://github.com/puppetlabs/puppetlabs-apt/blob/master/spec/acceptance/nodesets/default.yml

13. Code Review

15. No errors on the puppet run
!=
Correctly configured

17. Mimic the production
environment

18. Image from http://wegeekgirls.files.wordpress.com/2014/04/mystique_x-men_days-of-future-past.png

20. 1. Target node's hostname
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: Specify OS
--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. Image from http://wegeekgirls.files.wordpress.com/2014/04/mystique_x-men_days-of-future-past.png

28. FROM tianon/debian:wheezy
RUN apt-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
ADD myserver-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 the existing
tools?

35. What can I do 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