Dev ops presentation


Published on

Presentation About Adopting DevOps Approach.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • “devs feels that ops throws away app problem at them”
  • Writing small code chunks instead of big releases.
  • Increasing frequency of deployments will improve the time to deploy new code.
  • Which leads to have the ability to build infrastructure at scales to dozens or even thousands of servers on multiple locations with different types of hardware even and softens things to level that’s just a click away to reverse back to a previous code build or to deploy a new release with bug/security fix or a new software feature.
  • Deliver products in hours and weeks instead of months as used to be before. and all are happy now, customers and DevOps.
    By automating infrastructure ops and devs have now more focus on improving business instead of wasting time on human deployments or devs dependency hell.
  • IBM Approach to DevOps
  • IBM Approach to DevOps
  • End of DevOps Sessions.
  • This is how they defined themselves on their own site.
  • Dev ops presentation

    1. 1. DevOps Introduction Ahmed Kamel Lead System Engineer @ArabHosters LinkedIn
    2. 2. The story ● Information Technology Companies are selling Products/Services to customers. ● Products/Services are written by developers. ● Products/Services are deployed operations.
    3. 3. What is Dev? ● Developer o Responsible for coding: ▪ New Products. ▪ New Features. ▪ Security Updates. ▪ Bug Fixes.
    4. 4. What is Ops? ● Operations: System Administrator/Engineer o Responsible for: ▪ 99.9 % UPTIME. ▪ Code Deployment. ▪ Performance. ▪ Monitoring. ▪ System Security.
    5. 5. The Problem ● Development: o Delay of code deployment into production environment. o Losing market competition to those who are able to deploy code faster. ● Operations: o Number of managed servers increases gradually. o Application code diagnostic and errors spotting.
    6. 6. Solution DevOps is about integrating developers and operations teams to improve collaboration and productivity by Automating infrastructure, Automating workflows and measuring application performance.
    7. 7. Automation ● Automating infrastructure. ● Automating workflows. ● Automating code testing. ● Automate everything.
    8. 8. Development Environment = Production Environment ● Automating infrastructure will allow to have an identical development and production environment. ● Editing small chunks of code will be possible and having a fast pace code release with new feature, security/bug fix will be possible. ● Rolling back to previous code build will be an easy task with deployment automation.
    9. 9. Monitor, Measure and Improve The Code ● Adopting frequent code deployment will lead to iterative process for monitoring measuring and improving the code and operations on daily basis. ● Which will help in fulfilling market needs on time.
    10. 10. Old style vs DevOps style ● Software developers and operation engineers were working separately. ● DevOps approach make them both work together to write configuration management code that describes how things could be built. ● Which leads to reducing deploy time, eliminating deployment fears and fulfilling
    11. 11. Infrastructure Automation
    12. 12. Source Control System ● Using source control system like GIT to manage, track and document both the application code and configuration management code. ● Leads to real time application performance monitoring and optimization due to the ability to spot bugs or code bottlenecks via monitoring tools and fix/deploy the new release or rollback to previous sane one in a very little time due to deployment automation achieved by config management. ● Easily allows developers and operations to see the performance impact of their new changes.
    13. 13. So how to adopt DevOps approach?
    14. 14. Tools ● Source code control system: GitHub. ● Code testing: Jenkins. ● Code Deployment: Chef, Puppet, SaltStack. ● Metrics: Graphite, LogStash. ● Monitoring: NewRelic, Nagios, Graphite.
    15. 15. SaltStack
    16. 16. SaltStack Walk-through ● Remote Execution. ● Configuration Management. ● WalkThrough. ● Average state example. ● More complex state example. ● SaltStack Can Manage Wide Range Of Cloud Infrastructures Also. ● Including OpenStack.
    17. 17. References ● List of useful references and which was used in creating this presentation and others: ○ Vidoes: ■ What is DevOps? - In Simple English ■ Understanding DevOps ■ What is DevOps? A Simple Explanation for Non-Techies ■ Docker and DevOps by Gene Kim ■ IBM DevOps: Continuous delivery of software-driven innovation
    18. 18. References ● List of useful references and which was used in creating this presentation and others: ○ Docs: ■ ■ ■ wp&S_PKG=ov18162 ■ ■