47
© 2016 CloudBees, Inc. All Rights Reserved 1 © 2016 CloudBees, Inc. All Rights Reserved Crossing the DevOps Chasms with Tools & Technology Brian Dawson, CloudBees DevOps Evangelist and Jenkins PMM @brianvdawson [email protected] DevOps Quadrants Webinar Series - Part #3: Tom McGonagle, CloudBees Sr. DevOps Consultant @mcgonagle [email protected]

Crossing the DevOps Chasms with Tools & Technology · PDF fileudBees 1 Crossing the DevOps Chasms with Tools & Technology Brian Dawson, CloudBees Tom DevOps Evangelist and Jenkins

  • Upload
    lamdien

  • View
    223

  • Download
    4

Embed Size (px)

Citation preview

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

1

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

Crossing the DevOps Chasms with Tools & Technology

Brian Dawson, CloudBees DevOps Evangelist and Jenkins PMM @brianvdawson [email protected]

DevOps Quadrants Webinar Series - Part #3:

Tom McGonagle, CloudBees Sr. DevOps Consultant @mcgonagle [email protected]

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

2

•  Review Quadrants Model

•  Transformation Strategies and Tools

•  Attributes of Enabling Tools and Technology

•  *Real World Examples

•  Next

…Gain inspiration on how to drive your DevOps transformation

Agenda

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

3

Introduction Background:

•  QA, Development, Sys Admin, Development Management, etc

•  Software development optimization –  1990s

o  Graphics pipeline optimization o  Tools and middleware

–  Early 2000’s o  OSS practices

–  Late 2000’s o  Process consulting o  CI, CD, and DevOps transformation practice

•  Knowledge redistribution = IT Socialist

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

4

•  What is your organizations current tools strategy?

–  There is none

–  Tool selection is the domain of individual teams/groups

–  Some standardization and/or centralization

–  Full standardization and/or centralization

Poll Question #1

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

5 5

Review of the DevOps Maturity

Quadrants

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

6

• Simplified model for assessing, and discussing DevOps transformations

• Derived from and applied in real-world DevOps transformations

• Flexible vs rigid, allows for subjective definition of maturity

• Extensible as method of driving, monitoring and measuring transformation

The Quadrants Model

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

7

The Quadrants

Quadrant 1: Team-level

Agile

Quadrant 2: Team-level

CD

Quadrant 3: Enterprise

Agile

Quadrant 4: Enterprise DevOps

Team

W

orkg

roup

En

terp

rise

Define Plan Code Build Integrate Test Release Deploy Operate

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

8

The Quadrants

Quadrant 1: Team-level

Agile

Quadrant 2: Team-level

CD

Quadrant 3: Enterprise

Agile

Team

W

orkg

roup

En

terp

rise

Define Plan Code Build Integrate Test Release Deploy Operate

Enterprise DevOps 10%

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

9

The Quadrants

Quadrant 1: Team-level

Agile

Quadrant 2: Team-level

CD

Quadrant 3: Enterprise

Agile

Team

W

orkg

roup

En

terp

rise

Define Plan Code Build Integrate Test Release Deploy Operate

Enterprise DevOps

•  Innovate faster

•  Respond to market

•  Gain competitive advantage

•  Increased productivity

•  Employee satisfaction and retention

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

10

The Chasms

Upstream Downstream

People & Culture

Process & Practices

Tools & Technology

Αγιλε, Σχρυµ, Κανβαν ΠΜΒΟΚ, ΙΤΙΛ, Ωατερφαλλ

Ποιντ Τοολσ,Γρασσροοτσ, Ραπιδ

Χηανγε

Μοϖε Φαστ, Ιννοϖατε Μαινταιν Θυαλιτψ Σταβιλιτψ, Υπτιµε

Εντερπρισε Χλασσ, Χορπ. Προχυρεµεντ, Σταβλε

Define Plan Code Build Integrate Test Release Deploy Operate

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

11

Tools as the Foundation

Upstream Downstream

People & Culture

Process & Practices

Tools & Technology

Αγιλε, Σχρυµ, Κανβαν ΠΜΒΟΚ, ΙΤΙΛ, Ωατερφαλλ

Ποιντ Τοολσ,Γρασσροοτσ, Ραπιδ

