development doesn't stop at the last commit

46
Software development Software development does NOT stop at the does NOT stop at the last commit last commit Kris Buytaert Open World Forum 2013, Paris @krisbuytaert

Upload: kris-buytaert

Post on 06-May-2015

2.461 views

Category:

Business


0 download

DESCRIPTION

A gentle introduction to devops as presented at Open World Forum 2013 , Paris

TRANSCRIPT

Page 1: Development Doesn't Stop at the Last Commit

Software development Software development does NOT stop at the does NOT stop at the

last commitlast commitKris Buytaert

Open World Forum 2013, Paris

@krisbuytaert

Page 2: Development Doesn't Stop at the Last Commit

Kris BuytaertKris Buytaert● I used to be a Dev,I used to be a Dev,● Then Became an OpThen Became an Op● Chief Trolling Officer and Open Source Chief Trolling Officer and Open Source

Consultant @inuits.euConsultant @inuits.eu● Everything is an effing DNS ProblemEverything is an effing DNS Problem● Building Clouds since before the bookstoreBuilding Clouds since before the bookstore● Some books, some papers, some blogsSome books, some papers, some blogs● Evangelizing devopsEvangelizing devops

Page 3: Development Doesn't Stop at the Last Commit

What's this devops thing What's this devops thing anyhow ? anyhow ?

Page 4: Development Doesn't Stop at the Last Commit

World , 200X-2009World , 200X-2009

Patrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, Jezz Patrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, Jezz Humble, Lindsay Holmwood, John Willis, Chris Read, Julian Simpson, Luke Humble, Lindsay Holmwood, John Willis, Chris Read, Julian Simpson, Luke

Kanies, John Allspaw and lots of others ..Kanies, John Allspaw and lots of others ..

Gent , October 2009Gent , October 2009

Mountain View , June 2010Mountain View , June 2010

Hamburg , October 2010Hamburg , October 2010

Boston, March 2011Boston, March 2011

Mountain View, June 2011Mountain View, June 2011

Bangalore, Melbourne, Bangalore, Melbourne,

Goteborg , October 2011Goteborg , October 2011

........

Almost 20 events held in 2013.Almost 20 events held in 2013.

Page 5: Development Doesn't Stop at the Last Commit

devops, a definition:devops, a definition:

Page 6: Development Doesn't Stop at the Last Commit

● Adopt the new philosophy. We are in a new economic age. Western management Adopt the new philosophy. We are in a new economic age. Western management must awaken to the challenge, must learn their responsibilities, and take on must awaken to the challenge, must learn their responsibilities, and take on leadership for change.leadership for change.

● Cease dependence on inspection to achieve quality. Eliminate the need for massive Cease dependence on inspection to achieve quality. Eliminate the need for massive inspection by building quality into the product in the first place.inspection by building quality into the product in the first place.

● Improve constantly and forever the system of production and service, to improve Improve constantly and forever the system of production and service, to improve quality and productivity, and thus constantly decrease costs.quality and productivity, and thus constantly decrease costs.

● Institute training on the job.Institute training on the job.● Institute leadership The aim of supervision should be to help people and machines Institute leadership The aim of supervision should be to help people and machines

and gadgets do a better job. and gadgets do a better job. ● Drive out fear, so that everyone may work effectively for the company. Drive out fear, so that everyone may work effectively for the company. ● Break down barriers between departments. People in research, design, sales, and Break down barriers between departments. People in research, design, sales, and

production must work as a team, in order to foresee problems of production and production must work as a team, in order to foresee problems of production and usage that may be encountered with the product or service.usage that may be encountered with the product or service.

● Eliminate slogans, exhortations, and targets for the work force asking for zero defects Eliminate slogans, exhortations, and targets for the work force asking for zero defects and new levels of productivity. Such exhortations only create adversarial and new levels of productivity. Such exhortations only create adversarial relationships, as the bulk of the causes of low quality and low productivity belong to relationships, as the bulk of the causes of low quality and low productivity belong to the system and thus lie beyond the power of the work force.the system and thus lie beyond the power of the work force.

