Devops the faster route to production
- 1. DevOps: Faster & more efficient route to production David Okwii davidokwii.com @oquidave Facebook Devp Cycles 19/09/2017
- 2. What is DevOps? DevOps is not a framework or a workflow. It's a culture on how to build and deliver software.
- 3. Why Devops? “Hope is not a strategy” ~ Traditional SRE saying
- 5. The IT crowd
- 7. Game of Code
- 9. Devs & Ops collaborate to achieve a shared goal
- 10. Development to production faster
- 12. 1.Culture
- 14. 2. Automation
- 16. 4. Measure
- 18. DevOps Toolchain
- 19. Devops Tools
Editor's Notes
- #2: Introduce myself, and what I do.
- #4: “Hope is not a strategy” “systems do not run themselves.”
- #6: Inside technology organizations there are many warring tribes developers, sysadmins, security professionals, network admins.
- #7: the developer who's writing code, and then throwing it over the wall to an operations engineer who is supposed to deploy it and then support it. At their core, the development teams want to launch new features and see them adopted by users. At their core, the ops teams want to make sure the service doesn’t break while they are holding the pager. Because most outages are caused by some kind of change—a new configuration, a new feature launch, or a new type of user traffic—the two teams’ goals are fundamentally in tension. "We want to launch anything, any time, without hindrance" versus "We won’t want to ever change anything in the system once it works"
- #8: A tale of two cities
- #9: The irresistible force paradox, also called the unstoppable force paradox: In DC Comics' All-Star Superman by Grant Morrison and Frank Quitely, Superman encounters the Ultrasphinx, who asks "What happens when the unstoppable force meets the immovable object?", to which Superman answers "They surrender."
- #10: http://davidokwii.com/the-solo-african-developer/
- #13: Facebook: Move fast and break things Google: “20% time” policy Netflix: Chaos Monkey
- #15: Tools for release management, provisioning, configuration management, systems integration, monitoring and control, and orchestration become important pieces in building a Devops fabric. Configuration management: Chef, Ansible, Vagrant Version control: git, svn Monitoring: Sensu, zabbix, nagios, Containers: lxc, docker Container manager: kubernetes, Docker swarm Continuous delivery: Jenkins, Hudson Automated builds: Apache Ant, Apache Maven
- #16: Build measure learn repeat 7 wastes of software dev: task switching partially done work motion waiting extra processes, extra features defects
- #17: DevOps strongly advises you to measure key metrics across the organization.Look for things like MTTR, the mean time to recovery, or Cycle Time. Look for costs, revenue,even something like employee satisfaction. https://newrelic.com/resource/how-to-measure-the-success-of-devops Time from feature requested to available in production Time from issue reported to fixed in production
- #18: For openness and transparency Communication and collaboration