Χηανγε

Μοϖε Φαστ, Ιννοϖατε Μαινταιν Θυαλιτψ Σταβιλιτψ, Υπτιµε

Εντερπρισε Χλασσ, Χορπ. Προχυρεµεντ, Σταβλε

Define Plan Code Build Integrate Test Release Deploy Operate

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

12

• People, Process and Tools

• CD and DevOps (practically) require automation

• Automation requires tooling

• Tools are the most quantifiable

• Starting point and foundation

DevOps Trinity and Tools

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

13

•  Which quadrant are you in?

–  Quadrant 1 – Team-Level Agile

–  Quadrant 2 – Team-Level CD

–  Quadrant 3 – Enterprise Agile

–  Quadrant 4 – Enterprise CD or DevOps

–  Quadrant 0 – None (Legacy, Waterfall)

Poll Question #2

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

14 14

Transformation Strategies and

Tools

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

15

Adoption Pattern Example

Left-to-Right, Team-level

1.  Team(s) adopt agile planning and project management

2.  Team(s) extend CI to Continuous Delivery

3.   Organization implements agile

4.   Organization aligns on DevOps strategy with teams using common CI/CD process and tools 1

3 4

2

Team

W

orkg

roup

En

terp

rise

Define Plan Code Build/CI Test Release/Deploy Operate

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

16

Adoption Cycles: Bottom-Up

1

64

3

Adoption

Team Level

Initiation

Executive Awareness

Team Successes

Workgroup Success

Scale Across Workgroups

Executive Support 2 5

Visibility

Team

W

orkg

roup

En

terp

rise

Time

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

17

Adoption Cycles: Top-Down

Visibility

Executive Initiative

Team Successes

Workgroup Success

Scale Across Workgroups

1

2

6

4

3

Workgroup Initiative

Team

W

orkg

roup

En

terp

rise

Time

Adoption

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

18

Discover: Determine current state and maturity

Define: Establish objectives

Map: Journey through the quadrants

Cross chasms, connect quadrants, continuously

improve

Order of Operations WHERE ARE

WE?

WHERE ARE WE GOING?

HOW DO WE GET THERE?

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

19

•  Identify pilot project

•  Form cross-functional ”red” team

•  Adopt unifying technologies

•  Establish plan with measurable KPI’s and milestones

•  Go!

•  Measure, document report, refine   •  Scale and Onboard

–  Extend tools to support team specific needs

Transformation Strategies

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

20 20

Enabling Tools and Technologies

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

21

Tools & Technologies enable “crossing the chasm”

Normalized

ü  Language and practice agnostic

ü  Not Dev or Ops specific

ü  Distributed

Rich Integration Support

ü  Tools as microservices

ü Modular

Automated

ü  Repeatability

ü  Reportability

ü  Flexibility

Increase Confidence In Downstream Deliverables

ü  Support supply-chain

ü  Traceability

ü  Immutability

ü Measure and report

Scale To Enterprise

ü  Cross-domain visibility metrics

ü  Security and governance

ü  Supported

21

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

22

Solution Soup

CloudBees

Jenkins OSS

Rally

Jira

Misc Point Solutions

Chef Puppet

HP OO

SVN Git

Nolio Miscellaneous ALM Solutions

HP ALI

TestLink

Helpdesk

Selenium

PPM

XL Release

Nexus

Chat LDAP

APM

Docker

Team

W

orkg

roup

E

xecu

tive

Define Plan Code Build Integrate Test Release Deploy Operate

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

23

Team

W

orkg

roup

E

xecu

tive

Define Plan Code Build Integrate Test Release Deploy Operate

Mis

c P

oint

S

olut

ions

Jira

, Te

amFo

rge.

.

Ecl

ipse

, In

telli

J, S

VN

, G

it

Jenk

ins,

M

ake,

M

aven

..

Jenk

ins,

CI

Sol

utio

ns

Sel

eniu

m,

Test

Link

XL

Rel

ease

, H

P O

O…

XL

Rel

ease

, H

P O

O…

Cha

t, Lo

ggin

g,

Mon

itorin

g

LDAP, SAML

Product Portfolio

Application Performance Mgt

Service Desk

Integrate and Automate

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

24

Security, Scalability and Manageability

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

