Download as PDF, PPTX
Uploaded byPete Cheslock
DevOpsDays - Pick any Three - Devops from scratch
This document contains the transcript of a presentation on DevOps. It discusses the traditional separation between development and operations teams and some of the problems it caused. It then talks about how DevOps aims to break down the walls between dev and ops so they work more collaboratively towards shared goals. It provides examples of practices like automating infrastructure provisioning and deployment, implementing monitoring of applications and infrastructure with metrics, and sharing ownership and accountability for the overall service. It also briefly touches on how security teams can be integrated into DevOps practices through a model like DevSecOps.
More Related Content
Similar to DevOpsDays - Pick any Three - Devops from scratch
DevOpsDays - Pick any Three - Devops from scratch
- 1. @petecheslock Pick Any 3: Good,Fast, or Safe DevOps from Scratch
- 2. @petecheslock Who Am I? PeteCheslock @petecheslock Technical Operations at Threat Stack
- 3.
- 4.
- 5. @petecheslock!5 Companies are Choosing SpeedOver Security 52% of Companies Admit to Sacrificing Security for Speed 64% of Sales professionals say they have had a deal slowed down by insufficient security
- 6. 6 Let Threat StackHelp You Build a Cloud SecOps Program
- 7. @petecheslock What Even isThe DevOps?
- 8.
- 9.
- 10.
- 11.
- 12.
- 13. @petecheslock DevOps is Anything YourHeart Desires
- 14.
- 15.
- 16. @petecheslock Let’s Talk Aboutthe Bad Old Days
- 17.
- 18.
- 19.
- 20. Crop image tofit inside this box The Bad Old Days Software
- 21. Crop image tofit inside this box The Bad Old Days Software Devs would rarely even have access to production systems… …which means Ops would have to take the code and install it based on Dev’s instructions
- 22. @petecheslock The Bad Old Days Infrastructure Leadtime for new servers would be measured in weeks (best) or months (worst) Code could be ready before servers were available. Long feedback loops in running code on actual hardware, wasted time and money.
- 23.
- 24. @petecheslock@petecheslock Dev’s job isto add new features Ops’s job is to keep the site stable and fast Traditional Thinking
- 25.
- 26.
- 27.
- 29. @petecheslock DevOps Operations job isNOT to keep the site stable and fast. Operations (and Dev’s) job is to enable the business.
- 30. @petecheslock Tools Culture& Lowering therisk of change through
- 31. @petecheslock 1 2 3 Thisis a Story in Three Acts ACT THREE Ownership and Accountability. ACT TWO Metrics are a first class citizen. ACT ONE Optimize for ease of software deployment.
- 32. @petecheslock Simplify the actof getting new software to Customers. Iterate and improve upon that process. Leverage tools like Canary Deployments and Dark Shipping Ship the code when its “Ready” Software Deployment
- 33. @petecheslock Simplify the actof getting new software to Customers. Iterate and improve upon that process. Leverage tools like Canary Deployments and Dark Shipping Ship the code when its “Ready” Software Deployment
- 34. @petecheslock COMPILE YOUR SOURCE BUILDA PACKAGE SIGN THE PACKAGE TEST THE PACKAGE DEPLOY THE PACKAGE Software Deployment
- 35. @petecheslock COMPILE YOUR SOURCE BUILDA PACKAGE SIGN THE PACKAGE TEST THE PACKAGE DEPLOY THE PACKAGE Software Deployment THIS IS KIND OF IMPORTANT
- 36. @petecheslock What even ISready? Ready means… Reviewed by other engineers Passed a series of unit, integration, and functional tests Reviewed to ensure that it meets other business or security requirements
- 37.
- 38.
- 39.
- 40. @petecheslock “If you wantmetrics for your apps - send your data here” Ops responsibility is to build the systems and make them easy to use Dev’s responsibility is to instrument their application to understand perf What About Metrics?
- 41. @petecheslock collectd -> write_graphite-> statsd_plugin app1 app2 app3 Graphite
- 42. @petecheslock Devs AND Opswork together to ensure we are using the right instance types for the workloads. Metrics
- 43. @petecheslock Devs AND Opswork together to ensure we are using the right instance types for the workloads. Metrics
- 44. @petecheslock How do weknow this is working?
- 45. @petecheslock We own theoverall health of the infrastructure. Ensure we are making the right choices for Scalability, Availability, and Cost. We build the tools that enable teams to deploy, manage, and update their applications. Ownership & Accountability Operations owns the infrastructure
- 46. @petecheslock They are on-calland get paged when their application runs into problems They manage the life of the service from idea to deployment and scaling. Ownership & Accountability Development owns their applications
- 47. @petecheslock Everyone cares aboutthe health of Threat Stack
- 48. @petecheslock How we doDevOps
- 49. @petecheslock Ops needs to trustdev to involve them on feature discussions How we do DevOps
- 50. @petecheslock Devs need to trustOps to discuss infrastructure changes. How we do DevOps Ops needs to trust dev to involve them on feature discussions
- 51. @petecheslock Everyone needs totrust that everyone is doing their best for the business
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59. Crop image tofit inside this box How to Integrate SecOps? Similar to integrating Dev and Ops teams. Adding Security into the mix - leverage your shared tools and processes. Threat Stack uses Threat Stack to protect Threat Stack.
- 61. @petecheslock "Abrasive individuals willsingle-handed do more to undermine the security brand and culture at your company than anything else.” https://speakerdeck.com/iodboi/crafting-an-effective-security-organisation-kiwicon-8 - Rich Smith (Etsy)
- 62. @petecheslock The best security cultureis collaborative not prescriptive.
- 63.
- 64.