DEVOPS For PHP Developers

Slide 1

Slide 1 text

DEVOPS for PHP Developers https://www.ﬂickr.com/photos/inedito/2963474098 PHP UK Conference London 2015 - Jeremy Quinton

Slide 2

Slide 2 text

• Working on the web with PHP since 2003 • Some operations work • Open Source Enthusiast • Big Fan of DEVOPS cultural and professional movement About

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

Ideology The set of ideas and beliefs of a group… http://www.merriam-webster.com/dictionary/ideology

Slide 5

Slide 5 text

Complaints and Confusion https://www.ﬂickr.com/photos/jkfjellestad/15524719680

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

Ideas or set of Ideals (New and Old) Which has lead to a common set of practices and patterns DEVOPS (at a high level) Goal of my talk today is to share some of these ideas, practices and patterns

Slide 8

Slide 8 text

Common DEVOPS definition - CAMS Damon Edwards and John Willis • Culture • Automation • Measurement • Sharing

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

The 2014 State of DEVOPS Report The largest and most comprehensive DEVOPS study to date https://www.ﬂickr.com/photos/80497449@N04/10012162166 The first scientific study of the relationship between Organisational performance, IT performance, DEVOPS practices.

Slide 11

Slide 11 text

The state of DEVOPS 2014 - http://puppetlabs.com/sites/default/files/2014-state-of-devops-report.pdf • Strong IT performance is a competitive advantage • Strong correlation between DEVOPS practices and IT performance

Slide 12

Slide 12 text

http://en.wikipedia.org/wiki/Gene_Kim http://en.wikipedia.org/wiki/Gene_Kim#mediaviewer/File:Gene_Kim.jpg Gene Kim “The best just keep getting better and accelerating away from the herd.” Author of the Phoenix project A Novel About IT, DevOps, and Helping Your Business Win

Slide 13

Slide 13 text

“DEVOPS means [caring] about your job enough to not pass the buck. DEVOPS means [caring] about your job enough to want to learn all the parts and not just your little world. ! Developers need to understand infrastructure. Operations people need to understand code. People need to work with each other and not just occupy space next to each other.” –- John E. Vincent ! https://twitter.com/lusis

Slide 14

Slide 14 text

Developer Mindset • How are we going to deploy our code? • How are we going to monitor the application in a production environment? • Is this code going to work in a multi node environment?   e.g. sessions, caching etc • Software is a thing that exists after it has been written

Slide 15

Slide 15 text

Break down the silos. But why? https://www.ﬂickr.com/photos/docsearls/5500714140

Slide 16

Slide 16 text

Development Developers QA Testers Operations Sys Admins Network Engineers DBA Development teams strive for change Operations teams strive for stability misalignment leads to conflict Measured on things like features Measured on things like uptime

Slide 17

Slide 17 text

• Ideally no isolated silos exist in the software delivery process. Breaking Down the Silos

Slide 18

Slide 18 text

IF WE COULD JUST CREATE A DEVOPS TEAM THAT WOULD BE GREAT

Slide 19

Slide 19 text

• DEVOPS proposes, instead, strategies to create better collaboration between functional silos or doing away with functional silos altogether and creating cross functional teams. better • DEVOPS movement addresses the dysfunction that results from organisations composed of functional silos. Breaking Down the Silos • DEVOPS proposes shared responsibilities and incentives across teams.

Slide 20

Slide 20 text

DEVOPS is Cultural shift https://www.ﬂickr.com/photos/philliecasablanca/3344142642

Slide 21

Slide 21 text

“Organisational culture is the behaviour of humans within an organisation and the meaning that people attach to those behaviours.” DEVOPS is Cultural shift

Slide 22

Slide 22 text

- http://puppetlabs.com/sites/default/files/2014-state-of-devops-report.pdf The state of DEVOPS 2014 Typology of Organisational Culture (Westrum, 2004) Pathological Power-oriented Bureaucratic Rule-oriented Generative Performance-oriented

Slide 23

Slide 23 text

Pathological - Power-oriented

Slide 24

Slide 24 text

