Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

DevOps checklist or how to understand where is your team in DevOps landscape

372 Aufrufe

Veröffentlicht am

DevOps is a hot topic during last several years. Some companies, teams and products have achieved quite impressive results in this area making cultural changes, transforming their processes and practices, introducing new roles, tools and techniques. At the same time there is no common approach for measuring achievements and understanding “how DevOps” the current team/company is. In this talk I will provide attendees with basic checklist to start with and some reliable tools/techniques to monitor progress of “DevOps transformation”.

Veröffentlicht in: Internet
  • Als Erste(r) kommentieren

DevOps checklist or how to understand where is your team in DevOps landscape

  1. 1. DevOps checklist or how to understand where is your team in DevOps landscape Mikalai Alimenkou @xpinjection http://xpinjection.com
  2. 2. Telegram channel https://t.me/xpinjection_channel
  3. 3. Disclaimer This talk is based on personal experience
  4. 4. Are you DevOps enough?
  5. 5. #1. Do you have “DevOps engineers”, who “resolves” all infrastructure relates issues?
  6. 6. #2. Does everybody know where he sits and how he looks like?
  7. 7. #3. Do you invite “DevOps engineer” to all process meetings? Do they actively participate?
  8. 8. #4. Do you have DevOps improvements/issues backlog? How many of them are fixed in a month?
  9. 9. #5. Do developers and infrastructure engineers practice pair programming?
  10. 10. #6. Do you have clearly described incident management process? Are developers involved?
  11. 11. #7. Can “DevOps engineer” describe system from architectural point of view?
  12. 12. #8. Do you have regular infrastructure tools workshops for developers?
  13. 13. #9. Do developers participate in infrastructure tools selection?
  14. 14. To make a progress you have to set a clear goal first
  15. 15. Visualize you goal with checklist
  16. 16. Transfer status and team roles
  17. 17. 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
  18. 18. CORE INFRASTRUCTURE: HARDWARE
  19. 19. CORE INFRASTRUCTURE: NETWORK
  20. 20. CORE INFRASTRUCTURE: VIRTUALIZATION
  21. 21. CORE INFRASTRUCTURE: VM LIFECYCLE
  22. 22. CORE INFRASTRUCTURE: CONTAINERS
  23. 23. CORE INFRASTRUCTURE: DATA STORAGE
  24. 24. CORE INFRASTRUCTURE: BACKUPS
  25. 25. CORE INFRASTRUCTURE: MONITORING
  26. 26. OMG! I just wanted to be DevOps…
  27. 27. DEV INFRASTRUCTURE: CI/CD (JENKINS)
  28. 28. DEV INFRASTRUCTURE: ARTIFACTS
  29. 29. DEV INFRASTRUCTURE: STATIC ANALYSIS
  30. 30. DEV INFRASTRUCTURE: PROXY/LB
  31. 31. DEV INFRASTRUCTURE: DATABASES
  32. 32. DEV INFRASTRUCTURE: VCS
  33. 33. DEV PROCESS: CI/CD JOBS
  34. 34. DEV PROCESS: COMMUNICATION
  35. 35. DEV PROCESS: DOCKER IMAGES
  36. 36. DEV PROCESS: DOCKER STACKS
  37. 37. CUSTOMER SUPPORT
  38. 38. Developers-driven approach to tooling
  39. 39. 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
  40. 40. Success is always in team work
  41. 41. What to read?
  42. 42. @xpinjection http://xpinjection.com mikalai.alimenkou@xpinjection.com

×