Bilbostack19 devops is not what you think
Download as PPTX, PDF0 likes146 views
The document outlines the concept of DevOps as a culture and mindset that enhances agile software development by promoting collaboration and optimizing the entire value stream. Key elements include practices like continuous delivery, infrastructure automation, and designing for failure. It emphasizes the importance of feedback loops and learning in a tech-driven environment.
Bilbostack19 devops is not what you think
- 1. Devops is not what you think BilboStack 2019
- 2. 2
- 3. @eferro Eduardo Ferro Aldama https://www.eferro.net Sysadmin, Developer, Product, Tech lead, Agile, XP/Devops advocate
- 4. Agenda o Definition o Culture / Mindset o Practices / Tools o Introducing DevOps o References o Conclusions 4
- 5. Definition
- 6. “Devops is... Cool name for sysadmins 6 A team that deploys other teams services A team that operates other teams services
- 7. “Devops is... learning to work in small batches 7 creating fast feedback loops enabling cross-functional collaboration though value streams developing a culture of experimentation” Jez Humble
- 8. DevOps includes and enhance the ideas of the Agile Software Development giving a more end to end vision of the value stream for a technology-based company. And, you know, Every Company Is A Tech Company. 8 @eferro
- 10. 10
- 11. 11 Biz/Prod Dev Ops AGILE SOFTWARE DELIVERY
- 12. 12 Devops (optimize whole value stream)
- 13. o Collaboration o Avoiding SILOs o Flow o Remove waste o Build Quality in o Create fast feedback loops o Maximize learning 13
- 15. o Developers on-call o Infrastructure Automation o Self Service Platform o Design for failure o Continuous Delivery o ... 15
- 16. o Pain Driven Development o Ops requirements in backlog o Production ready code o Instrumentation o Monitoring 16 Developers on call
- 17. “You build it, you run it. 17 Werner Vogels CTO Amazon
- 18. 18 Developers on call Practices & patterns Actionable Alarms Push metrics Pull metrics Centralized logging Observability Design for Failure Tools Kibana Prometheus Grafana Fluentd Logstash PagerDuty
- 19. 19 Infrastructure Automation o Infrastructure as code o Configuration Management
- 20. Tools Puppet Chef Ansible Terraform Consul Docker 20 Infrastructure Automation Practices & patterns Infrastructure testing Inmutable Infra Image bakering Containers Push conf management Pull conf management
- 21. o Each team o Deploy by themselves o Operate their services 21 Self Service Platform
- 22. 22 Self Service Platform Practices & patterns Deploy pipelines One command deploy Blue Green Deployments Rolling Deployments Platform Control Panel Alerts Monitoring Tools Kubernetes OpenShift CloudFoundry Heroku Docker OpenStack Jenkins
- 23. o Embrace failure o Design for failure o Learn from it 23 Design for Failure
- 24. o Optimize recovery (MTTR) o Observability o Monitoring o Automatic recover 24 Design for Failure
- 25. 25 Design for Failure Practices & patterns Circuit Breakers Retries Blameless IRs Chaos Engineering Game days Testing in production Smoke tests Tools Hystrix HA Proxy Chaos Monkey Envoy OpenTracing
- 26. Build, Test, Deploy your apps in a fast and automated manner. 26 Continuous Delivery
- 27. o Continuous Integration o Deployment Pipelines o Deploy during working hours o Automatic testing o Release vs Deploy 27 Continuous Delivery
- 28. 28 Continuous Delivery Practices & patterns XP practices BDD Deployment pipelines Rolling Deploys Feature Toggles Parallel Changes Tools Cypress Jenkins CircleCI GitLab launchdarkly
- 30. 30
- 31. 31
- 32. 32 Self Service Platform Product Team A Product Team B Platform Team Production Engineering DevOps Team SRE Team
- 33. o Deployment Frequency o Lead time for changes o Time to restore o Change Failure Rate 33 Metrics
- 34. o Deploy during working hours o Self Service deployments o Blameless IR o Dashboard and Metrics 34 Inflection points
- 35. References
- 36. 36
- 38. 38 Conclusions Devops is a mindset Devops includes/requires Agile Development Continuous Delivery Flow, Feedback, Continuous Learning
- 39. “ To make error is human. To propagate error to all server in automatic way is #devops.” – DevOps Borat. 39
Editor's Notes
- #9: http://www.eferro.net/2018/05/devops-concepts-and-learning-path.html https://www.forbes.com/sites/oreillymedia/2014/05/13/every-company-is-a-tech-company/#47fc2c1420a0
- #11: Value Streams Customer / Ideas -> Working Software in Production Customers: -External customers -Internal customers (Financial Depto, Delivery Teams, Value Stream: are Business Outcome Driven Value Streams samples SaaS Product Value Stream: From external customer feedback to new feature in a SaaS product. (New feature) Internal IT value Stream: From internal customer request to a new internal ERP feature. (New feature, integration) Platform Value Stream: From internal customer (delivery team) to a new capability in our infrastructure or platform. (Optimized pipeline, New platform feature).
- #12: Walls Specialization Queues / Waiting time Waiting Misunderstanding Batch Oriented Huge lead time Huge cost of coordination Even Worst Sec Architecture QA Compliance No walls Agile Software Delivery Optimize Only Software creation A good improvement for late 90s early 2000 Packaged software Internal software 1 deploy / month Not Enough for: Age of software SaaS
- #13: No barriers / No walls Functional Optimization vs Business Outcomes
- #14: Main characteristics of DevOps culture: Collaboration between development and operations (avoiding SILOs and conflicting goals). Organize around the value streams optimizing for the flow efficiency (not resource efficiency). Learning to work in small batches. Remove waste (Non-Value Adding Activities). Of course, we talk about value from the customer point of view. Build quality in. Create fast feedback loops. Maximize organizational learning (making safe to fail and learn). Iterative Incremental Continuous Automated Self-Service Collaborative Holistic
- #22: Requires Code pipelines No hands-off
- #23: The self service platform should be
- #33: Several teams one for each value stream One of the value streams have the other teams as clients and are in charge of the platform…. But they are also a cross-functional team including all the roles. They don’t deploy other teams artifacts. The platform should be self service Good option when our previous structure have a infrastructure/systems team 1- Blameless IRs 2- Feedback 3- Build self service tools 4- Each product team deploys 5- Each product team on-call for their services