Bureaucratic Rule-oriented https://www.ﬂickr.com/photos/unsureshot/268754069

Slide 25

Slide 25 text

Generative - Performance-oriented https://www.flickr.com/photos/gfreeman23/8732672635

Slide 26

Slide 26 text

DEVOPS identifies that organisational culture is important and that this culture is crucial to whether or not DEVOPS will succeed within any given organisation. Takeaway

Slide 27

Slide 27 text

Increasing collaboration between dev and ops “What is remarkable is that even though agile actively seeks collaboration from all its stakeholders, most agile projects did not extend themselves toward the operations people.” ! ! - Patrick Debois.

Slide 28

Slide 28 text

Agile Development Team Waterfall Operations Team Increasing collaboration between dev and ops Scrumfall

Slide 29

Slide 29 text

Change your definition of done “At the end of each sprint, we must have working and shippable code…” ! “demonstrated in an environment that resembles production”

Slide 30

Slide 30 text

Practices • Make environments available early in the development process. https://www.vagrantup.com Development environments made easy. Create and configure lightweight, reproducible, and portable development environments. Build, Ship and Run Any App, Anywhere ! Docker - An open platform for distributed applications for developers and sysadmins. OR

Slide 31

Slide 31 text

Chef Puppet Ansible Salt Configuration management tools (Infrastructure as code) • These tools enable more transparency at the infrastructure level. • Also get developers and operations people collaborating early in the software delivery process Amazon Rackspace Digital Ocean Cloud providers Practices • Make sure devs and ops build code and environments at the same time.

Slide 32

Slide 32 text

Packer is a tool for creating identical machine images for multiple platforms from a single source configuration. Packer https://www.packer.io • Create a common dev,qa, production environment creation process. Practices

Slide 33

Slide 33 text

• Collaboration between development and operations starts long before the deployment of software and well afterwards. Practices • Get Operations and Developers sitting together.

Slide 34

Slide 34 text

Cycle Time • How long does it take you to go from code committed to getting that code running in production? • Asked in another way if you had a critical bug fix and it was one line of code how long does it take you to get that to production.

Slide 35

Slide 35 text

“What businesses really want of us as software developers is that we allow them to have an idea, get the idea into the hands of our users, figure out if the idea works, and react to the understanding that we can gain from this experiment.” Cycle Time https://leanpub.com/buildqualityin

Slide 36

Slide 36 text

“High performing organisations deploy code 30 times more often, and 8000 times faster than their peers, deploying multiple times a day, versus an average of once a month.” Key Finding - DEVOPS 2013 Report “Have 50% fewer failures and restore service 12 times faster than their peers.” https://puppetlabs.com/wp-content/uploads/2013/03/2013-state-of-devops-report.pdf

Slide 37

Slide 37 text

Some problems dev and ops teams face • Cycle time is measured in weeks or months. release • Problems with deployment. • Various bottle necks. Key goals of DEVOPS is to increase ﬂow, reduce cycle time,  shorten the feedback loop.

Slide 38

Slide 38 text

Continuous Delivery Read this Book

Slide 39

Slide 39 text

Continuous Delivery Design practice used in software development to automate and improve the process of software delivery. Techniques such as automated testing, continuous integration and continuous deployment Allow software to be developed to a high standard and easily packaged and deployed to environments, resulting in the ability to rapidly, reliably and repeatedly push out enhancements and bug ﬁxes to customers at low risk and with minimal manual overhead. http://en.wikipedia.org/wiki/Continuous_delivery

Slide 40

Slide 40 text

Key Goals of Continuous Delivery • Software is always in a releasable state throughout its lifecycle. • The only way to categorically prove software is production ready is to deploy it production.

Slide 41

Slide 41 text

Devops for developers - Michael Heuttermann Available functionality Time Big releases Small releases

Slide 42

Slide 42 text

Benefits of deploying more frequently • Smaller changes make it easier to identify problems • Risk of deployment is reduced • The process of fixing problems becomes optimised Devops for developers - Michael Heuttermann

Slide 43

Slide 43 text