● Eliminate management by objective. Eliminate management by numbers Eliminate management by objective. Eliminate management by numbers and numerical goals. Instead substitute with leadership.and numerical goals. Instead substitute with leadership.

● Remove barriers that rob the hourly worker of his right to pride of Remove barriers that rob the hourly worker of his right to pride of workmanship. The responsibility of supervisors must be changed from workmanship. The responsibility of supervisors must be changed from sheer numbers to quality.sheer numbers to quality.

● Remove barriers that rob people in management and in engineering of Remove barriers that rob people in management and in engineering of their right to pride of workmanship. their right to pride of workmanship.

● Institute a vigorous program of education and self-improvement.Institute a vigorous program of education and self-improvement.● Put everybody in the company to work to accomplish the transformation. The Put everybody in the company to work to accomplish the transformation. The

transformation is everybody's job.transformation is everybody's job.

Page 7: Development Doesn't Stop at the Last Commit

William Edwards William Edwards Deming Deming

1986, Out of the Crisis. 1986, Out of the Crisis.

http://en.wikipedia.org/wiki/W._Edwards_Deminghttp://en.wikipedia.org/wiki/W._Edwards_Deming

Page 8: Development Doesn't Stop at the Last Commit

Devops is a cultural and Devops is a cultural and professional movementprofessional movement

Adam Jacob, OpscodeAdam Jacob, Opscode

Page 9: Development Doesn't Stop at the Last Commit

C(L)AMSC(L)AMS● CultureCulture

● (Lean)(Lean)

● AutomationAutomation

● MeasurementMeasurement

● SharingSharing

Damon Edwards and John WillisDamon Edwards and John Willis

Gene KimGene Kim

Page 10: Development Doesn't Stop at the Last Commit

Whats in it for you ?Whats in it for you ?● Faster time to marketFaster time to market

• Features go live in hours vs yearsFeatures go live in hours vs years

● In a more safeIn a more safe

● Reliable fashionReliable fashion

• Fully automatedFully automated

● More happy More happy {customers,developers,managers,investors}{customers,developers,managers,investors}

Page 11: Development Doesn't Stop at the Last Commit

A typical dev shopA typical dev shop● The PM:The PM:

•““Put this Code Live, here's a tarball” NOW! Put this Code Live, here's a tarball” NOW!

•Marketing Campain is launched Marketing Campain is launched

•We need this yesterday We need this yesterday

•It's going on national radio at 5It's going on national radio at 5

Page 12: Development Doesn't Stop at the Last Commit

An oldschool ops shopAn oldschool ops shop● What dependencies ?What dependencies ?

● No machines available ?No machines available ?

● What database ?What database ?

● Security ?Security ?

● High Availability ? High Availability ?

● Scalability ?Scalability ?

● My computer can't install this ?My computer can't install this ?

Page 13: Development Doesn't Stop at the Last Commit

Devs vs OpsDevs vs Ops

Page 14: Development Doesn't Stop at the Last Commit

Culture,Culture,automation, automation,

Measturement,Measturement,

sharingsharing

Page 15: Development Doesn't Stop at the Last Commit

Burn the Silos Burn the Silos

Page 16: Development Doesn't Stop at the Last Commit

Crossfunctional TeamCrossfunctional Team● Project team with skills from all overProject team with skills from all over

• DevelopmentDevelopment

• Continuous Integration Continuous Integration

• TestingTesting

• Infrastructure (HA/ Scale/ Performance)Infrastructure (HA/ Scale/ Performance)

• DeploymentDeployment

• MeasurementMeasurement

● Seat them together !Seat them together !

● Goal = Help the businessGoal = Help the business

Page 17: Development Doesn't Stop at the Last Commit

