Downloaded 78 times
Uploaded byPuppet
Continuously Testing Infrastructure - Beyond Module Testing - PuppetConf 2014
The document discusses continuously testing infrastructure by testing images, containers, and infrastructure as a service using tools like Packer, Serverspec, and Expect. It advocates applying test-driven development principles to infrastructure provisioning and management. Specifically, it suggests writing tests against an infrastructure API to define policies and desired functionality before provisioning resources. The document also describes testing based on data from PuppetDB to automatically generate and run configuration checks.
More Related Content
Similar to Continuously Testing Infrastructure - Beyond Module Testing - PuppetConf 2014
Continuously Testing Infrastructure - Beyond Module Testing - PuppetConf 2014
- 1. Continuously Testing Infrastructure Puppet Conf,San Francisco, 2014 Gareth Rushgrove Beyond Module Testing
- 2.
- 3.
- 4.
- 5.
- 6.
- 7.
- 8. Testing individual modules GarethRushgrove
- 9.
- 10.
- 11.
- 12.
- 13. Testing images and containers GarethRushgrove
- 14. Test driving infrastructure asa service Gareth Rushgrove
- 15. Testing with PuppetDB GarethRushgrove
- 16.
- 17.
- 18. Packer builds images basedon a JSON template Gareth Rushgrove
- 19.
- 20. It has somePuppet integration too Gareth Rushgrove
- 21.
- 22. But how dowe know the image works? Gareth Rushgrove
- 23. Lets add sometests! Gareth Rushgrove
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30. Serverspec also supports port,file, ppa, selinux, user, group, lxc, iptables, cron and more Gareth Rushgrove
- 31. Only publish theimage if the tests pass Gareth Rushgrove
- 32. Run tests automatically witha continuous integration system Gareth Rushgrove
- 33.
- 34.
- 35.
- 36.
- 37. Same approach works withcontainers too Gareth Rushgrove
- 38.
- 39.
- 40.
- 41. Test driven development GarethRushgrove
- 42. First the developerwrites an automated test case that defines a desired improvement or new function Gareth Rushgrove
- 43. Then produces the minimumamount of code to pass that test Gareth Rushgrove
- 44. And finally refactorsthe new code Gareth Rushgrove
- 45. Gareth Rushgrove First thedeveloper writes an automated test case that defines a desired improvement or new function
- 46. Your infrastructure should! havean API Gareth Rushgrove
- 47. What if wewrite assertions against! that API? Gareth Rushgrove
- 48.
- 49.
- 50. Great for buildingDSLs Gareth Rushgrove
- 51. Don’t worry, youcould write the examples in any language Gareth Rushgrove
- 52. Policy driven development GarethRushgrove
- 53. I don’t wantto launch too many nodes, they’re expensive Gareth Rushgrove Policy
- 54.
- 55. I don’t wantany stopped nodes, they are costing me money Gareth Rushgrove Policy
- 56.
- 57. Large nodes arereally expensive, so limit their usage Gareth Rushgrove Policy
- 58.
- 59. We should bebacking up every node Gareth Rushgrove Policy
- 60.
- 61. I only wantnodes in London and ! San Francisco Gareth Rushgrove Policy
- 62.
- 63. All our nodesshould be named environment-name Gareth Rushgrove Policy
- 64.
- 65.
- 66.
- 67. Now we havethe tests, we can provision some infrastructure Gareth Rushgrove
- 68.
- 69.
- 70.
- 71.
- 72.
- 73.
- 74.
- 75.
- 76.
- 77.
- 78.
- 79.
- 80. PuppetDB can storea lot of data about your infrastructure Gareth Rushgrove
- 81. The most recentfacts from every node Gareth Rushgrove
- 82. The most recentcatalog for every node Gareth Rushgrove
- 83. A wide rangeof metrics Gareth Rushgrove
- 84.
- 85. I want torun the same operating system on all hosts Gareth Rushgrove Policy
- 86.
- 87. Security enforcing packages shouldbe installed everywhere Gareth Rushgrove Policy
- 88.
- 89. I want tolimit how many puppet resources I’m using Gareth Rushgrove Policy
- 90.
- 91. We should avoidheavy I/ O load on the database by maintaining a high catalog duplication rate Gareth Rushgrove Policy
- 92.
- 93.
- 94.
- 95. PuppetDB is agreat source of context for tests Gareth Rushgrove
- 96. Generate serverspec tests fromPuppetDB data Gareth Rushgrove
- 97. Automatically detect hosts, andgenerate commands Gareth Rushgrove
- 98.
- 99. Match puppet resourcesto serverspec resources Gareth Rushgrove
- 100.
- 101. For instance ona Puppet Enterprise master Gareth Rushgrove
- 102.
- 103. Run serverspec testson all puppet managed hosts Gareth Rushgrove
- 104.
- 105.
- 106.
- 107. Is this monitoring? GarethRushgrove
- 108. We’re still movingtowards infrastructure as code Gareth Rushgrove
- 109. Infrastructure as code ratherthan infrastructure from code Gareth Rushgrove
- 110. Taking about policyas code might help communicate intent Gareth Rushgrove
- 111. Questions? And thanks forlistening