The document discusses continuous deployment pipelines for systems configuration. It defines continuous delivery and deployment, and explains why pipelines are important to enable fast fixes, increase agility, and allow anyone to deploy changes. The document outlines concepts of pipelines, artifacts, and testing at different stages. It provides tips for configuration tools and developing modules, and discusses triggers, monitoring, and culture for continuous deployment.

1. Garrett Honeycutt
gh@learnpuppet.com
learnpuppet.com
@learnpuppet
Continuous Deployment
Pipeline for Systems
2017-09-30
Ohio LinuxFest
Columbus, OH

2. # whoami
LearnPuppet.com
Automation consulting and
training 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. Only Bob can Deploy
Allow anyone to deploy from
a single place

15. Concepts

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

17. Jenkins

18. Determinism
Repeatable results

19. Artifact
All things necessary to
configure a system.

20. Artifact
Immutable

21. Artifact
You need an artifact store

23. Artifact
Moves through the pipeline

24. Tips for your
configuration
management tooling

25. Roles
Each system has exactly one

26. Profiles
Describe technical makeup
for roles
Site specific data

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

28. Pipeline
Let's build a real pipeline.

29. Start small
Use manual triggers if
needed

30. Pipeline
Cost and Time rises each
step

31. Create an artifact

32. Static Analysis
Fast!

33. Save artifact
Upload to artifact store

34. Test config mgmt
Role based perspective

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

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

41. Functional testing
multi-node
Test the entire stack

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

43. Tools galore
Lot's of choices here

44. Monitoring
Run monitoring against
environment

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

46. Security Testing
Find vulnerabilities before
deployment

47. Compliance
Reporting that shows you are
in compliance

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

50. What to deploy?
Entire systems

51. Triggers
How does the pipeline start?

52. Module development
Individual modules

53. Module development
What to test?

54. Module development
How to test?

55. TravisCI

56. AppVeyor

57. Module testing
Matrix tests

59. Feedback in PR

60. Feedback in PR

61. 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'

62. Triggers
How does the pipeline start?

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

64. Information Radiator
Let people know what's
happening

66. ChatOps
Tell people when something
breaks or is deployed

68. Culture
Breaking the build is OK

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

70. Rely on the Pipeline
Never touching Prod

71. Start small
1. Add a different type of testing

72. Start small
1. Add a different type of testing
2. Write tests

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

74. Using a Pipeline
1. Forces you to automate

75. Using a Pipeline
1. Forces you to automate
2. Will decrease MTTR

76. Using a Pipeline
1. Forces you to automate
2. Will decrease MTTR
3. Increases responsiveness to
the needs of your organization.

77. Confidence

78. Garrett Honeycutt
gh@learnpuppet.com
learnpuppet.com
@learnpuppet
Continuous Deployment
Pipeline for Systems
2017-09-30
Ohio LinuxFest
Columbus, OH