This is my experience as a black box test engineer venturing into Devops using Chef. I cover the following topics during the course of my presentation - Why Chef, Pre-requisites, Cooking on a vagrant VM and conclude with an introduction to Berkshelf.
1. QA to sous-Chef
Sajnikanth Suriyanarayanan
Presented at Devops Summit on 27th March 2014
& at DevopsSG on 2nd October 2013
2. About Me
● Coastal GeoScientist and Civil Engineer
● 10+ years in Software Quality Assurance
and Functional Testing
● HP Certified Professional in Quality Center
● Lead Quality Assurance at Vistaprint
● http://sajnikanth.com
3. ● I’m a beginner
● May not be the standard way
● introduction to vagrant
● introduction to chef provisioning
● introduction to berkshelf
Disclaimer & Take-Away
6. Problem
Current project is brand new. So:
● write test scripts
● merge pull requests
● deploy code (where to?)
● test changes
7. ● App lives locally
● Experiment with technologies (mysql or
mongoDB; apache or nginx;)
● Unstable environment
Problem ...
A server should be like a phoenix, regularly
rising from the ashes - Martin Fowler
8. Vagrant + bash
● Reproducible
● Portable
● Isolated; room for experimentation
● Use Bash to install apps 'automatically'
10. Vagrant + Chef
Apprehensions:
● Ruby
● Steep learning curve
○ hosted chef or chef solo
○ knife
○ opscode
○ cookbooks
○ recipe
○ omnibus
○ information overload!!
20. Demo - We try again
vagrant up
Cookbook bluepill not found
Cookbook rsyslog not found
Cookbook build-essential not found
Cookbook ohai not found
Cookbook runit not found
Cookbook yum not found
Cookbook yum-epel not found