la la land of devops integration (tugait)

TUGA IT 2017LISBON, PORTUGAL

THANK YOU TO OUR SPONSORSPLATINUM

GOLD SILVER

PARTICIPATING COMMUNITIESCLOUD PRO PT

La La Land of DevOps Integration

Manuel Pais | Skelton Thatcher Consulting@manupaisable | skeltonthatcher.com

TugaIT 2017 / @tugaitconf / #tugait19 May 2017, Lisbon PT

Continuous Delivery (Tooling) (Anti-)Patterns

Manuel Pais | Skelton Thatcher Consulting@manupaisable | skeltonthatcher.com

TugaIT 2017 / @tugaitconf / #tugait19 May 2017, Lisbon PT

Today1. DevOps integration: two camps 2. Pattern #1: Best of breed tools3. Pattern #2: Pipeline = workflow4. Pattern #3: Own your golden logs

About meManuel Pais

@manupaisable

Consultant at Skelton Thatcher Consulting

teamtopologies.com

Upcoming book:

Team Topologies for effective software systems

by Matthew Skelton & Manuel Pais

releasabilitybook.com

Upcoming book:

Team Guide to Software Releasability

by Chris O’Dell & Manuel Pais

Team-first digital transformation30+ organisations

UK, US, DE, PT, India, Chinaskeltonthatcher.com

Today1. DevOps integration: two camps 2. Pattern #1: Best of breed tools3. Pattern #2: Pipeline = workflow4. Pattern #3: Own your golden logs

“integrating various tools in software

delivery is very hard”

“a toolchain is a design pattern that everybody

can agree on”

Integrated DevOps Tool

In the left corner…

Integrated DevOps

Toolchain

In the right corner…

Integrated DevOps

Toolchain

Integrated DevOps Tool

Integrated DevOps

Toolchain

Integrated DevOps Tool

Quick setup, familiarity

Less to worry about

Integrated DevOps Tool

Long term ownership

Best tool for (each) job

Integrated DevOps Toolchain

tool choices…are trade-offs

the problem is not being aware of those trade-offs

some patternsbecome extremely hardwith integrated tools…

Today1. DevOps integration: two camps 2. Pattern #1: Best of breed tools3. Pattern #2: Pipeline = workflow4. Pattern #3: Own your golden logs

Integrated DevOps Tool

Integrated DevOps Toolchain

single-purpose toolsneed APIs to survive

Integrated DevOps Tool

Integrated DevOps Toolchain

Integrated DevOps Toolchain

Integrated DevOps Toolchain

a flexible toolchain standardizes practices,

not tools

Integrated DevOps Tool

Integrated DevOps Tool

tooling should evolvewhen YOU need it

Limit blast radius

tightly coupled tooling

tightly coupled tooling

tightly coupled tooling

tightly coupled tooling

limit blast radius

poorly understood concepts

poorly understood concepts

Today1. DevOps integration: two camps 2. Pattern #1: Best of breed tools3. Pattern #2: Pipeline = workflow4. Pattern #3: Own your golden logs

what’s missing?

what’s missing?we tend to care about

technical bits only…

painful bottlenecksin team interactions

bottlenecks = silos

time is lost in queues, not execution

automating hand-offs requires trust… which in

turn requires time

breaking down silos is HARD!

extra credit…

non-technical stakeholdersare part of delivery too

pipeline = (real) workflow

highlight bottlenecks => build bridgestrust requires time => automate gradually

not just technical => include everyone

pipeline = (real) workflow

highlight bottlenecks => build bridgestrust requires time => automate gradually

not just technical => include everyone

pipeline = (real) workflow

highlight bottlenecks => build bridgestrust requires time => automate gradually

not just technical => include everyone

Today1. DevOps integration: two camps 2. Pattern #1: Best of breed tools3. Pattern #2: Pipeline = workflow4. Pattern #3: Own your golden logs

the problem with logs

111.222.333.123 HOME -[01/Feb/1998:01:08:39 -0800] "GET /bannerad/ad.htm HTTP/1.0" 200 198 "http://www.referrer.com/bannerad/ba_intro.htm" "Mozilla/4.01 (Macintosh; I; PPC)"

the (other) problem with logs

the (other) problem with logs

too much information

information hiding

the (other) problem with logs

information hiding

the (other) problem with logsintegrated tools

information hiding

the (other) problem with logs

too much information

information hiding

the (other) problem with logs

too much information

difficult to use log aggregation to diagnose pipeline issues with an integrated DevOps tool

information hiding should not be the reason why you can’t diagnose

the problem with error messages

generic error messages

generic error messages

“VM could not be started”

generic error messages

“VM could not be started”

“Deployment failed”

without correct error information you can’t

diagnose/improve

log aggregation

own your logsquickly find correlated events

don’t depend on generic error messagesextract pipeline metrics (bonus)

Today1. DevOps integration: two camps 2. Pattern #1: Best of breed tools3. Pattern #2: Pipeline = workflow4. Pattern #3: Own your golden logs

Tomorrow

tooling choices are trade-off choices

Tomorrow

tool chain ownership supports evolution

Tomorrow

visualize real workflow to break down silos

Sources• Betty Zakheim, 2017, ‘How Difficult Can It Be to Inte-

grate Software Development Tools? The Hard Truth’,https://www.infoq.com/articles/tool-integration-hard-truth

• Damon Edwards, 2014 ‘DevOps is an Enterprise Concern’,https://www.infoq.com/interviews/interview-damon-edwards-qcon-2014

• Don G. Reinertsen, 2009, ‘The Principles of Product Development Flow: Second Generation Lean Product Development’ https://www.youtube.com/watch?v=L6v6W7jkwok

thank you

Manuel Pais@manupaisable

skeltonthatcher.com

La La Land of DevOps Integration

Manuel Pais | Skelton Thatcher Consulting@manupaisable | skeltonthatcher.com

TugaIT 2017 / @tugaitconf / #tugait19 May 2017, Lisbon PT

PLEASE FILL IN EVALUATION FORMSFRIDAY, MAY 19th SATURDAY, MAY 20th

https://survs.com/survey/cprwce7pi8 https://survs.com/survey/l9kksmlzd8

YOUR OPINION IS IMPORTANT!

THANK YOU TO OUR SPONSORSPLATINUM

GOLD SILVER

Short and Wide Pipeline