“Hope is not a strategy”
“systems do not run themselves.”
Inside technology organizations there are many warring tribes developers, sysadmins, security professionals, network admins.
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"
A tale of two cities
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."
http://davidokwii.com/the-solo-african-developer/
Facebook: Move fast and break things Google: “20% time” policy Netflix: Chaos Monkey
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
Build measure learn repeat
7 wastes of software dev:
task switching
partially done work
motion
waiting
extra processes,
extra features
defects
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
For openness and transparency
Communication and collaboration
