Embed Size (px)
Citation preview
Agenda
1. Introduction2. What is DevOps?3. What is Continuous Delivery?4. Theories behind DevOps5. Why DevOps?6. The ING Lease IT story
About you
1. Who are you, what company do you work for?2. What is your talent?3. DevOps to me is…
About me
• 1997 Bachelor in teaching• 1997 Tester• 2001 My first Agile project• 2004 Joined Ordina• 2008 Thoughtleader Agile Testing & Author of ‘Testen2.0’• 2012 Thoughtleader Agile• 2013 DevOps PM & trainer Management 3.0• 2014 Agile & DevOps coach, trainer, consultant• 2016 Selfemployed @ The Future Group
1. Introduction
Goals
• Uncovering what DevOps is• Theories behind DevOps• Why should an organization implement DevOps?• Understand how DevOps works in practice
Note: DevOps is fairly new and under heavy construction
Rightshifting – Bob Marshall
Where we are: Where we want to go:
Rightshifting – Bob Marshall
• Ad hoc: no process or organization, focus on ‘as is’, people relations – “Customer of the week”
• Analytical: Focus on processes and tasks, up front structuring– CMMI, PRINCE2, ITIL, BiSL,Six Sigma, …
• Synergetic: Focus on collaboration, value creation– Agile, Scrum, DevOps, Lean, …– “None of us is as smart as all of us” - Gerald M. Weinberg
• Chaordic: Innovation mindset, no formal organization, feedback use– Google Friday, Lean Start Up– Dee Hock (‘Chaordic’): ‘Simple rules and regulations give rise to
complex, intelligent behavior. Complex rules and regulations give rise to simple, stupid behavior”
Rightshifting – Bob Marshall
#ohno
2. What is DevOps?
Hi, I’m Dev!
Hi, I’m Ops!
Agile voor Managers
What is DevOps?
2. What is DevOps?Definitions
Wikipedia (renew
ed):
DevOps is a culture, movement or practice that emphasizes the collaboration and
communication of both software developers and other IT-professionals while automating
the process of software delivery and infrastructure changes.[1][2] It aims at establishing a
culture and environment where building, testing, and releasing software, can happen
rapidly, frequently, and more reliably.[3][4][5]
DevOps is “a cross-disciplinary community of
practice dedicated to the study of building,
evolving and operating rapidly-changing
resilient systems at scale.” – Jez Humble
…with the ultimate goal to proactively support
the organization in becoming digital, client-
focused and data-driven enterprises. – Anko
Tijman
2. What is DevOps?
2. What is DevOps?#1 DevOps is automation
Automation
Automation of repetitive tasks:• Deployments• Testing• Monitoring• Operations
• Infrastructure as code• Continuous Integration & Delivery• Continous Deployment• Monitoring
2. What is DevOps?#1 DevOps is automation
2. What is DevOps?DevOps automation practices
Just a few • A/B testing• Automated dashboards• Big visible dashboards• Blue-green deployment• Composable deployments• Consistent tooling• Cross-functional skills• Dark launching• Deployment pipeline• Develop for production• Feature toggles• Feedback from production
• Integrated deployment planning• Integrate production stories• Packaged artifact• Polyskilled experts• Production support• Scripted deployments• Stop the line (Lean)• Test-driven everything• Version everything• …
2. What is DevOps?#2 Devops is collaboration
Collaboration
• Cross functional teams– Dev and Ops and all of their roles – Analyst, Developer, Tester, Application mgr, Sys Admin, Infra, etc.– Projects AND Changes AND Incidents in one team– BizDevOps?!
• Team goals– Team metrics– Learning as a team– Continous improvement (people, process, technology)
• Joint tooling– Process– Deployments– Monitoring
2. What is DevOps?#2 Devops is collaboration
Learning from production
2. What is DevOps?#3 Learning from production
2. What is DevOps?#3 Learning from production
• Feedback from production– Business value: Users, conversion, etc.– Technical excellence: CPU, logging, etc.– Feature feedback– Product Backlog continuous improvement
• Continuous improvement– System– Process – Team– Stakeholders
• Impact on Design and Architecture– Emerging design– Emerging architecture– Built to last built to change
Exercise
Visualizations Why should an organization
implement DevOps? What is the impact of DevOps
on organizations?
Agile voor Managers
3. Continuous Delivery
3. Continuous DeliverySomething like this…
3. Continuous DeliveryWhy?
You’re in a thrilling environment
You want to learn fast
You want to be in control
3. Continuous DeliveryCI, CD, DevOps
3. Continuous DeliveryIn just over 5 minutes
3. Continuous DeliveryDevOps tools overview
Databases• MySQL• MSSQL• PostgreSQL• MangoDB• DB2• Cassandra• …
SCM configuratie mgt• Git• Subversion• Mercurial• Github• Bitbucket• Helix• …
Build• Maven• Buildr• Quickbuild• MSBuild• Gradic• ANT• …
• UrbanCodeBuild• Rake• Meister• BuildMaster• VisualBuild• Luntbuild
Titel
Continuous• Jenkins• Codeship• Teamcity• Continuum• Bamboo• Gump• …
Integration• Snap CI• Shippable • Continuous CI• Travis CI• Circle CI• CruiseControl
Repository Mgt• Archiva• Nexus• Artifactory• NuGet
Testing• FitNesse• Cucumber• JUnit• Selenium• Selenide• Cucumber.js• Appium
• JMeter• XL TestView• Gatling• QUnit• TestNG• TestComplete• …
Titel
Deployment• SSH• Deployment
manager• Capistrano• RapidDeploy• Go• Smartfrog• UrbanCode
• Juju• CodeDeploy• ElectricFlow• Rundeck• Octopus• XL Deploy• CA Nollo
Config / • Chef• Puppet• BladeLogic• Ansible• Vagrant
Provisioning• Cobbler• Salt• Terraform• Bcfg2• CFEngine
Containerization• Docker• Rocket• Kubernetes• Packer• ElasticBox• Mesos
Titel
Cloud• AWS• Azure• Heroku• Rackspace• Bluemix• Apprenda• Open Stack• Cloud Foundry
Release management• XLRelease• UrbanCode Release• CA Service Virtual.• BMC Release process• HP Codar• Excel• Plutora Release• Serena Release
BI/Monitoring• Splunk• Kibana• New Relic• Ganglia• XL Testview• Cacti• Graphite• Icinga
Logging• Sumo Logic• Logstash• Loggly• Greylog
3. Continuous DeliveryBusiness risk when CD
Lamborghini GallardoV10 engine, 500 bhpTopspeed 309 km/h
0 – 100 km/h: 4.2 secCO2 400 g/km
Agile voor Managers
4. Theories behind DevOps
4. Theories behind DevOpsPatrick Debois
• Founder of the DevOps movement• DevOpsDays 2009, Ghent (B)• Jedi.be
4. Theories behind DevOpsJez Humble, Damon Edwards
• Culture: Own the change to drive collaboration and communication
• Automation: Take manual steps out of your value chain
• Lean: Use lean principles to enable higher cycle frequency
• Measurement: Measure everything and use data to refine cycles
• Sharing: Share experiences, successful or not, to enable others to learn
CALMS…http://www.rackspace.com/blog/quantifying-devops-capability-its-important-to-keep-calms/
4. Theories behind DevOpsCALMS - Culture
4. Theories behind DevOpsAvoid local pain
Where we are:
4. Theories behind DevOpsThree ways
1. The First Way : Systems Thinking emphasizes the performance of the entire system
2. The Second Way is about creating and amplifying the right to left feedback loops
3. The Third Way is about creating a culture that fosters both continual experimentation, taking risks and learning from failure; and understanding that repetition and practice is the prerequisite to mastery.
1.
2.
3.
4. Theories behind DevOpsTheory of Constraints (ToC)
A focusing process to identify the constraint and restructure the rest of the organization around it.• Production lines• A company is a system• Gathering, analyzing, solving, and implementing (management)
problems• There is always a biggest constraint
– Continuous Improvement!
4. Theories behind DevOpsToC & DevOps
• Why aren’t we deploying more often?• Why do deployments take so long?• Why is releasing our software such a
hassle?• …• Book: The Phoenix Project
Agile voor Managers
5. Where is DevOps bringing us
5. Where is DevOps bringing us?Automation
1. Seamless deployments Automation, automation, automation No process hassle Recoverability Monitoring & Measuring
5. Where is DevOps bringing usCollaboration
2. Collaboration accomplished Cross functional teams Competence driven T-shaped people Joint goals, joint metrics, joint performance
5. Where is DevOps bringing usLearning
3. Continuous learning provided Based on facts Feedback loops throughout the organization Teams that own business processes Cross departments
Auditors: please audit THIS!
5. Where is DevOps bringing usTransformations in the organization
1. From analog to digital
Automation
5. Where is DevOps bringing usTransformations in the organization
2. From internal focus to client driven
Collaboration
5. Where is DevOps bringing usTransformations in the organization
3. From opinion to data driven
Learning from production
DevOps is:
Where we are:AutomationCollaboration
Learning from production
Contact
@AnkoTijman06-52053470
CoachingTraining
Presentaties
