How to build a Continuous Deployment / Delivery Pipeline for Systems. Presented 2017-03-11 in Seattle, WA for Cascadia IT Conference.

1. Garrett Honeycutt
gh@learnpuppet.com
learnpuppet.com
@learnpuppet
Continuous Deployment
Pipeline for Systems
2017-03-11
Cascadia IT Conf
Seattle, WA

2. # whoami
7th year at CasitConf!
LearnPuppet.com
Automation consulting
specializing in Puppet

3. What is CD?
Continuous Delivery
Continuous Deployment

4. "Continuous Delivery doesn't
mean every change is
deployed to production ASAP.
It means every change is
proven to be
deployable at any time"
@ccaum

5. Why?

6. Fail fast
Quick feedback leads to
fixing the issue faster

7. Increasing Pain

8. Boring Deployments
Take the excitement out of
making changes

9. Putting out fires
Reactive or Proactive?

10. MTTR vs MTBF
Mean Time to Repair
Mean Time Between Failures

11. Agility
Response to business needs

12. Enablement
Enable your business

13. Debugging
Solve one problem at a time

14. Concepts

15. Pipeline
Series of steps that are tied
together through automation

16. Jenkins

17. Determinism
Repeatable results

18. Artifact
All things necessary to
configure a system.

19. Artifact
Immutable

20. Artifact
You need an artifact store

22. Artifact
Moves through the pipeline

23. Roles
Each system has exactly one

24. Profiles
Describe technical makeup
for roles
Site specific data

25. Control repo
mod 'ssh',
:git => 'https://github.com/ghoneycutt/
puppet-module-ssh.git',
:ref => 'v3.49.1'

26. Pipeline
Let's build a real pipeline.

27. Start small
Use manual triggers if
needed

28. Pipeline
Cost and Time rises each
step

29. Create an artifact

30. Static Analysis
Fast!

31. Save artifact
Upload to artifact store

32. Test config mgmt
Role based perspective

33. Functional testing
per role
Build a system and verify its
state

36. Functional testing
per role
Build a system and
verify its state

38. Functional testing
multi-node
Test the entire stack

39. Function testing of
systems
From point of view of
consumer

40. Tools galore
Lot's of choices here

41. Monitoring
Run monitoring against
environment

42. Performance Testing
Does your new feature
provide worse service?

43. Security Testing
Find vulnerabilities before
deployment

44. Compliance
Reporting that shows you are
in compliance

45. What to deploy?
Code and data to maintain
state

46. What to deploy?
Entire systems

47. Triggers
How does the pipeline start?

48. Module development
Individual modules

49. Module development
What to test?

50. Module development
How to test?

51. TravisCI

52. AppVeyor

53. Module testing
Matrix tests

55. Feedback in PR

56. Feedback in PR

57. Control repo
# upsteam repo
mod 'ssh',
:git => 'https://github.com/ghoneycutt/
puppet-module-ssh.git',
:ref => 'v3.49.1'
# private module
mod 'myapp',
:git => 'https://github.com/me/puppet-
module-myapp.git',
:ref => 'master'

58. Triggers
How does the pipeline start?

59. Where to put testing
scripts?
Keep tests close to code

60. Information Radiator
Let people know what's
happening

62. ChatOps
Tell people when something
breaks or is deployed

63. Culture
Breaking the build is OK

64. Failing in production
You are not done until you
write a test

65. Rely on the Pipeline
Never touching Prod

66. Start small
1. Add a different type of testing
2. Write tests
3. Repeat

67. Confidence

68. Garrett Honeycutt
gh@learnpuppet.com
learnpuppet.com
@learnpuppet
Continuous Deployment
Pipeline for Systems
2017-03-11
Cascadia IT Conf
Seattle, WA