One Team = One Goal !One Team = One Goal !

Page 18: Development Doesn't Stop at the Last Commit

Enable CommunicationEnable Communication

Page 19: Development Doesn't Stop at the Last Commit

Build TrustBuild Trust● ExperimentExperiment

• DevDev

• TestTest

● ProdProd

● Automate all the Automate all the thingsthings

● Measure successMeasure success

● Measure FailureMeasure Failure

Page 20: Development Doesn't Stop at the Last Commit

Lets Play TogetherLets Play Together

Getting AlongGetting AlongOpsOpsDevs Devs

Page 21: Development Doesn't Stop at the Last Commit
Page 22: Development Doesn't Stop at the Last Commit

Agile ?Agile ?● Agile vs AgileAgile vs Agile

● Scrum vs KanbanScrum vs Kanban

● Definition of Done Definition of Done

• Done means testedDone means tested

• Done means in production Done means in production

• Done means monitored and in productionDone means monitored and in production

Page 23: Development Doesn't Stop at the Last Commit

A software project is not done until A software project is not done until

your last enduser is in his grave ! your last enduser is in his grave !

Kris Buytaert, DOD Amsterdam 2013Kris Buytaert, DOD Amsterdam 2013

Page 24: Development Doesn't Stop at the Last Commit

Culture, Culture,

Automation,Automation,Measurement,Measurement,

SharingSharing

Page 25: Development Doesn't Stop at the Last Commit

Automate all the thingsAutomate all the things● BuildBuild

• reproducable builds are undiscussablereproducable builds are undiscussable

● TestTest

• testing reduces risk testing reduces risk

• automate deployments of your test infra automate deployments of your test infra

● DeployDeploy

• Infrastructure as CodeInfrastructure as Code

• 100% automation 100% automation

• Can you rebuild your infrastructure ?Can you rebuild your infrastructure ?

Page 26: Development Doesn't Stop at the Last Commit

Continuous IntegrationContinuous Integration

● Builds Builds

● Nightly Builds Nightly Builds

● Builds with tests Builds with tests

● Nightly Builds with tests Nightly Builds with tests

● Frequent integration Frequent integration

● Continuous Integration Continuous Integration

Page 27: Development Doesn't Stop at the Last Commit

Test AutomationTest Automation● Unit testsUnit tests

● Regression testsRegression tests

● SeleniumSelenium

● Cucumber Cucumber

● TDDTDD

● BDDBDD

Page 28: Development Doesn't Stop at the Last Commit
Page 29: Development Doesn't Stop at the Last Commit

devops (<)> continuous delilvery devops (<)> continuous delilvery

Page 30: Development Doesn't Stop at the Last Commit

" Our job as engineers (and ops, dev-ops, QA, " Our job as engineers (and ops, dev-ops, QA, support, everyone in the company actually) is to support, everyone in the company actually) is to enable the business goals. We strongly feel that enable the business goals. We strongly feel that in order to do that you must have in order to do that you must have the ability to the ability to deploy code quickly and safelydeploy code quickly and safely. Even if the . Even if the business goals are to deploy strongly QA’d code business goals are to deploy strongly QA’d code once a month at 3am (it’s not for us, we push all once a month at 3am (it’s not for us, we push all the time), having a reliable and easy the time), having a reliable and easy deployment should be deployment should be non-negotiablenon-negotiable." ."

Etsy Blog upon releasing DeployinatorEtsy Blog upon releasing Deployinator

http://codeascraft.etsy.com/2010/05/20/quantum-of-deployment/http://codeascraft.etsy.com/2010/05/20/quantum-of-deployment/

Page 31: Development Doesn't Stop at the Last Commit

Infrastructure as CodeInfrastructure as Code● Treat configuration automation as code Treat configuration automation as code

● Development best practicesDevelopment best practices

• Model your infrastructureModel your infrastructure

• Version your cookbooks / manifestsVersion your cookbooks / manifests

