DevOps checklist or how to understand where is your team in DevOps landscape
5 likes1,111 views
The document provides a checklist for assessing a team's maturity in the DevOps landscape, focusing on team roles, processes, and tools. It emphasizes the importance of collaboration, continuous education, and shared accountability among developers and DevOps engineers. The checklist covers aspects such as infrastructure management, development processes, and customer support to help teams visualize and achieve their goals.
DevOps checklist or how to understand where is your team in DevOps landscape
- 1. DevOps checklist or how to understand where is your team in DevOps landscape Mikalai Alimenkou @xpinjection http://xpinjection.com
- 4. Disclaimer This talk is based on personal experience
- 6. Are you DevOps enough?
- 8. #1. Do you have “DevOps engineers”, who “resolves” all infrastructure relates issues?
- 9. #2. Does everybody know where he sits and how he looks like?
- 10. #3. Do you invite “DevOps engineer” to all process meetings? Do they actively participate?
- 11. #4. Do you have DevOps improvements/issues backlog? How many of them are fixed in a month?
- 12. #5. Do developers and infrastructure engineers practice pair programming?
- 13. #6. Do you have clearly described incident management process? Are developers involved?
- 14. #7. Can “DevOps engineer” describe system from architectural point of view?
- 15. #8. Do you have regular infrastructure tools workshops for developers?
- 16. #9. Do developers participate in infrastructure tools selection?
- 17. To make a progress you have to set a clear goal first
- 18. Visualize you goal with checklist
- 19. Transfer status and team roles
- 20. Main checklist categories • CORE INFRASTRUCTURE Hardware, virtualization, network, containerization, datastores, backups, monitoring • DEVELOPMENT INFRASTRUCTURE CI/CD, artefacts, static code analysis, proxy, load balancer, databases, VCS • DEVELOPMENT PROCESS CI/CD jobs, Docker images, Docker stacks, communication • CUSTOMER SUPPORT
- 24. CORE INFRASTRUCTURE: VM LIFECYCLE
- 26. CORE INFRASTRUCTURE: DATA STORAGE
- 29. OMG! I just wanted to be DevOps…
- 30. DEV INFRASTRUCTURE: CI/CD (JENKINS)
- 32. DEV INFRASTRUCTURE: STATIC ANALYSIS
- 36. DEV PROCESS: CI/CD JOBS
- 38. DEV PROCESS: DOCKER IMAGES
- 39. DEV PROCESS: DOCKER STACKS
- 40. CUSTOMER SUPPORT
- 41. Developers-driven approach to tooling
- 43. Summary • Found and grow DevOps culture, not job titles • Work as a team at all stages of development cycle • Prepare and share tools for developers • Build continuous education and knowledge sharing • Share responsibilities and accountability for success • Prefer specialization for complex activities • Choose right tools together to automate routine
- 45. Success is always in team work
- 46. What to read?
Editor's Notes
- #42: У вас есть CI? Да, у нас стоит Jenkins где-то. Причем, неожиданно все начали использовать CI/CD повсеместно, хотя от CD у большинства нет ничего вообще. Постоянные holy wars по поводу инструментов: chef, puppet, ansible, terraform.