DevOps

Questions I Will Answer Today

• What Is DevOps?
• What Problems Will DevOps Help Me Solve?
• How Do I Get Started?
• What Mistakes Can I Avoid?

Who Am I?

Note : [ Hit 's' for more Information]

The Problem In A Nutshell

• Everything needs software.
• Software runs on a server to become a service.
• Delivering a service from inception to its users is too slow and error-prone.
• There are internal friction points that make this the case.
• This loses you money. (Delay = loss)
• Therefore IT is frequently the bottleneck in the transition of "concept to cash."

Symptoms

• Defects released into production, causing outage
• Inability to diagnose production issues quickly
• Problems appear in some environments only
• Blame shifting/finger pointing
• Long delays while dev, QA, or another team waits on resource or response from other teams
• "Manual error" is a commonly cited root cause
• Releases slip/fail
• Quality of life issues in IT

Note : [ Hit 's' for more Information]

Why Does This Problem Exist?

• "Business-IT Alignment?"
• The business has demanded the wrong things out of IT
• Cost sensitive
• Risk averse
• IT has metastasized over time into a form to give the business what it's said it wants
• Centralized and monolithic
• Slow and penny wise, pound foolish

But Then We Demanded Innovation

DevOps Defined

• DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support.
• DevOps is also characterized by operations staff making use many of the same techniques as developers for their systems work.

[Note: "Press 's' for More information"]

DevOps Defined

• DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support.
• DevOps is also characterized by operations staff making use many of the same techniques as developers for their systems work.

[Note: "Press 's' for More information"]

[Note: "Press 's' for More information"]

DevOps History In 60 Seconds

Where Do I Start?

[Note: "Press 's' for More information"]

DevOps Concepts

• DevOps Principles
• DevOps Practices
• DevOps Tools

[Note: "Press 's' for More information"]

DevOps Principles

• The Three Ways
• Systems Thinking
• Amplify Feedback Loops
• Culture of Continual Experimentation
• CAMS
• Culture - People > Process > Tools
• Automation - Infrastructure as Code
• Measurement - Measure Everything
• Sharing - Collaboration/Feedback
• Informed by the values in the Agile Manifesto and Lean Theory of Constraints

DevOps Practices

• Version Control For All
• Automated Testing
• Proactive Monitoring and Metrics
• Kanban/Scrum
• Visible Ops/Change Management
• Configuration Management
• Incident Command System
• Continuous Integration/Deployment/Delivery
• "Put Developers On Call"
• Virtualization/Cloud/Containers
• Toolchain Approach
• Transparent Uptime/Incident Retrospectives

[Note: "Press 's' for More information"]

An Implementation Model

[Note: "Press 's' for More information"]

Add Ops Into Dev

Accelerate Flow To Production

• Reduce batch size
• Automated environments mean identical dev/test/prod environments
• Create safety through automation
• Continuous Integration/Testing
• Automated Regression Testing
• Continuous Delivery
• Continuous Deployment
• Feature Flags (A/B testing)
• Security Testing

Add Dev Into Ops

• Don't do tasks for people. Build tools so they can do their own work.
• Monitoring/logging/metrics feeds back into dev (and the business)
• Blameless Incident Postmortems
• Developers Do Production Support/Empower Ops Acceptance

Grass Roots Checklist

• Find ways to collaborate - involve others early
• Find ways to automate and make self-service
• Become metrics driven
• Learn new things, continually improve
• Understand the larger business goals, metrics, and priorities you support
• Communicate
• Work in parallel with small batches
• Allow refactoring
• Prove the business value to management

Management Checklist

• Experiment - choose a test case as a pilot
• Then document and spread best practices
• Empower your teams, but guide their values
• Metrics are your friend - demand measurable outcomes
• Don't accept excuses when the old baseline isn't good enough
• Fail fast, continually improve
• Build on small successes to gain broad support for more substantive change.
• Align roles and responsibilities across groups -enable collaboration even if it seems "inefficient"

Things Not To Do

• Only Token Gestures
• "Ops team, change your name to DevOps team!"
• "Put DevOps in those job titles!"
• Only Implement Tools
• Changing tools without changing tactics leaves the battlefield strewn with bodies
• Create More Silos
• Devalue Operations Or Development Knowledge
• Anything You're Not Measuring The Impact Of

[Note: "Press 's' for More information"]

Does It Really Help?

• 2014 State of DevOps Report (9200 surveyed) measured correlation between high performing organizations and DevOps practice adoption
• Lead time to changes down
• MTTR up
• No alteration in change fail rate

Core DevOps Research List

Thanks !!!