Test and behavior driven infrastructure provides a framework to cope with an ever changing environment. TDI allows operations the benefits as TDD (Test Driven Development) and BDD (Behavior Driven Development), minimizing risk, building confidence, and maintaining focus. I will look at problems commonly seen in traditional system administration. I will cover configuration management and go over a continuous integration workflow in TDI, including the methodology, components, and stages.

1. GETTING
STARTED w/
TDI

2. Hello!
I AM CARLOS MEZA
Sysadmin that wants to
do things better.
Carlos@digitalr00ts.com
@digitalr00ts

3. ROADMAP
My journey learning TDI
1. The Promise of TDI
2. Configuration
Management
3. Principles of Test
and Behavior Driven
Development
4. Continuous
Integration
5. Test Driven
Infrastructure
6. Continuous Delivery
7. Continuous
Deployment
8. Challenges

4. 1.
TEST DRIVEN
INFRASTRUCTURE
Why TDI?

5. WHY TDI
TDI applies agile development
to infrastructure.
○Minimizes Risk
○Builds Confidence
○Maintains Focus

6. WHY TDI
TDI applies agile development
to infrastructure.
○Verifiable Behavior - Consistency
○Increased Code Quality - Confidence
○Safe Refactoring - Speed
○Improved Design - Adaptability

7. SYSADMIN ANTI-PATTERNS
Issues with system
deployment and maintenance
○Lack of Process
○Manual Process
○Poor Code

8. 2.
Configuration
Management
Infrastructure As Code

9. CONFIGURATION MANAGEMENT
CM ensures that a system is in a
known, good, and trusted state
○Visibility
○Reliability
○Productivity
○Scalability

10. CHEF WORKFLOW

11. TOOL OPTIONS
○Puppet
○Chef
○Salt
○Ansible

12. CHEF RECIPE EXAMPLE
package 'explicit_action' do
action :remove
end
package 'with_attributes' do
version '1.0.0'
action :remove
end

13. CM SHORTCOMINGS
CM does not prevent bad
infrastructure code
○Incomplete Code
○Unclear Code
○Unintended Consequences

14. 3.
TEST / BEHAVIOR
DRIVEN
DEVELOPMENT
Principles and Methods

15. TEST
DRIVEN DEVELOPMENT
A framework to
manage evolving environments with
highly reliable and maintainable code.
○Maintains Scope
○Faster Feedback
○Reduces Risk and
Builds Trust

16. BEHAVIOR
DRIVEN DEVELOPMENT
Facilitates collaboration between
stakeholders and developers by describing
requirements as system behaviors.
○Business Values Prioritized
○Tests are Documentation
○Improves Communication

17. SERVERSPEC EXAMPLE
describe port(80) do
it { should be_listening }
end
describe command("lsb_release -d") do
it { should return_stdout /wheezy/ }
end

18. RED, GREEN, REFACTOR
http://www.agileapps.co.uk/methodology/continuous.html

19. 4.
CONTINUOUS
INTEGRATION
Automating Failure

20. CONTINUOUS INTEGRATION
A practice with short development cycles,
automated testing and
code integration
○Detect Issues Sooner
○Faster to Implement

21. TESTING
Unit Test
Verifies that individual parts of your code
continue to work (Pre-Convergence)
Integration Test
Verifies the end state of the system post
integration (Post-Convergence)

22. CI WORKFLOW
https://insights.sei.cmu.edu/devops/2015/01/continuous-integration-in-devops-1.html
1

23. CI WORKFLOW
https://insights.sei.cmu.edu/devops/2015/01/continuous-integration-in-devops-1.html
2

24. CI WORKFLOW
https://insights.sei.cmu.edu/devops/2015/01/continuous-integration-in-devops-1.html
3
5
4

25. CI WORKFLOW
https://insights.sei.cmu.edu/devops/2015/01/continuous-integration-in-devops-1.html
6

26. TOOL OPTIONS
○Jenkins
○Travis CI
○Go (ThoughtWorks)

27. CODE REVIEW
http://explosm.net/comics/2083/

28. CODE REVIEW
Peer review of source code
○Readability
○Maintainability
○Knowledge Sharing

29. TOOL ASSISTED OPTIONS
○Garret
○Review Board
○Phabricator

30. 5.
TEST DRIVEN
INFRASTRUCTURE
Agile Infrastructure

31. PRINCIPLES AND PRACTICES
○Document - Requirements
○Test - Describe behavior
○Script - Code to pass test
○Audit - Version control
○Continuous - Automatically test and
integrate changes

32. TDI WORKFLOW
FORK

33. TDI WORKFLOW
CODE

34. TDI WORKFLOW
COMMIT

35. TDI WORKFLOW
TEST TRIGGERED

36. TDI WORKFLOW
TEST JOB

37. TDI WORKFLOW
INTEGRATION TEST

38. TDI WORKFLOW
FEEDBACK

39. TDI WORKFLOW
PULL REQUEST

40. TDI WORKFLOW
TO CODE REVIEW

41. 6.
CONTINUOUS
DELIVERY
Delivering to staging
environments

42. CONTINUOUS DELIVERY
A practice of delivering every change to a
production-like environment.
○Increases Ability to Adapt
○Increases Reliability
○Lowers Risk
○Faster to Production

43. CD WORKFLOW
COMMIT PULL REQUEST

44. CD WORKFLOW
TEST TRIGGERED

45. CD WORKFLOW
TEST JOB

46. CD WORKFLOW
iNTEGRATION TEST

47. CD WORKFLOW
FEEDBACK

48. CD WORKFLOW
DELIVER

49. 7.
CONTINUOUS
DEPLOYMENT
Automating to Production

50. CONTINUOUS DEPLOYMENT
Automating acceptance testing to promote
code through pre-productions
environments to production.
○Quicker Return on Investment
○Faster Client Feedback

51. CD WORKFLOW
Dev Staging Prod

52. CD WORKFLOW
Dev Staging Prod

53. CD WORKFLOW
Dev Staging Prod

54. CD WORKFLOW
Dev Staging Prod
Manual
(Continuous Delivery)

55. TOOL OPTIONS
Jenkins Plugins:
○Workflow
○Pipelines
Chef
○Delivery Truck
○Go (ThoughtWorks)

56. 8.
CHALLENGES
This Will All Fail

57. CHALLENGES
Cultural shift
○Workflow Changes
○Time Investment
○Full Adoption

58. CHALLENGES
Poor Testing
○Lack of Understanding
○Overlooking Test Parameters
○Trivial Tests

59. 9.
CONCLUSION
Wrap It Up

60. Conclusion
○Improves Reliability
○Increases Speed
○Increases in Productivity
○Adaptability
○Reduces Cost

61. SOURCES AND
MORE INFORMATION
○5 Things About Configuration
Management Your Boss Needs To Know
https://www.scriptrock.com/blog/5-configuration-management-boss
○Overview of Test Driven Infrastructure
with Chef
https://www.chef.io/blog/2015/04/21/overview-of-test-driven-
infrastructure-with-chef/
○Agile DevOps: Test-driven infrastructure
http://www.ibm.com/developerworks/library/a-devops5/

62. SOURCES AND
MORE INFORMATION
○Guide to Agile Practices -
http://guide.agilealliance.org
○ThoughtWorks Insights on CD
https://www.thoughtworks.com/insights/continuous-delivery

63. THANKS!
Special thank you to
Ned Harris of Chef.io

64. FOLLOW
ME
@digitalr00ts
Carlos@digitalr00ts.com