25

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

26 26

*Real World Examples

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

27

http://www.slideshare.net/collabNet/achieving-devops-using-open-source-tools-in-the-enterprise

Traceability and Reportability

http://www.slideshare.net/SonatypeCorp/devops-and-continuous-delivery-reference-architectures

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

28

Visibility

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

29

Visibility and Metrics

http://www.capitalone.io/blog/hygieia-making-sense-out-of-your-devops-tools/

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

30

Reliability and Repeatability

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

31

Reliability and Repeatability

Supply Chain

Automation

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

32

Automation Coverage

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

33

Continuous Delivery and Automation are Key

Development Production

Commit Build Test Stage Deploy

Feedback Loop

$ The Business

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

34

Continuous Delivery Needs an Automation Engine

Complex Delivery Pipelines

Delivery of App and Config

Robust and Highly Available

Results Report

SOURCE CODE

CONTROL SYSTEM

Code Commit

</> Development Production

Continuous Integration/Delivery

Commit Build Test Stage Deploy

! ! !

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

35

Jenkins Powered CD Pipelines: Jenkins Pipeline

Development Production

Commit Build Stage Deploy

? ?

Pipelines Need: P  Branching P  Looping

P  Restarts P  Checkpoints P  Manual Input

Sonar Test

Selenium Test

Perf Test

Jenkins Pipeline

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

36

Pipeline Code Example

node('docker'){checkoutscm/*GrabtheabbreviatedSHA1ofourpipeline’scommit.*/sh'gitrev-parseHEAD>GIT_COMMIT'defshortCommit=readFile('GIT_COMMIT').take(6)stage'Build'defimage=docker.build("jenkinsciinfra/bind:build-${shortCommit}")stage'Deploy'image.push()}

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

37

Pipeline Code Examples

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

38

A Real-world CD Pipeline with Jenkins Pipeline

Development Production

Pipelines Need: P  Branching P  Looping

P  Restarts P  Checkpoints P  Manual Input

Jenkins Pipeline

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

39

Criteria for CD & DevOps @ Scale

Ongoing support & maintenance

Security & compliance

Scale & operations

Control & visibility

Enterprise Continuous Delivery

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

40

CloudBees Jenkins Platform – Private SaaS Edition

CloudBees Jenkins Platform – Private SaaS Edition

VM VM VM VM

Private Cloud Infrastructure

Private SaaS Edition Control Tier

CloudBees Jenkins

Operations Center

Reso

urce

Mgm

t Ti

er

Stor

age

(NFS

/EBS

)

Developer

SOURCE CODE CONTROL SYSTEM

Code Commit

</>

CD Pipelines

CD as a Service

Turnkey Provisioning

Self-Service Jenkins

Project Team Jenkins Admin

Shared Services Manager

Agent Agent

Agent Agent

Agent Agent

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

41

CD and DevOps @Scale with Jenkins 2 and CloudBees

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

42

Jenkins 2 and CloudBees Jenkins Plarform Features

Jenkins 2

+

❖  User Management w/Role-Based Access Controls

❖  Managed Masters w/High Availability

❖  Build and Performance Analytics

❖  VM and Cloud Native support

★  Continuous Delivery

★  Pipeline-as-Code

★  Stage View

★  Improved UI

+

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

43

•  Where did/would you start with your DevOps transformation?:

1.  Culture

2.  Process

3.  Tools and Technology

4.  None of the Above

Poll Question #3

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

44

•  Part 1: Introduction to the 4 Quadrants of DevOps Maturity

–  May 4th, 2016 - Watch at: https://goo.gl/9KsAvt

•  Part 2: Mapping and Measuring Your Journey to DevOps

–  June 1st, 2016 – Watch at: https://goo.gl/1K7Ngq

•  Part 3: Crossing the DevOps Chasms with Tools & Technology

–  July 7th, 2016 – Watch at: https://goo.gl/0VQRWD

•  Follow-up and implementation tools

–  White paper

–  Maturity calculator

–  Contact CloudBees for Assistance: Products, Support, Services, and Partners

Next …

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

45 45

Questions?

DM: @brianvdawson Email: [email protected] Or: [email protected]

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

46

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

46

Thank You

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

47

© 2

016

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d