22 Jul 2013
Chef Testing and Training
Ive been using chef now for about 6 months now on and off, self taught, professionally and personally, but was lucky enough to take a 3 day chef fundamentals training course from a local chef guru @tomduffield. It was a great level set for many concepts Ive seen in cookbooks but didnt see the patterns till now. Also I received a certificate of awesome that Ill be hanging up at my desk to remind me how awesome I am :)
One thing that always peaks my interest is testing. Infra has always been that one thing that you just hope will work when you get the config right, or the network settings right, but you never know until you actually make the change. Virtualization/Cloud with APIs, along with the emerging set of tools for chef automation and testing are changing the way we create, test and deploy applications.
Tom drew a nice layout of the current state of Chef testing tools and approaches. Here are my notes from the conversation:
3 types/stages of chef testing
Static code analysis
What it thinks its going to do before it happens
Actually build environments and do asserts on the infrastructure
- vagrant with human eyes looking at the output
- minitest chef_handler
- test_kitchen with vagrant for testing multiple OSs at the same time
My take aways, and possible future blog posts:
- Other cool things Ill be looking at is using chef-zero to play with instead of chef-solo to test my searches locally.
- Setup a Continuous Integration/Continuous Delivery environment with Jenkins
Other tips or tools on chef testing? Fork this post and contribute below!
Want to contribute to this article? Edit this post on Github!