A presentation for the Automation session at the 2014 Cyber Summit by Fletcher Nichol, an Engineer with Heavy Water Operations.

1. Test Kitchen
and
Infrastructure as Code
Cyber Summit 2014
Fletcher Nichol
September 25, 2014
@fnichol

2. http://hw-ops.com

3. Agenda
1. Infrastructure as Code
2. Test Kitchen

4. Preface
I am a software developer

5. What is
Infrastructure?

6. Infrastructure
Physical and virtual resources:
compute (servers, vms),
networking, storage, etc.

7. What is
Infrastructure
Automation?

8. Code

9. Software

10. What is
Infrastructure
As Code?

11. Infrastructure as Code
“Enable the reconstruction of the
business from nothing but a
source code repository, an
application data backup, and bare
metal resources”
- Adam Jacob, Web Operations

14. If we can model
infrastructure as code

15. If we can model
infrastructure as code
can we apply code
process and practices?

16. In other words…

17. Can we apply

18. Can we apply
Software Engineering
to infrastrcuture?

19. Yep.

20. What processes and
practices apply to software?

21. Testing

22. Test Kitchen
“Your infrastructure
deserves tests too”

24. Test Kitchen
An infrastructure
testing tool

25. Test Kitchen
Used in development

26. Test Kitchen
Used in CI/CD
pipeline

27. Test Kitchen
Describes your testing
setup on a single server

28. Test Kitchen
.kitchen.yml
Code

29. ---
driver:
name: vagrant
!
provisioner:
name: chef_solo
!
platforms:
- name: ubuntu-14.04
- name: centos-6.5
!
suites:
- name: client
run_list:
- recipe[postgresql::client]
- name: server
run_list:
- recipe[postgresql::server]
Code

30. ---
driver:
name: vagrant
!
provisioner:
name: chef_solo
!
platforms:
- name: ubuntu-14.04
- name: centos-6.5
!
suites:
- name: client
run_list:
- recipe[postgresql::client]
- name: server
run_list:
- recipe[postgresql::server]
Code

31. ---
driver:
name: vagrant
!
provisioner:
name: chef_solo
!
platforms:
- name: ubuntu-14.04
- name: centos-6.5
!
suites:
- name: client
run_list:
- recipe[postgresql::client]
- name: server
run_list:
- recipe[postgresql::server]
Code

32. ---
driver:
name: vagrant
!
provisioner:
name: chef_solo
!
platforms:
- name: ubuntu-14.04
- name: centos-6.5
!
suites:
- name: client
run_list:
- recipe[postgresql::client]
- name: server
run_list:
- recipe[postgresql::server]
Code

33. ---
driver:
name: vagrant
!
provisioner:
name: chef_solo
!
platforms:
- name: ubuntu-14.04
- name: centos-6.5
!
suites:
- name: client
run_list:
- recipe[postgresql::client]
- name: server
run_list:
- recipe[postgresql::server]
Code

34. Test Kitchen
Runs multiple testing
setups in isolation

35. Test Kitchen
Plugin system to support
automation tools, cloud providers,
& testing frameworks

36. Test Kitchen
Drivers
Amazon EC2, Rackspace, Digital Ocean,
OpenStack, LXC, Vagrant, CloudStack,
Joyent, VMware vSphere, Google Compute
Engine, Microsoft Azure, Docker, etc.

37. Test Kitchen
Provisioners
Chef (Solo, Client), Simple Shell,
Puppet (Apply), Salt, Ansible, etc.

38. Test Kitchen
Testing Frameworks
Simple bash, bats, MiniTest,
shUnit2, Aruba, Serverspec,
RSpec, shpec, Cucumber, etc.

39. Test Kitchen
Getting Started
http://kitchen.ci/docs/getting-started/

40. It’s All Software
“In short, software is eating the
world.”
- Marc Andreessen, 2011

41. Infrastructure Automation is
Real

42. Infrastructure Automation is
Real Hard™

43. Infrastructure Automation is
Real …but

44. Infrastructure Automation is
Real Possible™

45. Thanks!
Cyber Summit 2014
Fletcher Nichol
September 25, 2014
@fnichol

46. Photo Credits
https://flic.kr/p/fD2CXV
https://flic.kr/p/i3NECz
https://flic.kr/p/9urXjF