O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

Codifying Devops -The Devops Story

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Próximos SlideShares
Education
Education
Carregando em…3
×

Confira estes a seguir

1 de 78 Anúncio

Codifying Devops -The Devops Story

Baixar para ler offline

What is Devops ? This presentation talks about the story behind devops, key principles, practices and gives you a path to understand how to get started with devops.

What is Devops ? This presentation talks about the story behind devops, key principles, practices and gives you a path to understand how to get started with devops.

Anúncio
Anúncio

Mais Conteúdo rRelacionado

Diapositivos para si (20)

Semelhante a Codifying Devops -The Devops Story (20)

Anúncio

Mais recentes (20)

Codifying Devops -The Devops Story

  1. 1. CODIFYING DEVOPS GOURAV SHAH
  2. 2. CODIFYING DEVOPS WHY HOW AND WHAT OF DEVOPS
  3. 3. WHY?
  4. 4. Source : Devops Guide by IT Revolution Press
  5. 5. THE DEVOPS STORY EVOLUTION OF AGILE ORGANISATIONS
  6. 6. ASSEMBLY LINE HENRY FORD 1915
  7. 7. TOYOTA PRODUCTION SYSTEM Taiichi Ohno 1948 - 1975
  8. 8. RELENTLESSLY WORK ON ELIMINATING WASTE FROM THE MANUFACTURING PROCESS…. TPS TPS/LEAN PHILOSOPHY
  9. 9. 8 TYPES OF WASTES ▸ Over Production ▸ Waiting ▸ Inventory ▸ Transportation ▸ Over Processing ▸ Motion ▸ Defects ▸ Workforce
  10. 10. TOYOTA PRODUCTION SYSTEM Just In Time Production Kanban Value Stream Mapping
  11. 11. https://en.wikipedia.org/wiki/Value_stream_mapping Vaule Stream Mapping
  12. 12. LEAN PRODUCTION James P Womack 1990 LEAN IT
  13. 13. THEORY OF CONSTRAINT Eliyahu M Goldratt 1984
  14. 14. THEORY OF CONSTRAINT ▸ Identify System’s Constraints ▸ Exploit the Constraint ▸ Subordinate everything to above decision ▸ Elevate the Constraint ▸ Repeat the Process
  15. 15. EXTREME PROGRAMMING (XP) SCRUM KANBAN DYNAMIC SYSTEMS DEVELOPMENT METHOD (DSDM) LEAN FEATURE DRIVEN DEVELOPMENT (FDD) METHODS
  16. 16. 2001 AGILE MANIFESTO
  17. 17. ENGINEERING ITERATIVE INCREMENTAL EXTREME PROGRAMMING (XP) SCRUM KANBAN DYNAMIC SYSTEMS DEVELOPMENT METHOD (DSDM) LEAN FEATURE DRIVEN DEVELOPMENT (FDD) METHODS DEV QA SOFTWARE DEVELOPMENT
  18. 18. dev Ops
  19. 19. WALL
  20. 20. 2008 PATRICK DEBOIS AGILE CONFERENCE, TORONTO CANADA
  21. 21. AGILE SYSTEMS ADMINISTRATOR GROUP Patrick DeboisAndrew Clay Shafer
  22. 22. 2009. VELOCITY CONFERENCE John Allspaw Paul Hammond 10+ DEPLOYS A DAY , DEVOPS & OPS CO-OPERATION AT FLIKR
  23. 23. BUILDING TOOLS AND CULTURE TO BRIDGE THE GAP BETWEEN DEV AND OPS AUTOMATED INFRASTRUCTURE SHARED VERSION CONTROL ONE STEP BUILD AND DEPLOY SHARED METRICS FEATURE FLAGS IRC AND IM BOTS MUTUAL RESPECT TRUST HEALTHY ATTITUDE ABOUT FAILURE AVOIDING BLAME src: https://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr/76 Tools Culture
  24. 24. 2009
  25. 25. #devops
  26. 26. To achieve their business goals CHANGE to achieve competitive advantage to survive to respond to changing customer needs Organizations need to constantly
  27. 27. EACH OF THAT CHANGE TRANSLATES TO A DEFINING DEVOPS DEPLOYMENT
  28. 28. EACH OF THAT CHANGE INTRODUCES A DEFINING DEVOPS RISK
  29. 29. WHILE STILL ACHIEVING OFFERS A PATH TO REDUCE THE RISK DEVOPS RAPID CHANGE PRINCIPLES PRACTICES TOOLS IS A CULTURAL MOVEMENT WHICH
  30. 30. METRICS LEAD TIME TO CHANGE MEAN TIME TO RECOVER FREQUENCY OF DEPLOYMENTS CHANGE FAILURE RATES
  31. 31. Source : State of Devops Report 2016 by Puppet Labs
  32. 32. Pipeline Plan Code Test Release Deploy Operation Agile DEV OPS Devops DevOps Security
  33. 33. ORG TEAMS INDIVIDUALS
  34. 34. ORG Customer Centric Organisations Initiating Devops Culture Beliefe in Automation
  35. 35. Incorporate Ops Strategise Practices and Tools Architectural Chances TEAMS
  36. 36. Skills Focus on Automation INDIVIDUALS
  37. 37. PRINCIPLES
  38. 38. Systems Thinking Amplify Feedback Loops Continuous Improvement
  39. 39. Systems Thinking Look at the big picture Reduce Waste Elevate Bottlenecks Improve the Flow
  40. 40. Plan Code Pre Prod Prod Systems Thinking
  41. 41. Source – The DevOps Handbook Value Stream Mapping
  42. 42. IDENTIFY THE WASTE WASTE IN SOFTWARE DELIVERY ▸ Over Production: Running tests which need not be run. Component has no dependencies. Building features not useful for customers. ▸ Waiting : Dev and QA waiting for environment to be available. ▸ Over Processing : Engaging workforce in deployment planning, environment setup, manual releases. ▸ Defects : Bugs and Rework, Firefighting. ▸ Inventory : Piling up Work in Progress ▸ Waste of Resources : Allocating more than necessary, valuable processing power and memory ▸ Waste of movement : Exchanging emails, having multiple meetings for deployment planning Source : Amit Choudhary https://www.linkedin.com/pulse/20140928153300-27449214-when-i-see-devops-i-see-tps-and-poka-yoke
  43. 43. Visualising Work
  44. 44. Environment Creation Code Deployments Test Setup and Run Overly Tight Architectures THEORY OF CONSTRAINTS Bottlenecks
  45. 45. Code Pre Prod Prod shift bottlenecks
  46. 46. ENVIRONMENT AUTOMATION BUILD AUTOMATION DEPLOYMENT AUTOMATION REDUCING WAITING
  47. 47. Automated Self Serviced ENVIRONMENT AUTOMATION Production Like
  48. 48. Provisioning Configuring Bare Metal VMs Cloud
  49. 49. Bare Metal Cobbler Razor Kickstart Preseed
  50. 50. CLOUD Self Serviceable Managed Automation Dynamic Capacity
  51. 51. Infrastructure as a Code (IaaC) Ability to describe state of infrastructure Treat it similar to Application Code Repeatable, Flexible, Automat-able Consistent Provisioning and Configuration of Environments
  52. 52. Infrastructure as a Code (IaaC) VMs Cloud Configurations
  53. 53. Provisioning Cloudformation Openstack Heat Terraform APIs Vagrant Ansible
  54. 54. Dev Stg Prod Configuration Management
  55. 55. IaaC
  56. 56. Automated Virtual Environments Works with Hypervisors Integrates with Configuration Management Tools (e.g. chef, puppet, ansible)
  57. 57. Changing the way Software is Built, Shipped and Run Standardisation
  58. 58. DEFECTS
  59. 59. Causes Rework Waste of Time Firefighting and Stress Could Causes Downtimes
  60. 60. Test Driven Development Continuous Integration
  61. 61. Continuous Integration Small Batches Continuous Build Automated Testing Functional and Non Functional Immediate Feedback
  62. 62. Continuous Integration Jenkins GoCD CircleCI / Travis Bamboo
  63. 63. Gradle Rake/Make BUILD AUTOMATION Maven Gradle Ant Packer
  64. 64. Without automated testing continuous integration is the fastest way to get a big pile of jump that never compiles or runs correctly….. ! AUTOMATED TESTING
  65. 65. Automated UI Test Integration Test Unit Test Manual Test Anti Pattern Inverted Test Pyramid Automated UI Test Automated API Test Automated Service Test Automated Component Test Automated Unit Test Exploratory Test 10%
  66. 66. Continuous Delivery Extension of Continuous Integration Keep the builds green Always ready to release Business decides when to release
  67. 67. Continuous Deployment
  68. 68. Code Deploy Octopus DEPLOYMENT AUTOMATION Capistrano Scripts Ansible Chef/Puppet
  69. 69. CONTINUOUS DEPLOYMENT IS NOT CONTINUOUS RELEASE CONTINUOUS DEPLOYMENT
  70. 70. Blue Green Canary Feature ToggleDecouple Services Contingency Switches Release Strategies
  71. 71. AMPLIFYING FEEDBACK
  72. 72. Plan Code Pre Prod Prod Systems Thinking Monitoring CustomerIdea
  73. 73. Monitoring Health Logs Performance Metrics
  74. 74. Health Nagios Sensu Data Dog SNMP
  75. 75. ELK Stack Splunk Data Dog Graylog Logs
  76. 76. Grafana Kibana Graphite New Relic Performance Metrics App Dynamics
  77. 77. LIKE. SHARE. SUBSCRIBE. WWW.SCHOOLOFDEVOPS.COM

×