DevOps transformations

Andrey Adamovich, DevChampions

-

-

-

"DevOps" tools

Tools

...

More tools

...

Even more tools

...

Is this the best stack?

...

Does this help?

...

Or this?

..

Ocean of tools!

-

But...

DevOps is not about tools!

Or is it?

History

Tools and weapons

f

Build and protect!

We use tools to protect our culture!

Tools vs Culture

Cargo cult

s

Healthy lifestyle

Start running

-

Broken leg!

-

Regret

-

Running does not work!

Running is not for me!

Running is for healthy people!

Well...

Combination of things

  • Just walking instead of running
  • Different diet
  • More sleeping time
  • Mix activities
  • Reduce stress (peace of mind)
  • Find a trainer/mentor

Tools vs Culture

Dialogues

-

-

-

-

Broken communication

d

Rigid structure

d

Lack of culture?

Lack of tooling?

2001

Agile

Agile principles

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

2003

-

Mary Poppendieck

-

Lean Software Development

Lean principles

  • Eliminate waste
  • Amplify learning
  • Decide as late as possible
  • Deliver as fast as possible
  • Empower the team
  • Build integrity in
  • See the whole

2008

-

Andrew Clay Shafer

-

Infrastructure is Code

-

Patrick Debois

-

Agile Infrastructure

DevOps

Wikipedia

DevOps aims at shorter development cycles, increased deployment frequency, and more dependable releases, in close alignment with business objectives.

2010

-

John Willis

-

C.A.M.S

  • Culture
  • Automation
  • Measurement
  • Sharing

2011

-

Jez Humble

-

CD principles

  • Build quality in
  • Work in small batches
  • Computers perform repetitive tasks, people solve problems
  • Relentlessly pursue continuous improvement
  • Everyone is responsible

2013

-

Gene Kim

-

The 3 ways of DevOps

The first way

a

The second way

a

The third way

a

Isomorphic models

2017

GitOps!

GitOps

  • Provisioning and deployment is declarative
  • Entire system state is under version control
  • Operational changes are made by pull request (plus build & release pipelines)
  • Diff tools detect any divergence and sync tools enable convergence
  • Rollback and audit logs are also provided via Git

Ops by pull request

The single source of truth

Knowledge capture

Everything is code!

Everything is code

  • Pipeline-as-code
  • Documentation-as-code
  • Tests-as-code
  • Security-as-code
  • Infrastructure-as-code
  • Network-as-code
  • Metrics-as-code

How?

Who do we need?

T-shaped people

a

T-shaped people

a

How do we plan?

-

Gene Kim

-

Unplanned work

a

Unplanned work

a

Unplanned work

a

Unplanned work

a

-

Dominica DeGrandis

-

Time thieves

s

Reduce WIP

More No!

How should we work together?

-

Mathew Skelton

-

DevOps Topologies

Type 1: Dev and Ops Collaboration

a

Type 2: Fully Shared Ops Responsibilities

a

Type 3: Ops as Infrastructure-as-a-Service

a

Type 4: DevOps as an External Service

a

Type 5: DevOps Team with an Expiry Date

a

What should we use?

-

Neal Ford

-

Innovation curve

A

Technology radar

A

Rings

  • Hold
  • Assess
  • Trial
  • Adopt

Quadrants

A

Radar example

a

Radar example

b

Future is here!

The future is already here ? it's just not very evenly distributed.

William Gibson

Where do we aim?

Where is the industry going?

-

Simon Wardley

-

Maps

  • Visual
  • Context
  • Position, anchor and movement
  • Components

Maps

  • Navigation
  • Learning
  • Strategy
  • Situational awareness

Maps

m

Final words

  • Directions and planning as well as progress should be visible (radars, maps, boards)
  • VCS repos are the source of truth (CD + GitOps)
  • Pipelines handle all aspects of software delivery (CD + GitOps)
  • Tools do not matter that much, but use them to enforce your culture!

The game

Thank you!

-