DevOps for Developers (Expert's Voice in Web Development)

__DevOps for Developers__ delivers a practical, thorough introduction to approaches, processes and tools to foster collaboration between software development and operations. Efforts of Agile software development often end at the transition phase from development to operations. This book covers the delivery of software, this means “the last mile”, with lean practices for shipping the software to production and making it available to the end users, together with the integration of operations with earlier project phases (elaboration, construction, transition). __DevOps for Developers__ describes how to streamline the software delivery process and improve the cycle time (that is the time from inception to delivery). It will enable you to deliver software faster, in better quality and more aligned with individual requirements and basic conditions. And above all, work that is aligned with the “DevOps” approach makes even more fun! * Provides patterns and toolchains to integrate software development and operations * Delivers an one-stop shop for kick-starting with DevOps * Provides guidance how to streamline the software delivery process ## What you’ll learn ## Who this book is for __DevOps for Developers__ is for motivated software engineers, particularly programmers, testers, QA, system admins, database admins, both beginners and experts, who want to improve their software delivery process. It’s the perfect choice for engineers who want to go the next step by integrating their approaches for development and delivery of software. This book is for engineers who want to shape their processes and decide on and integrate open source tools and seek for guidance how to integrate standard tools in advanced real world use cases. ## Table of Contents Title Page 1 Copyright Page 2 Contents at a Glance 4 Table of Contents 5 About the Author 11 About the Technical Reviewers 12 Acknowledgments 13 Introduction 14 Audience 15 What You Will Learn 15 Book Structure 15 Part I: Fundamentals 17 Chapter 1: Beginning DevOps for Developers 18 The Definition of DevOps 18 Influences and Origins 20 Development and Operations in Conflict 20 Broaden the Usage of Agile 22 Views of DevOps 23 What DevOps Is NOT 24 Roles and Structures 24 DevOps and Tool Suites 26 Structure of This Book 27 Conclusion 27 Chapter 2: Introducing DevOps 29 Traditional Project Settings 29 Agile Project Settings 32 Blame Game: Dev vs. Ops 35 Conflicts During Deployment 35 Conflicts After Deployment 36 Conflicts About Performance 36 Operations as Bottleneck 37 Horizontal Optimization 38 Operations and ITSM 38 DevOps to the Rescue 40 The Essence of DevOps 40 Values and Goals 41 Processes 42 Tools 43 Conclusion 45 Chapter 3: Building Blocks of DevOps 46 Measurement and Metrics 46 Traditional Use of Metrics 47 Agile Approach to Metrics 47 Definition of Done 48 Broken Agile Metrics 48 Qualify Changes 50 Improving Flow of Features 51 Cycle Time 51 Lead Time, Takt Time, and Throughput 52 Improve and Accelerate Delivery 53 Automatic Releasing 54 Pitfalls of Automation 54 Law of Marginal Costs 55 Verb/Noun Mistake 55 Paradox of Automation 55 Irony of Automation 55 Automation Good Practices 56 Apply Releases Incrementally and Iteratively 56 Apply Monitoring, Thoroughly 57 Decoupled Deployment and Release 58 Branch by Abstraction 58 Feature Toggles 58 Dark Launching 59 Blue-Green Deployment 59 Conclusion 60 Part II: Metrics and Measurement View 61 Chapter 4: Quality and Testing 62 What Is Quality? 62 Leading and Supporting Attributes 63 Measurable Attributes 64 Reliability on Context 64 Key Aspects of Quality 65 Patterns for Improving Quality 65 Internal and External Quality 66 Use Scenarios to Describe Quality 66 Quality Is an Inherent Part 67 QA and Making Quality Visible 67 Degeneration: Faults and Failures 68 Test Automation Mix 69 Unit Testing 69 Service Tests 70 UI Testing 70 Errors in Test Strategy 71 Acceptance Criteria 72 Inject Quality Gates 72 Example of a Quality Gate 73 Conclusion 75 Chapter 5: Introduce Shared Incentives 76 War Study: Magic Kingdoms 76 What Is a Team? 77 Goals and Working Agreements 78 Motivation 80 Becoming a Team 81 Tuckman’s Stages of Group Development 82 Facilitator and Caretakers 83 Success Stories 83 Aaron Nichols: DevOps at Rally Software 84 Architecture Council and Weekly Sync Meetings 84 Retrospectives 85 Embracing Change and Experimenting 86 Shared Core Values 86 Lisa Crispin: DevOps, Naturally 87 Shared Responsibilities 87 Brainstorming and Experiments 87 Quality as a Shared Goal 88 Conclusion 88 Part III: Process View 89 Chapter 6: Gain Fast Feedback 90 The DevOps Area Matrix 90 Extend Development to Operations 91 Extend Operations to Development 92 Embed Development into Operations 93 Embed Operations into Development 94 Starting with Kanban 95 Introducing Kanban 95 Five Core Properties 96 An Example Kanban Board for DevOps 97 Example Use Case 98 The Anarchic Approach 99 The Improved Approach 101 Conclusion 103 Chapter 7: Unified and Holistic Approach 104 Getting Started with Concepts 104 Nonfunctional Requirements 105 Conceptual Deficits 107 Origins of Conceptual Deficits 108 Limited Rationality 109 Complex and Dynamic Environments 110 Principal-Agent Problem 110 Moral Hazard 111 Attributes of a Unified Approach 113 Foster Traceability 113 Check Nonfunctional Requirements 115 Align Goals 115 Conclusion 116 Part IV: Technical View 117 Chapter 8: Automatic Releasing 118 Prerequisites for Automatic Releasing 118 Patterns with Appropriate Tools 121 Use Delivery Pipelines 121 Example Pipelines 123 Use Baselines 124 Creating Baselines 124 Picking Up Baselines 126 Shared Version Numbers 128 Accessing Revision Numbers 128 Passing Revision Numbers 129 Version Automatically 129 Parameterizing Maven’s Versions Plug-In 130 Calling During Build Time 131 Further Approaches 132 Use Release Containers with RPM 132 Overview of Topology 132 RPM Spec File and Configuration 134 Apply Task-Based Development 135 Prerequisites and Context 135 Example with Artifactory 136 Use Database Update Scripts 137 Releasing Automatically 137 Example for Handling Change Sets 138 Conclusion 140 Chapter 9: Infrastructure as Code 141 Starting with Infrastructure as Code 142 Traditional Infrastructure Handling 142 How to Do It Better 143 Test Environments with Vagrant 145 Host-Only Networking, Multi-VM Environments 148 Provisioning with Puppet 148 Using Vagrant for Continuous Integration 150 Complementary Tools 153 Provisioning with Puppet 154 Setting Up a Puppet Master 154 Setting Up a Puppet Client 154 Use Case: Open Source Infrastructure with Puppet 156 The Need, from the Jenkins Viewpoint 156 The How at Jenkins 157 Running Puppet 157 The Tradeoffs 157 Source of Truth 159 Testing with Vagrant 160 Full Circle 161 Where to Look Next? 161 Alternatives 162 Conclusion 162 Chapter 10: Specification by Example 163 Getting Started with Acceptance Tests 163 Acceptance Tests as a Communication Vehicle 164 Defining Your Acceptance Criteria 165 Elaborating the Examples 166 Automating the Acceptance Criteria 167 Implementing the Tests 169 Slice High-Level Tests into Steps 169 Table-Driven Tests 170 Test Steps as Java or Groovy Classes 171 Turn Steps into Working Tests 171 Page Object Pattern 172 Reporting on the Test Outcomes 173 Providing Living Documentation 175 Conclusion 175 Moving On 176 Index 177 Front Matter....Pages i-xviii Front Matter....Pages 1-1 Beginning DevOps for Developers....Pages 3-13 Introducing DevOps....Pages 15-31 Building Blocks of DevOps....Pages 33-47 Front Matter....Pages 49-49 Quality and Testing....Pages 51-64 Introduce Shared Incentives....Pages 65-77 Front Matter....Pages 79-79 Gain Fast Feedback....Pages 81-94 Unified and Holistic Approach....Pages 95-107 Front Matter....Pages 109-109 Automatic Releasing....Pages 111-133 Infrastructure as Code....Pages 135-156 Specification by Example....Pages 157-170 Back Matter....Pages 171-176 Michael Hüttermann. Includes Bibliographical References And Index.