What DevOps Isn't
4 likes136 views
The document discusses the misconceptions about DevOps and provides an insight into its philosophy as a combination of cultural practices, tools, and collaboration between teams. It emphasizes that tools alone won't resolve issues within DevOps and that shared accountability, automation, and a focus on quality are essential for successful implementations. The author shares insights on how Bold Penguin adopts DevOps principles, including infrastructure as code, security measures, and a focus on continuous integration and deployment.
![Jez Humble
Author of Continuous Delivery
“[DevOps] is a cross-disciplinary community of prac.ce
dedicated to the study of building, evolving and opera<ng
rapidly-changing resilient systems at scale.”](https://image.slidesharecdn.com/whatdevopsisnt-181102025742/85/What-DevOps-Isn-t-4-320.jpg)
What DevOps Isn't
- 2. About Me • SVP of Engineering @ Bold Penguin Former DevOps Leader @ Magellan Health Former CTO @ Olive (fka CrossChx) • Software engineer by background. DevOps by choice Find me on Slack
- 4. Jez Humble Author of Continuous Delivery “[DevOps] is a cross-disciplinary community of prac.ce dedicated to the study of building, evolving and opera<ng rapidly-changing resilient systems at scale.”
- 5. Gene Kim CTO @Tripwire,Author of Phoenix Project “DevOps is more like a philosophical movement, and not yet a precise collec<on of prac<ces… DevOps is more like a vibrant community of prac..oners…”
- 6. “… DevOps is the combina<on of cultural philosophies, prac.ces, and tools…” — DevOps and AWS, aws.amazon.com/devops “DevOps is the union of people, process, and products to enable con<nuous delivery of value to our end users… teams now work together with shared and efficient prac.ces and tools.” — Azure DevOps
- 8. Easy… right?
- 9. So… what isn’t DevOps?
- 10. Tools.
- 11. Tools will NOT fix your broken DevOps. https://www.slideshare.net/AmazonWebServices/dev345tools-wont-fix-your-broken-devops
- 12. Plan Build Verify Release MonitorOperate
- 13. Expectation
- 14. Reality
- 15. Just like owning a treadmill doesn’t mean you’re in shape… Owning a tool doesn’t mean you’re doing DevOps.
- 17. “A system administrator is a person who is responsible for the upkeep and reliable operation of computer systems.” Wikipedia
- 18. Shouldn’t that be everybody?
- 19. Werner Vogels CTO @ Amazon Web Services “The tradi<onal model is that you take your soHware to the wall that separates development and opera<ons, and throw it over and then forget about it. Not at Amazon. You build it, you run it.” https://queue.acm.org/detail.cfm?id=1142065
- 20. Efficacy of IT Ops will always be constrained by the decisions made upstream.
- 23. If Ops doesn’t have a seat at the table when products are being built…. …you are definitely not doing DevOps.
- 24. Just about CI/CD
- 25. Security Audit & Compliance HIPAA SOC 2 PCI DSS HITRUST FedRAMP Monitoring Network Host SecOps Disaster RecoveryInfrastructure Provisioning Patching Forensics Threat DetecAon SLAs Backups Strategy RTO/RPO AlerAng Issue DetecAon Performance SLOs SOX Capacity Planning Availability Change Management Maintenance SoLware Updates Telemetry
- 26. How do we perform any operations function more efficiently? (and preferably via code).
- 28. Move fast and break things! - Someone who doesn’t do your performance review.
- 29. Velocity is constrained by quality.
- 30. 78.2% Avg. Code Coverage https://testing.googleblog.com/2014/07/measuring-coverage-at-google.html 150MM Test Runs / Day
- 31. Testing on theToilet @ Google https://testing.googleblog.com/2007/01/introducing-testing-on-toilet.html
- 32. 1,500 Tests / Build 20K Test Runs / Day
- 34. You probably don’t work at Google or Netflix. … but you should get very serious about test automation.
- 35. Blaming the people when things go wrong
- 37. “…an authorized S3 team member executed a command which was intended to remove a small number of servers for one of the S3 subsystems… Unfortunately, one of the inputs to the command was entered incorrectly and a larger set of servers was removed than intended.” https://aws.amazon.com/message/41926/
- 38. “We are making several changes as a result of this operational event.” https://aws.amazon.com/message/41926/
- 40. 1. Modify the tool to remove capacity at a slower speed. 2. Improve recovery time of S3 subsystems.
- 41. When things go wrong and your first reaction is to blame the person. … you’re not doing DevOps.
- 42. A destination
- 43. The throughput of any goal oriented system is limited by at least one constraint.
- 44. As soon as you solve a constraint, you can expect another constraint to appear.
- 45. How does Bold Penguin DevOps?
- 46. We don’t treat infrastructure like a pet. Patching infrastructure has some unintended consequences.
- 47. 1. Can not roll back to a previously known-good state. 2. Vulnerable to configuration drift. 3. Difficult to audit changes. 4. Opens a known attack vector.
- 48. We are cloud native. All cattle, no pets.
- 49. We rely on our automation to provision and replace out-of-date infrastructure components.
- 50. We like immutable infrastructure.
- 51. microservice- f7e9277404 Alpha InternalTesting Docker Container ami-b356ad9efb Amazon Machine Image core-ecs-clustercore-ecs-clustercore-ecs-cluster Cloudformation Stacks Beta UAT microservice- f7e9277404 Docker Container ami-b356ad9efb Amazon Machine Image core-ecs-clustercore-ecs-clustercore-ecs-cluster Cloudformation Stacks Prod Show time! microservice- f7e9277404 Docker Container ami-b356ad9efb Amazon Machine Image core-ecs-clustercore-ecs-clustercore-ecs-cluster Cloudformation Stacks
- 52. We do infrastructure as code.
- 53. Any infrastructure changes are written in executable templates. They are stored in version control, deployed, tested, and promoted just like application code.
- 54. microservice- f7e9277404 Deployment Pipeline Alpha InternalTesting Docker Container ami-b356ad9efb Amazon Machine Image Beta UAT microservice- f7e9277404 Docker Container ami-b356ad9efb Amazon Machine Image core-ecs-clustercore-ecs-clustercore-ecs-cluster Cloudformation Stacks Prod Show time! microservice- f7e9277404 Docker Container ami-b356ad9efb Amazon Machine Image core-ecs-clustercore-ecs-clustercore-ecs-cluster Cloudformation Stacks core-ecs-clustercore-ecs-clustercore-ecs-cluster Cloudformation Stacks core-ecs-clustercore-ecs-clustercore-ecs-cluster Cloudformation Stacks core-ecs-clustercore-ecs-clustercore-ecs-cluster Cloudformation Stacks
- 55. We like to use ChatOps.
- 57. Showing open pull requests
- 58. Alerting of possible security issues.
- 59. We are very serious about security. https://www.boldpenguin.com/security
- 60. Encryption by default Role-based access controls Principal of least privilege Organizations & IAM Roles Multi-factor authentication
- 61. We do CI/CD, too.
- 63. Continuous deployment with CodePipeline
- 64. We have shared ownership & shared accountability.
- 65. Any developer can make a PR.
- 66. We measure are obsessed with downtime, availability, and performance.
- 68. Graphs!
- 70. Thank you! p.s. come work at Bold Penguin!