Operation Framework study found the best-performing organization were better at diagnosing & fixing service incidents. 1. “Culture of Causality” 2. Used disciplined approach to solving problems using telemetry graph of something that isn’t moving yet, just in case it decides to make a run for it…Tracking everything is key to moving fast, but the only way to do it is to make tracking anything easy…We enable engineers Collection at business logic, application, & environments layer a. Events, logs, & metrics b. Common service to centralize, rotate, and delete 2. Event router responsible for storing our events and metrics

control repository ii. Version control is for everyone in the value stream iii. Everything, everything, everything is checked into version control 1. Application code & dependencies 2. Environment – continually ensure all environments are synchronized and consistent e. ENABLE AUTOMATED SELF-SERVICE DEPLOYMENTS i. As a result of compliance, oversight, and control needs separate Operations groups deployment ii. Shows readiness of production environments at a glance iii. Provides push-button, self-service for any suitable version into production iv. Record automatically for auditing who and what commands

Velocity all about? What did I learn? Service Workers: The Practical Bits by Patrick Meenan (Google) @patmeenan http://www.slideshare.net/patrickmeenan/service-workers-for-performance  They are effectively Financial Training by David Genn (IG) @david_genn  Separate deployment from release  Automate everything  Trust your tests  Conversations are way better than project proposals  Start small, be

constraint (Machines should not take lunch breaks) STEP 3 SUBORDINATE everything else to the above decision (Making sure everything marches to the tune of the constraint) STEP 4 ELEVATE the system’s

organizations are typically structured as:1. Standardized Model – where routine and systems govern everything; including strict compliance with budget and schedule 2. Experimental Model – every day every pioneered at GitHub – put automation tools (Hubot) into the middle of their chatrooms 1. Everyone saw everything that was happening 2. New engineers could see what daily work and how it was performed 3. People

happen. Meanwhile, the department handles IT upgrades for the parts of the government that do everything from issue driver’s licenses, to distribute unemployment benefits, to regulate fish and wildlife

studied.  Created a self-improvement project  2 week iterations, planning and demos  Put everything into a repository (configurations, scripts, etc.) Infrastructure as Code  Turned over repeatable

or use technology to overcome our inherent shortcomings.” The Truth about Relativity – Why Everything Is Relative – Even When It Shouldn’t Be  Examples: House Shopping, Vacations,  Observations:

sidecar container will include: 1. A logging agent to push logs to a platform centralized logging service. 2. Container policy enforcement. This includes ensuring container hardening from DCAR containers notifications when there is anomalous behavior. 4. Vulnerability Management 5. A service mesh proxy to connect to the service mesh 6. Zero Trust down to the container level. Zero trust requires strict Program-specific Log Storage and Retrieval Service 2. Service Mesh 3. Program-specific artifact repository 4. Runtime Behavior Analysis Artificial Intelligence (AI) service 5. DCAR for the hardened containers

Respond to the rapidly changing competitive landscape 2. Provide stable, reliable, and secure service to the customer b. THE BUSINESS VALUE OF DEVOPS i. Code and change deployments (thirty times more iii. Production deployments (sixty times higher change success rate) iv. Mean time to restore service (168 times faster) 4. An Introduction to The DevOps Handbook xxi 5. PART I—THE THREE WAYS 1 a desired iv. Operations – the team responsible for maintaing the production environment and ensuring service levels are met v. Infosec – team responsible for securing systems and data vi. Release Managers