Download as PDF, PPTX
Uploaded bygarrett honeycutt
Continuous Deployment Pipeline for Systems - Presented at Ohio LinuxFest 2017-09-30
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.
More Related Content
Similar to Continuous Deployment Pipeline for Systems - Presented at Ohio LinuxFest 2017-09-30
Continuous Deployment Pipeline for Systems - Presented at Ohio LinuxFest 2017-09-30
- 1. Garrett Honeycutt gh@learnpuppet.com learnpuppet.com @learnpuppet Continuous Deployment Pipelinefor Systems 2017-09-30 Ohio LinuxFest Columbus, OH
- 2. # whoami LearnPuppet.com Automation consultingand training specializing in Puppet
- 3. What is CD? ContinuousDelivery Continuous Deployment
- 4. "Continuous Delivery doesn't meanevery change is deployed to production ASAP. It means every change is proven to be deployable at any time" @ccaum
- 5.
- 6. Fail fast Quick feedbackleads to fixing the issue faster
- 7.
- 8. Boring Deployments Take theexcitement out of making changes
- 9. Putting out fires Reactiveor Proactive?
- 10. MTTR vs MTBF MeanTime to Repair Mean Time Between Failures
- 11.
- 12.
- 13. Debugging Solve one problemat a time
- 14. Only Bob canDeploy Allow anyone to deploy from a single place
- 15.
- 16. Pipeline Series of stepsthat are tied together through automation
- 17.
- 18.
- 19. Artifact All things necessaryto configure a system.
- 20.
- 21. Artifact You need anartifact store
- 23. Artifact Moves through thepipeline
- 24.
- 25. Roles Each system hasexactly one
- 26. Profiles Describe technical makeup forroles 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 areal pipeline.
- 29. Start small Use manualtriggers if needed
- 30. Pipeline Cost and Timerises each step
- 31.
- 32.
- 33. Save artifact Upload toartifact store
- 34. Test config mgmt Rolebased perspective
- 35. Functional testing per role Builda system and verify its state
- 38. Functional testing per role Builda system and verify its state
- 41. Functional testing multi-node Test theentire stack
- 42. Function testing of systems Frompoint of view of consumer
- 43. Tools galore Lot's ofchoices here
- 44.
- 45. Performance Testing Does yournew feature provide worse service?
- 46. Security Testing Find vulnerabilitiesbefore deployment
- 47. Compliance Reporting that showsyou are in compliance
- 49. What to deploy? Codeand data to maintain state
- 50. What to deploy? Entiresystems
- 51. Triggers How does thepipeline start?
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 59.
- 60.
- 61. Control repo # upsteamrepo 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 thepipeline start?
- 63. Where to puttesting scripts? Keep tests close to code
- 64. Information Radiator Let peopleknow what's happening
- 66. ChatOps Tell people whensomething breaks or is deployed
- 68.
- 69. Failing in production Youare not done until you write a test
- 70. Rely on thePipeline Never touching Prod
- 71. Start small 1. Adda different type of testing
- 72. Start small 1. Adda different type of testing 2. Write tests
- 73. Start small 1. Adda 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.
- 78. Garrett Honeycutt gh@learnpuppet.com learnpuppet.com @learnpuppet Continuous Deployment Pipelinefor Systems 2017-09-30 Ohio LinuxFest Columbus, OH