Evolving to DevOps
Download as PPTX, PDF1 like444 views
The document discusses fundamentals of adopting a DevOps culture and practices. It emphasizes establishing a culture of collaboration, communication and shared responsibility between development and operations teams. It also stresses the importance of automating processes, embracing tools to save time but not as the primary focus, and continuously improving culture, processes and technologies over time. Mistakes to avoid include poor infrastructure setup, configuration issues, and security vulnerabilities. The document advocates starting small, measuring progress, and celebrating successes to evolve existing practices towards continuous integration, delivery and deployment.
Evolving to DevOps
- 1. Fundamentals DevOps Summit 2015 May 22, 2015 Mumbai Ashish Nanotkar Technical Lead – DevOps Clogeny Technologies Pvt. Ltd.
- 4. A culture to Enable DevOps • Do not blame • Take responsibility for the team • Get on call with all • Surround yourself with mentors • Ownership
- 5. Social skills for DevOps • Be a part of business social structure • Step out of comfort zone – don’t be a nerd • Communicate • Be responsible • Respect the differences • Human contribution is important than tools
- 6. A structure to enable DevOps • Identify barriers • Identify responsibilities • That’s someone else’s problem • Reduce tension • Dev and ops report to same person • Tear down the walls
- 7. Tooling to enable DevOps • Automation is the key • Little automation at a time • No tool is perfect fit • Embrace skills not tools • Use tools to save time • Use saved time for follow-up on tools • Setup telemetry
- 8. You are never done • Iterate over • Implement agility • Developing culture takes time • Personal, organizational and technical improvement • Celebrate milestones
- 9. Ops mistakes • Wrong infrastructure setup • Poorly designed test environments • Incorrect configuration management • Deploying the wrong way • Not handling incidents correctly
- 10. Ops mistakes • Neglecting monitoring and alerting • Failing to maintain backups • Ignoring high availability principles • Falling into common security traps
- 11. Starting with DevOps • Educate stakeholders • Build small applications • Use a static analysis tool • Make processes visible • Measure as much as you can
- 12. Starting with DevOps • Make value visible • Celebrate success • Invite the Ops team • Be agile • Release one feature at a time • Start with the most comfortable zone
- 13. Getting the Hype OUT! • CI – Continuous Integration • CD – Continuous Delivery • CD – Continuous Deployment
- 14. Continuous Integration • Testing strategy • Flexible infrastructure • Version control system • Automated builds • Feedback mechanism • Functional testing
- 15. Continuous Delivery • Build, test and deploy automatically • Consistent configuration management • Fix configuration drift • Develop on mainline • Larger features implemented incrementally • Remove incomplete features • Depends on strong CI implementation
- 16. Continuous Deployment • Continuous delivery to Production • Reduction in lead time • Earlier evaluations for A/B testing • Environment screening • Fast feedback loop • Manage and test rollbacks
- 17. DevOps: • A culture • A framework CI is for everyone Delivery is for most, and Deployment is for the rare few … and everyone does it their way.
- 18. Thank you Fundamentals DevOps Summit 2015 Ashish Nanotkar nanotkarashish@gmail.com Organized by: UNICOM Trainings & Seminars Pvt. Ltd. contact@unicomlearning.com