This document summarizes tools and techniques for collaboration between Dev and Ops teams, including: - Shared version control of infrastructure as code, secrets stores, and documentation to provide transparency. - The use of dashboards, chat, wikis, and monitoring and logging tools to share information across teams. - Having Dev and Ops use the same environment names and classifications to facilitate coordination between pipelines, dashboards, and other systems.

1. How collaboration
works between
Dev and Ops
Giulio Vian
DevOps, Agile Testing and Test Summit
Dublin, 6 February 2020

2. Topic
Tools and
techniques for a
fluent flow of
information and
artefacts between
Dev and
Ops

3. Logistic
Presentation deck on SlideShare (giuliov)
Bibliography at the end
Questions at the end
Is my timer running?

4. Source: Microsoft

5. Principles
Transparency
Shared Responsibility
Shared Goals
Photo by Pere López

6. Source: Gartner

7. Shared information
Version Control
Secret Stores
Environments
Chat & Wiki
Dashboards
Reviews & Approvals
Monitoring & Logs

8. DashboardsTech

9. Dashboards
© Unum
Process
Adapted from © AgileCraft

10. Dashboards
© BrainsMcFadden
Biz

11. Environments
Dev & Ops use the same names
Names reflected in tools
Pipelines, dashboards, monitors, log sources
ABC classification
Minimize Change Approval Board

12. Reviews & Approvals

13. Version Control
Shared actionable description of infrastructure
Shared actionable description of pipelines
Documentation changes synchronised
Review & approve mechanism
Pull requests
Access control & code isolation

14. Infrastructure as Code
Version
Control
Secrets
Store
Infrastructure
Pipeline

15. IaC examples resource "azurerm_resource_group" "hello" {
name = "demo-${var.env_name}"
location = var.resource_group_location
tags = {
environment = var.env_name
}
}
Resources:
HelloBucket:
Type: AWS::S3::Bucket
// Copyright 2016-2019, Pulumi Corporation. All rights reserved.
import * as gcp from "@pulumi/gcp";
const greeting = new gcp.cloudfunctions.HttpCallbackFunction("greeting", (req, res)
=> {
res.send(`Greetings from ${req.body.name || "Google Cloud Functions"}!`);
});
export const url = greeting.httpsTriggerUrl;

16. Fractal
Version
Control
Secrets
Store
Run-time
Infrastructure
Version
Control
Secrets
Store
CD
Infrastructure
Version
Control
Secrets
Store
Application
Run-time
Transparency
Shared Responsibility
Shared Goals

17. Secret Stores
Hierarchically organised
Native or use separate instances
Devs manage secrets keys (within app scope)
Key Lifecycle, e.g. retirement of application
Ops manage secrets values
Value Lifecycle, e.g. Certificate expiration
Secrets:
Passwords
Tokens
Crypto Keys
Certificates

18. Chat
Self-subscription to events
chatbot commands
Kick-off builds or deployments
Approvals
Mix notification with comments

19. Chat Notifications

20. Chatbot

21. Chat Notifications

22. Wiki

23. Wiki
Single-place when searching
Shared pages
Hierarchical structure
Librarian role

24. Monitoring & Logs

25. Monitoring & Logs

26. Monitoring & Logs
Accessible to everyone
From everywhere
Centralised and searchable

27. Principles
Transparency
Shared Responsibility
Shared Goals
Photo by Pere López

28. Continuous Improvement
Projection Reality

29. Bibliography
The DevOps Handbook
G.Kim, P.Debois, J.Willis, J.Humble (IT Revolution 2016)
Accelerate
Nicole Forsgren, Jez Humble (Trade Select 2018)
Project to Product
Mik Kersten (IT Revolution 2019)
The Mythical Man-Month
Frederick P. Brooks Jr. (Addison Wesley 1995, 2nd ed.)
Site Reliability Engineering
B.Beyer , C.Jones, J.Petoff, N.R.Murphy (O′Reilly 2016)
Making Work Visible
Dominica Degrandis (IT Revolution 2017)
29

30. Giulio Vian
Senior
DevOps
Engineer
Hardware spec:
1 KB RAM
(16KB after upgrade)
4 KB ROM
(8KB after upgrade)
First computer Past Companies Communities

31. Address
giulio.dev@casavian.eu
@giulio_vian
https://www.slideshare.net/giuliov
http://blog.casavian.eu
https://medium.com/@giuliovdev
https://github.com/giuliov

32. The End