Codifying DevOps: Why How and What
•
4 recomendaciones•383 vistas
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.
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Codifying DevOps: Why How and What
Similar a Codifying DevOps: Why How and What (20)
Último
Último (20)
Codifying DevOps: Why How and What
- 2. CODIFYING DEVOPS WHY HOW AND WHAT OF DEVOPS
- 3. WHY?
- 4. Source : Devops Guide by IT Revolution Press
- 5. THE DEVOPS STORY EVOLUTION OF AGILE ORGANISATIONS
- 8. RELENTLESSLY WORK ON ELIMINATING WASTE FROM THE MANUFACTURING PROCESS…. TPS TPS/LEAN PHILOSOPHY
- 9. 8 TYPES OF WASTES ▸ Over Production ▸ Waiting ▸ Inventory ▸ Transportation ▸ Over Processing ▸ Motion ▸ Defects ▸ Workforce
- 10. TOYOTA PRODUCTION SYSTEM Just In Time Production Kanban Value Stream Mapping
- 13. THEORY OF CONSTRAINT Eliyahu M Goldratt 1984
- 14. THEORY OF CONSTRAINT ▸ Identify System’s Constraints ▸ Exploit the Constraint ▸ Subordinate everything to above decision ▸ Elevate the Constraint ▸ Repeat the Process
- 15. EXTREME PROGRAMMING (XP) SCRUM KANBAN DYNAMIC SYSTEMS DEVELOPMENT METHOD (DSDM) LEAN FEATURE DRIVEN DEVELOPMENT (FDD) METHODS
- 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. dev Ops
- 19. WALL
- 20. 2008 PATRICK DEBOIS AGILE CONFERENCE, TORONTO CANADA
- 21. AGILE SYSTEMS ADMINISTRATOR GROUP Patrick DeboisAndrew Clay Shafer
- 22. 2009. VELOCITY CONFERENCE John Allspaw Paul Hammond 10+ DEPLOYS A DAY , DEVOPS & OPS CO-OPERATION AT FLIKR
- 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. 2009
- 25. #devops
- 26. To achieve their business goals CHANGE to achieve competitive advantage to survive to respond to changing customer needs Organizations need to constantly
- 27. EACH OF THAT CHANGE TRANSLATES TO A DEFINING DEVOPS DEPLOYMENT
- 28. EACH OF THAT CHANGE INTRODUCES A DEFINING DEVOPS RISK
- 29. WHILE STILL ACHIEVING OFFERS A PATH TO REDUCE THE RISK DEVOPS RAPID CHANGE PRINCIPLES PRACTICES TOOLS IS A CULTURAL MOVEMENT WHICH
- 30. METRICS LEAD TIME TO CHANGE MEAN TIME TO RECOVER FREQUENCY OF DEPLOYMENTS CHANGE FAILURE RATES
- 31. Source : State of Devops Report 2016 by Puppet Labs
- 32. Pipeline Plan Code Test Release Deploy Operation Agile DEV OPS Devops DevOps Security
- 34. ORG Customer Centric Organisations Initiating Devops Culture Beliefe in Automation
- 35. Incorporate Ops Strategise Practices and Tools Architectural Chances TEAMS
- 37. PRINCIPLES
- 39. Systems Thinking Look at the big picture Reduce Waste Elevate Bottlenecks Improve the Flow
- 40. Plan Code Pre Prod Prod Systems Thinking
- 41. Source – The DevOps Handbook Value Stream Mapping
- 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. Visualising Work
- 44. Environment Creation Code Deployments Test Setup and Run Overly Tight Architectures THEORY OF CONSTRAINTS Bottlenecks
- 45. Code Pre Prod Prod shift bottlenecks
- 46. ENVIRONMENT AUTOMATION BUILD AUTOMATION DEPLOYMENT AUTOMATION REDUCING WAITING
- 48. Provisioning Configuring Bare Metal VMs Cloud
- 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. Infrastructure as a Code (IaaC) VMs Cloud Configurations
- 55. IaaC
- 56. Automated Virtual Environments Works with Hypervisors Integrates with Configuration Management Tools (e.g. chef, puppet, ansible)
- 57. Changing the way Software is Built, Shipped and Run Standardisation
- 58. DEFECTS
- 59. Causes Rework Waste of Time Firefighting and Stress Could Causes Downtimes
- 60. Test Driven Development Continuous Integration
- 61. Continuous Integration Small Batches Continuous Build Automated Testing Functional and Non Functional Immediate Feedback
- 63. Continuous Integration Jenkins GoCD CircleCI / Travis Bamboo
- 65. Without automated testing continuous integration is the fastest way to get a big pile of jump that never compiles or runs correctly….. ! AUTOMATED TESTING
- 66. 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%
- 67. Continuous Delivery Extension of Continuous Integration Keep the builds green Always ready to release Business decides when to release
- 70. CONTINUOUS DEPLOYMENT IS NOT CONTINUOUS RELEASE CONTINUOUS DEPLOYMENT
- 71. Blue Green Canary Feature ToggleDecouple Services Contingency Switches Release Strategies
- 73. Plan Code Pre Prod Prod Systems Thinking Monitoring CustomerIdea
- 74. Monitoring Health Logs Performance Metrics