How to Use DevOps & APM to Release Better Software Faster
•Download as PPTX, PDF•
5 likes•1,250 views
This document discusses how DevOps and application performance management (APM) can be used together to release better software faster. It provides three key points: 1) DevOps breaks down silos between development and operations teams and enables collaboration, infrastructure automation, continuous integration and delivery, and other practices that reduce risks and speed up the software release cycle. 2) Applying APM strategies throughout the entire software lifecycle provides visibility into business metrics and the health of each build. This allows issues to be identified and prioritized earlier when they are cheaper to fix. 3) Integrating APM intelligence into deployment workflows and automated processes helps optimize mean time to repair and allows software to be released at the speed of business
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to How to Use DevOps & APM to Release Better Software Faster
Similar to How to Use DevOps & APM to Release Better Software Faster (20)
More from Dynatrace
More from Dynatrace (20)
Recently uploaded
Recently uploaded (20)
How to Use DevOps & APM to Release Better Software Faster
- 1. 1 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive How to Use DevOps & APM to Release Better Software Faster Brett Hofer Global DevOps Practice Lead Dynatrace @brett_solarch Hasan Yasar Technical Manager Carnegie Melon SEI @SEINews
- 2. © 2015 Carnegie Mellon University How to Use DevOps & APM to Release Better Software Faster Hasan Yasar Technical Manager Software Engineering Institute Carnegie Mellon University
- 3. 3 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University DevOps ? Why
- 4. 4 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Known SDLC / Waterfall process
- 5. 5 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University With Agile
- 6. 6 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Business Research Budget Document Water- Jez Humble, https://youtu.be/L1w2_AY82WY Dave West, http://sdtimes.com/analyst-watch-water-scrum-fall-is-the-reality-of-agile/
- 7. 7 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Business Research Budget Document Water- Development Scrum- Jez Humble, https://youtu.be/L1w2_AY82WY Dave West, http://sdtimes.com/analyst-watch-water-scrum-fall-is-the-reality-of-agile/
- 8. 8 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Business Research Budget Document Water- Development Scrum- Integrate Test Release Fall Jez Humble, https://youtu.be/L1w2_AY82WY Dave West, http://sdtimes.com/analyst-watch-water-scrum-fall-is-the-reality-of-agile/ QA & Operations
- 9. 9 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Shared Goals CollaborationBusiness Needs DevOps
- 10. 10 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Teams Together DevOps brings
- 11. 11 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Project Roles Have Different Functions Developers Operations Create Change Deliver Maintain Monitor Manage Environment
- 12. 12 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Developers Favor Dynamic Behaviors Developers Operations Create Change Deliver Maintain Monitor Manage Environment
- 13. 13 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Operations Favors Static Behaviors Developers Operations Create Change Deliver Maintain Monitor Manage Environment
- 14. 14 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Developers Operations Create Change Deliver Maintain Monitor Manage Environment Where is the real pain?
- 15. 15 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Software Projects Are Complex Deployment Maintenance Security Programming Infrastructure Scalabilty Networks Functional Requirements Performance Testing User Interface Technical Documentation Updates Code Review Release Review User Documentation Data Privacy Intrusion Detection User Requirements Business Constraints Legal Issues Market Needs Budgets / Timelines
- 16. 16 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Information Security Expertise Deployment Maintenance Security Programming Infrastructure Scalabilty Networks Functional Requirements Performance Testing User Interface Technical Documentation Updates Code Review Release Review User Documentation Data Privacy Intrusion Detection User Requirements Business Constraints Legal Issues Market Needs Budgets / Timelines Business Analyst Expertise Quality Assurance Expertise IT Operations Expertise Developer Expertise
- 17. 17 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University DevOps Breaks Down Silos: Eliminate pains
- 18. 18 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University The DevOps Lifecycle : Faster release with visible feedback loop! Collaboration between project team roles Infrastructure as Code: Scripted Infrastructure Configuration Automation of Tasks / Processes / Workflows Performance Monitoring Applications and Infrastructure
- 19. 19 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Collaborative Decisions DevOps enables
- 20. 20 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Goal: Eliminate risk in through SLDC /siloed Team
- 21. 21 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University The DevOps lifecycle is Full of Decision Points Without team knowledge, developers continually make uninformed decisions, causing eventual risk or inefficiency
- 22. 22 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University The DevOps lifecycle is Full of Decision Points How many users? Payment model? Who is the Target Market? Which regions?
- 23. 23 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University The DevOps lifecycle is Full of Decision Points What OS? What ports? VMs or containers? Entry points?
- 24. 24 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University The DevOps lifecycle is Full of Decision Points What kind of user authentication? REST vs SOAP? How to architect for scalability?
- 25. 25 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Uninformed Decisions Lead Your Project Down Suboptimal Paths Developers Only Dev + Ops
- 26. 26 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University DevOps enables Infrastructure Automation
- 27. 27 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University A Traditional Scenario A system requires multiple servers networked together Each server is to be provisioned uniquely, providing a specific service
- 28. 28 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University A Traditional Scenario At deployment, the deployment environment (Test / QA / Production) is manually provisioned to match the expected infrastructure configuration This often means manual installation of packages, configurations, and networking components… …and room for human error
- 29. 29 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Divergence on deployment process Environments are independent, volatile, and easily manipulated. Without care, they will diverge.
- 30. 30 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Move into automation : Infrastructure as Code (IaC) A Code that creates infrastructure * A concretely defined description of the environment is good material for conversation between team members.
- 31. 31 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University IaC Apparent Benefits Because the environment and application are versioned together, tagging code is that much more meaningful.
- 32. 32 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University IaC Promotes Quality Attributes The process that creates and configures the infrastructure for your application is, itself, an application. As an application, environment creation and configuration is now: • Automatable • Repeatable • Versionable • Reviewable • Testable (it works) • Human-readable • Verifiable (it is right)
- 33. 33 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University IaC Has Operational Benefits • Lower Risk • Guaranteed Documentation • Stable Rollback • Fast Onboarding • Time Savings • 100% Environment Parity
- 34. 34 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Common DevOps enabled tools for :IaC Chef or Puppet - wrappers around your shell provide hooks and convenience methods abstract operating system-specifics, provide portability Ansible or Fabric - to automate apps and IT infrastructure Docker - linux containers runs on Linux only (for now) entire environments can be easily shared Shell scripts – simply scripting platform-specific commands Vagrant - assists in managing virtual machines and executing provisioners
- 35. 35 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University And brings Quality! DevOps improves Defects Detection
- 36. 36 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Automating Integration Fixes These Issues Automation… Removes inefficiencies due to human-driven process Standardizes artifact submission process Guarantees consistent results Allows team to fail fast (and fix fast) Reduces pain of integration
- 37. 37 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Continuous Integration is Even Better Continuous Integration uses a build server to… Integrate artifacts on every change Give team with immediate notification of failure or success Require issues be fixed before moving forward Enforce standards (can fail based on quality as well as functionality)
- 38. 38 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Fail the Build When Software is Not Good Enough Don’t just configure failure for compile/build errors! Want 90% test coverage? Fail the build if code base is <90% covered Want all DB queries < 2sec? Test them, and fail the build otherwise Want to make sure code conforms to style guide? You guessed it… CI is your best tool to enforce quality standards
- 39. 39 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Continuous Integration Requires Some Discipline… For successful implementation of a CI process: Developers must commit changes often CI system should build every commit Automate every step of the build process Automate tests, and fail the build on test failure CI system should report results immediately to everyone CI system should instantly revert to previous release on failure All environments should have 100% parity
- 40. 40 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University …But Yields Significant Rewards Lower costs • Immediate detection of problems • Removal of human integration labor Greater visibility for everyone • Developers • Operations • Quality Assurance • Management • Customers Increased confidence in your software
- 41. 41 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Global Vision Project Management Tools Issue Tracker Wiki
- 42. 42 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University DevOps Interoperability / Traceability - General
- 43. 43 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University DevOps - Interoperability / Traceability –Reference Implementation
- 44. 44 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Human actions/inputs to the software development process
- 45. 45 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Actions performed by autonomous systems
- 46. 46 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University And enables Faster Release DevOps reduces Deployment Failures
- 47. 47 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Continuous Deployment Changes are deployed ASAP into production Continuous Delivery Changes are deployed immediately into a production-like environment, to ensure that they could be deployed into production
- 48. 48 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Shift Left Operational Concerns
- 49. 49 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Shift Left Operational Concerns
- 50. 50 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Gold-standard deployment • Environment Parity by IaC • Use the same process to deploy to development, test, and production • Automate • Perform incremental changes • Appropriate Testing
- 51. 51 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Continuous Delivery Enforces 100% Parity Environment inconsistencies between environments will result in risks ✔ ✔ ✔ ✖
- 52. 52 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Incremental Changes, Continues Testing, Early Performance Monitoring • Smaller changes to production can be less risky than large ones • Decrease the number of potential defects that could cause an outage • Monitor the performance of application as early as possible.
- 53. 53 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Test Enough That You Are Sure You Could Deploy Successfully How much is enough? What factors are important to you and your organization? Security? Automate a large number of security-focused unit/integration tests Scalability? Automate high-volume load testing Design your CI/CD success criteria to enforce your goals
- 54. 54 How to Use DevOps & APM to Release Better Software Faster © 2015 Carnegie Mellon University Continuous Delivery Is REALLY About Rigorous Testing Certainty requires rigorous testing before and after deployment
- 55. 55 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive How to Use DevOps & APM to Release Better Software Faster Brett Hofer Global DevOps Practice Lead Dynatrace @brett_solarch
- 56. Release at the Speed of Business • Increase speed to market while improving quality and performance • Injecting DevOps practices into the Application Lifecycle • Application Performance Management Best Practices
- 57. 57 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive • Bake your APM strategy right into the application lifecycle • Dev and Ops teams – improve processes! • Ensures Business Success Metrics are always visible & understood throughout the entire Application lifecycle • APM integration done in parallel with dev - minimal to no coding impacts yet increasing speed & quality Release “at the speed of business”
- 58. 58 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive • Bake your APM strategy right into the application lifecycle • Dev and Ops teams – communicate effectively! • Collaborate on the health of each build • Comprehensive Dashboard strategy • Consistent measurements between Dev, Test and Production • Identify, prioritize and shift business goals as far left as possible • Everyone understands them early on • Monitor build state, KPIs, SLAs and risks throughout life cycle Release “at the speed of business”
- 59. 59 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive • Bake your APM strategy right into the application lifecycle • Optimize and automate issue feedback • Faster feedback in Dev and Test = faster prioritization to fix • Finding issues earlier and faster means cheaper • Earlier in lifecycle = cheaper • Delivering functionality faster means risk to experiencing issues in production • Imperative to have a comprehensive APM strategy early to ensure root cause and fix lifecycle is reliable and fast • Decreased MTTR at every leg of delivery means faster and more reliable delivery of functionality. Release “at the speed of business”
- 60. 60 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive • Reducing cycle times/optimizing MTTR throughout • Use APM best practices for reliable, accelerated deployments • Integrating APM intelligence into deployment workflows • Integrating APM throughout automated deployments (including elastic VM, cloud and container environments) Release “at the speed of business”
- 61. 61 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Thank-you! Brett Hofer @brett_solarch http://blog.dynatrace.com Hasan Yasar @SEINews https://insights.sei.cmu.ed u/devops/
Editor's Notes
- organizations adopting devops are deploying code 30 times more frequently with 50% fewer failures. 3/4 of enterprise organizations are currently evaluation Docker for production use. Those kind of numbers are here to stay.
- organizations adopting devops are deploying code 30 times more frequently with 50% fewer failures. 3/4 of enterprise organizations are currently evaluation Docker for production use. Those kind of numbers are here to stay.
- POSSIBLE DIAGRAM
- POSSIBLE DIAGRAM
- POSSIBLE DIAGRAM
- Misalignment Causes Pain When Tasks Intersect
- organizations adopting devops are deploying code 30 times more frequently with 50% fewer failures. 3/4 of enterprise organizations are currently evaluation Docker for production use. Those kind of numbers are here to stay.
- DIAGRAM
- DIAGRAM
- DIAGRAM
- DIAGRAM
- DIAGRAM <decisions image with proper input> Again, not 100% on what to put on these. This is just a suggestion.
- You can’t buy or hire DevOps. It requires wholesale organizational buy-in, and a potentially substantial culture shift to be successful
- JESSICA – I’m concerned that the black lettering on gray boxes may not be visible to audience…thoughts on switching to white lettering? So, back to IaC.. For example, the database server needs Postgres, the application server needs a specific version of Node.js, a few other services that require various Python modules running on different machines..
- How do we replicate the development environment exactly? Up to this point, it’s never existed “properly” as its actual components, only either just a collection of running processes or a virtualized version of the actual components. ** Add
- ** Add ‘project team’ on left – developers and ops working together to create the provisioning script – and the provisioning script creating the developers’ environments. ** Tabled: call out each environment, or reduce to “multiple environments”, add in “staging”?
- ** Split into three slides ** graphic for first statement
- Increased assurance / confidence of working software Guaranteed documentation of environment configurations Easy migration (roll back / move forward) of entire environment Easy onboarding of new team members Time savings over the life of a project 100% parity between all environments
- organizations adopting devops are deploying code 30 times more frequently with 50% fewer failures. 3/4 of enterprise organizations are currently evaluation Docker for production use. Those kind of numbers are here to stay.
- Work on this: Enable instant revert to previous releases
- organizations adopting devops are deploying code 30 times more frequently with 50% fewer failures. 3/4 of enterprise organizations are currently evaluation Docker for production use. Those kind of numbers are here to stay.
- Dev wants to go fast Testing Team wants to keep up with dev, but moves slower Ops wants to go slow
- *Add these notes as a slide element Very large movement where Business is looking to deliver functionality faster, more agile, introduce more features in mobile and desktop quicker to beat the competition, respond to issues quickly and enhance the customer experience regularly. This means releasing software updates more often. Doing that increases risk and so a certain type of culture has to be adopted. DevOps has been that culture of choice. DevOps is made up of three pillars that a team will typically look to optimize: People, Process and Technology Engagement uses a single application within a company and helps identify a single critical dashboard along with some example Business KPIs and then walks the DevOps teams through an optimal continuous delivery lifecycle with automation to ensure the proper people, processes and technology leverage the most out of Dynatrace. Ultimately this helps them achieve faster time to market while maintaining quality necessary for the Business. Ideally they will leverage this work when implementing it for the rest of the application.
- *Add these notes as a slide element Very large movement where Business is looking to deliver functionality faster, more agile, introduce more features in mobile and desktop quicker to beat the competition, respond to issues quickly and enhance the customer experience regularly. This means releasing software updates more often. Doing that increases risk and so a certain type of culture has to be adopted. DevOps has been that culture of choice. DevOps is made up of three pillars that a team will typically look to optimize: People, Process and Technology Engagement uses a single application within a company and helps identify a single critical dashboard along with some example Business KPIs and then walks the DevOps teams through an optimal continuous delivery lifecycle with automation to ensure the proper people, processes and technology leverage the most out of Dynatrace. Ultimately this helps them achieve faster time to market while maintaining quality necessary for the Business. Ideally they will leverage this work when implementing it for the rest of the application.
- *Add these notes as a slide element Very large movement where Business is looking to deliver functionality faster, more agile, introduce more features in mobile and desktop quicker to beat the competition, respond to issues quickly and enhance the customer experience regularly. This means releasing software updates more often. Doing that increases risk and so a certain type of culture has to be adopted. DevOps has been that culture of choice. DevOps is made up of three pillars that a team will typically look to optimize: People, Process and Technology Engagement uses a single application within a company and helps identify a single critical dashboard along with some example Business KPIs and then walks the DevOps teams through an optimal continuous delivery lifecycle with automation to ensure the proper people, processes and technology leverage the most out of Dynatrace. Ultimately this helps them achieve faster time to market while maintaining quality necessary for the Business. Ideally they will leverage this work when implementing it for the rest of the application.
- *Add these notes as a slide element Very large movement where Business is looking to deliver functionality faster, more agile, introduce more features in mobile and desktop quicker to beat the competition, respond to issues quickly and enhance the customer experience regularly. This means releasing software updates more often. Doing that increases risk and so a certain type of culture has to be adopted. DevOps has been that culture of choice. DevOps is made up of three pillars that a team will typically look to optimize: People, Process and Technology Engagement uses a single application within a company and helps identify a single critical dashboard along with some example Business KPIs and then walks the DevOps teams through an optimal continuous delivery lifecycle with automation to ensure the proper people, processes and technology leverage the most out of Dynatrace. Ultimately this helps them achieve faster time to market while maintaining quality necessary for the Business. Ideally they will leverage this work when implementing it for the rest of the application.