DevOps for developers

Machine generated contents note: pt. I Fundamentals --

ch. 1 Beginning DevOps for Developers --

Definition of DevOps --

Influences and Origins --

Development and Operations in Conflict --

Broaden the Usage of Agile --

Views of DevOps --

What DevOps Is NOT --

Roles and Structures --

DevOps and Tool Suites --

Structure of This Book --

Conclusion --

ch. 2 Introducing DevOps --

Traditional Project Settings --

Agile Project Settings --

Blame Game: Dev vs. Ops --

Conflicts During Deployment --

Conflicts After Deployment --

Conflicts About Performance --

Operations as Bottleneck --

Horizontal Optimization --

Operations and ITSM --

DevOps to the Rescue --

Essence of DevOps --

Values and Goals --

Processes --

Tools --

Conclusion --

ch. 3 Building Blocks of DevOps --

Measurement and Metrics --

Traditional Use of Metrics --

Agile Approach to Metrics --

Improving Flow of Features --

Cycle Time --

Lead Time, Takt Time, and Throughput --

Improve and Accelerate Delivery --

Automatic Releasing --

Decoupled Deployment and Release --

Conclusion --

pt. II Metrics and Measurement View --

ch. 4 Quality and Testing --

What Is Quality? --

Leading and Supporting Attributes --

Patterns for Improving Quality --

Internal and External Quality --

Use Scenarios to Describe Quality --

Quality Is an Inherent Part --

Test Automation Mix --

Inject Quality Gates --

Conclusion --

ch. 5 Introduce Shared Incentives --

War Study: Magic Kingdoms --

What Is a Team? --

Goals and Working Agreements --

Motivation --

Becoming a Team --

Tuckman's Stages of Group Development --

Facilitator and Caretakers --

Success Stories --

Aaron Nichols: DevOps at Rally Software --

Lisa Crispin: DevOps, Naturally --

Conclusion --

pt. III Process View --

ch. 6 Gain Fast Feedback --

DevOps Area Matrix --

Extend Development to Operations --

Extend Operations to Development --

Embed Development into Operations --

Embed Operations into Development --

Starting with Kanban --

Introducing Kanban --

Five Core Properties --

Example Kanban Board for DevOps --

Example Use Case --

Anarchic Approach --

Improved Approach --

Conclusion --

ch. 7 Unified and Holistic Approach --

Getting Started with Concepts --

Nonfunctional Requirements --

Origins of Conceptual Deficits --

Limited Rationality --

Complex and Dynamic Environments --

Principal-Agent Problem --

Moral Hazard --

Attributes of a Unified Approach --

Foster Traceability --

Check Nonfunctional Requirements --

Align Goals --

Conclusion --

pt. IV Technical View --

ch. 8 Automatic Releasing --

Prerequisites for Automatic Releasing --

Patterns with Appropriate Tools --

Use Delivery Pipelines --

Use Baselines --

Shared Version Numbers --

Version Automatically --

Use Release Containers with RPM --

Apply Task-Based Development --

Use Database Update Scripts --

Conclusion --

ch. 9 Infrastructure as Code --

Starting with Infrastructure as Code --

Traditional Infrastructure Handling --

How to Do It Better --

Test Environments with Vagrant --

Host-Only Networking, Multi-VM Environments --

Provisioning with Puppet --

Using Vagrant for Continuous Integration --

Complementary Tools --

Provisioning with Puppet --

Setting Up a Puppet Master --

Setting Up a Puppet Client --

Use Case: Open Source Infrastructure with Puppet --

Need, from the Jenkins Viewpoint --

How at Jenkins --

Where to Look Next? --

Alternatives --

Conclusion --

ch. 10 Specification by Example --

Getting Started with Acceptance Tests --

Acceptance Tests as a Communication Vehicle --

Defining Your Acceptance Criteria --

Elaborating the Examples --

Automating the Acceptance Criteria --

Implementing the Tests --

Slice High-Level Tests into Steps --

Table-Driven Tests --

Test Steps as Java or Groovy Classes --

Turn Steps into Working Tests --

Page Object Pattern --

Reporting on the Test Outcomes --

Providing Living Documentation.