Deployment becomes a non event

Slide 44

Slide 44 text

Continuous Integration • Create quality at the source - helps build trust • Fix broken builds immediately - don’t block other developers • Keep your builds fast - get feedback sooner

Slide 45

Slide 45 text

Automated Acceptance Testing https://www.ﬂickr.com/photos/wynandvanpoortvliet/3562677155

Slide 46

Slide 46 text

Automated acceptance testing “Automated testing turns fear into boredom” - Eran messeri google. • Automated acceptance testing of functional and non functional requirements. • RSpec tests for your servers configured by Puppet, Chef or anything else. https://github.com/serverspec/serverspec

Slide 47

Slide 47 text

A deployment pipeline is automated implementation of your applications build, deploy, test and release process. Deployment pipeline

Slide 48

Slide 48 text

Deployment pipeline Delivery Team Version Control Check in Feedback Build & unit tests Trigger Automated Acceptance Tests Trigger Feedback Release Approval

Slide 49

Slide 49 text

• Collaboration • Feedback • Teams can deploy and release any version of their software to any environment at will through a fully automated process. Key objectives of Deployment pipeline - Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation by Jez Humble and David Farley

Slide 50

Slide 50 text

Tools available to build deployment pipelines Travis CI Jenkins Testing tools PHPunit phpspec Behat BAMBOO Code Standard Quality Tools Continous Integration Servers Phing Build Tools PHP CodeSniffer - https://github.com/squizlabs/PHP_CodeSniffer PHP Mess detector http://phpmd.org/ PHPLoc - https://github.com/sebastianbergmann/phploc PHPCI Codeception PHP Documentor -http://www.phpdoc.org/

Slide 51

Slide 51 text

Automated Deployments Think of deployment as a two step process • Select environment where we want our software to go. • Push a button to release the software to that environment. Tools Capistrano Rocketeer Deployer - Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation by Jez Humble and David Farley

Slide 52

Slide 52 text

Measurement

Slide 53

Slide 53 text

Monitoring • If you are releasing often you want fast feedback. • Adding monitoring to the definition of done for new software features.

Slide 54

Slide 54 text

Measurement • You can’t improve what you can’t measure. • Measurements are shared not only between developers and ops people   but with the entire organisation.

Slide 55

Slide 55 text

Tools Statsd Logstash + ElasticSearch + Kibana Log ﬁles from production - Measurement and monitoring Collectd Graphite Grafana Cacti Monitoring and Altering Nagios Sensu Ganglia Sentry Graylog Application Metrics Splunk

Slide 56

Slide 56 text

Sharing with operations https://www.ﬂickr.com/photos/clappstar/2773208127 Sharing

Slide 57

Slide 57 text

Sharing - Pain • Developers take more ownership and responsibility for their code. • Developers on call for production issues.

Slide 58

Slide 58 text

Blameless post mortems Blameless Post Mortems

Slide 59

Slide 59 text

Everything is in source control https://twitter.com/jclermont/status/557202948703666177

Slide 60

Slide 60 text

• Code and scripts for building the application. Things that should be in version control for your application • Code and scripts for testing the application. • Code and scripts for deploying the application. • Code and scripts for building environments for the application.

Slide 61

Slide 61 text

Summary • Why we need DEVOPS • Breaking down Silos • Organisational culture • Increasing Collaboration between Developers and Operations • Cycle Time and Continuous Delivery • Measurement and monitoring • Sharing

Slide 62

Slide 62 text

Patrick Debois https://twitter.com/patrickdebois/status/539073067738468352

Slide 63

Slide 63 text

Feedback https://joind.in/talk/view/13368

Slide 64

Slide 64 text

Good DEVOPS Resources https://leanpub.com/buildqualityin Attend a DEVOPS day conference http://www.devopsdays.org/ http://foodfightshow.org/ Podcasts http://devopscafe.org/ http://amzn.to/1vD8gUi http://amzn.to/1zMaAc7 http://amzn.to/1AiZMpy http://amzn.to/1brnEZI

Slide 65

Slide 65 text

Questions?