1.
DevOps: Its not tools, StupidDavid Nalleyke4qqq@apache.org@ke4qqq

2.
# whoami● Recovering Sysadmin● Member of the Apache Software Foundation● Committer/PMC member Apache CloudStack● Fedora Project contributor● Open Source Business Office @ Citrix

3.
The DevOps Landscape● DevOps – term originated in 2009● Buzzword status soon followed● Now we have DevOps-washing

4.
DevOpsDays● 1 in 2009● 4 in 2010● 6 in 2011● 6 in 2012● 15 on the books for 2013

5.
Job titles● 50% increase in DevOps skill listing onLinkedIn profiles between 2011 and 2012.● 75% increase in DevOps skill listing in job reqshttp://info.puppetlabs.com/2013-state-of-devops-report

6.
Tools● Chef/Puppet● Jenkins● Travis-CI●

7.
The problem with tools..● Dont imply that you have skill● Doesnt solve the problems DevOps addresses● Far too often see as a substitute● Lots of people trying to sell you tools● Tools are still indispensable

8.
Teams● No such thing as a DevOps Team● You cant silo your DevOps efforts●

9.
DevOps isnt...● A Job Title● A tool● Something you can get from a vendor● A team● Easy

10.
So what is DevOps?● Adopt the new philosophy. We are in a new economic age. Western management must awaken to thechallenge, must learn their responsibilities, and take on leadership for change.● Cease dependence on inspection to achieve quality. Eliminate the need for massive inspection bybuilding quality into the product in the fi rst place.● Improve constantly and forever the system of production and service, to improve quality and productivity,and thus constantly decrease costs.● Institute training on the job.● Institute leadership The aim of supervision should be to help people and machines and gadgets do abetter job.● Drive out fear, so that everyone may work effectively for the company.● Break down barriers between departments. People in research, design, sales, and production must workas a team, in order to foresee problems of production and usage that may be encountered with theproduct or service.● Eliminate slogans, exhortations, and targets for the work force asking for zero defects and new levels ofproductivity. Such exhortations only create adversarial relationships, as the bulk of the causes of lowquality and low productivity belong to the system and thus lie beyond the power of the work force..● Eliminate management by objective. Eliminate management by numbers and numericalgoals. Instead substitute with leadership.● Remove barriers that rob the hourly worker of his right to pride of workmanship. Theresponsibility of supervisors must be changed from sheer numbers to quality.● Remove barriers that rob people in management and in engineering of their right to prideof workmanship. This means, inter alia, abolishment of the annual or merit rating and ofmanagement by objectives● Institute a vigorous program of education and self-improvement.● Put everybody in the company to work to accomplish the transformation. The transformation iseverybodys job.

11.
The Goal

12.
We arent special● Weve had a tendency to think of ourselves asspecial and unique because of technology● The reality is that because weve designatedourselves as special weve failed to takeadvantage of what others have learned beforeus.

13.
The future....if we adapt..

14.
Easier Definition● Culture● Automation● Measurement● Sharing

15.
Primarily – its cultural● Automation, Measurement, and Sharing dontmatter if you dont get culture right.● First focus is pulling down the walls betweendevelopers and operations. They cant continueto be silos.

16.
DevOps cultural battle is not wonovernight● Continuous, small, improvements. (Kaizen)● Forklift changes are often disruptive.

17.
Visit us atredhat.com/Connect