• Test your cookbooks/ manifestsTest your cookbooks/ manifests

• Dev/ test /uat / prod for your infraDev/ test /uat / prod for your infra

● Model your infrastructureModel your infrastructure

● A working service = automated ( Application Code + A working service = automated ( Application Code + Infrastructure Code + Security + Monitoring )Infrastructure Code + Security + Monitoring )

● Think Puppet, Chef, Cfengine, ...Think Puppet, Chef, Cfengine, ...

● IAC -ne scriptingIAC -ne scripting

Page 32: Development Doesn't Stop at the Last Commit

OrchestrationOrchestration● On what servers is XYZ running ? On what servers is XYZ running ?

● Restart apache on all servers with fact X Restart apache on all servers with fact X

● Configure DB Configure DB

• then configure web then configure web

• then restart app then restart app

Over different hosts , automated Over different hosts , automated

● Mcollective, Rundeck, Ansible ...Mcollective, Rundeck, Ansible ...

Page 33: Development Doesn't Stop at the Last Commit

Culture, Culture,

Automation,Automation,

Measurement :Measurement :

measure all the thingsmeasure all the thingsSharingSharing

Page 34: Development Doesn't Stop at the Last Commit
Page 35: Development Doesn't Stop at the Last Commit

Self Service MetricsSelf Service Metrics

● Being able to add new metrics Being able to add new metrics

● Build your own dashboardsBuild your own dashboards

● Look at metrics / logs on all platformsLook at metrics / logs on all platforms

● Learn from the LogfilesLearn from the Logfiles

● Learn from the platformLearn from the platform

Page 36: Development Doesn't Stop at the Last Commit

During developmentDuring development

Page 37: Development Doesn't Stop at the Last Commit

And runtimeAnd runtimeOperating SystemOperating System● diskdisk

● CpuCpu

● MemoryMemory

ApplicationApplication● #users#users

● #feature usage#feature usage

● response timeresponse timeMiddleWareMiddleWare● TransactionsTransactions

● Queue lengthQueue length

● Api calls Api calls

● (Aborted) Connections(Aborted) Connections

Page 38: Development Doesn't Stop at the Last Commit
Page 39: Development Doesn't Stop at the Last Commit

Math 101Math 101

● f(x)f(x)

● f'(x)f'(x)

● f''(x)f''(x)

● ... statistics 101... statistics 101

● Machine LearningMachine Learning

Page 40: Development Doesn't Stop at the Last Commit

Culture, Culture,

Automation, Automation,

Measurement,Measurement,

SharingSharing

Page 41: Development Doesn't Stop at the Last Commit

DashboardsDashboards

Page 42: Development Doesn't Stop at the Last Commit

Visualize Business MetricsVisualize Business Metrics● $revenue$revenue

● #sales#sales

● signups signups

● conversionsconversions

● Api callsApi calls

● Application useApplication use

Page 43: Development Doesn't Stop at the Last Commit

SharingSharing● Open SourceOpen Source

● Talk about ExperiencesTalk about Experiences

● Publish the codePublish the code

● No proprietary software was used in these No proprietary software was used in these slidesslides

Don't get Locked In !Don't get Locked In !

Page 44: Development Doesn't Stop at the Last Commit

FoodFood

Page 45: Development Doesn't Stop at the Last Commit

It's not about the toolsIt's not about the tools

Page 46: Development Doesn't Stop at the Last Commit

ContactContactKris Buytaert Kris Buytaert [email protected]@inuits.be

Further ReadingFurther Reading@krisbuytaert @krisbuytaert http://www.krisbuytaert.be/bhttp://www.krisbuytaert.be/blog/log/http://www.inuits.be/http://www.inuits.be/

InuitsInuits

Duboistraat 50Duboistraat 502060 Antwerpen2060 AntwerpenBelgiumBelgium891.514.231891.514.231

+32 475 961221+32 475 961221