Downloaded 19 times
Uploaded byDirk Wallerstorfer
Moving beyond DevOps with automated cloud-native platforms
The document discusses the transition from traditional DevOps to autonomous cloud operations, emphasizing automation and tool consolidation to enhance performance monitoring and resource efficiency. It outlines strategies for implementing continuous deployment (CD) pipelines, auto-remediation, and shift-left/right practices to increase speed and quality in software development. The goal is to foster a culture of 'no operations' (noops) by integrating cloud and container platforms while improving customer satisfaction through proactive issue resolution.
Moving beyond DevOps with automated cloud-native platforms
- 1. confidential Moving beyond DevOps withautomated cloud-native platforms Dirk Wallerstorfer, Team Lead Innovation Lab ContainerDays 2018 Hamburg, 19 June 2018
- 2. 85% of enterprisesare implementing DevOps
- 3. confidential The typical organizationmonitors no more than 5% of their apps for performance and availability.
- 4. On average, asingle transaction uses 82 different types of technology Browser Multi-geo Mobile Network Code Hosts Logs IoT 3rd parties Services Cloud SDN Containers Application complexity
- 5. confidential Moving to autonomouscloud operations - Tool Consolidation - Automation - Cloud Migration - PaaS Migration - Unbreakable CD - Metadata Information Democracy Runbook Automation Self Protecting Biz Automation Biz Impact Security Detection Virtual Operations Free up resources Enable autonomous operations Implement safety nets Introduce auto-remediation Automate everything Autonomous operations
- 6. Free up resources 25+tools to keep the lights on War rooms Operations is manual Goal: increase visibility, free up resources 1
- 7.
- 8.
- 9.
- 10. Enable autonomous operations Migrateto cloud and container platforms Move towards NoOps – culture change Have an integrated platform Goal: microservices, CD pipeline 2
- 11.
- 12.
- 13. Implement safety nets Movefast, but don’t break things Give autonomy and safety “Unbreakable” software development Goal: shift-left, shift-right, unbreakable CD 3
- 14. Injecting speed & quality:automatic gate at test & performance • Continuous Performance Validation for daily builds • Root Cause details automatically pushed to JIRA • Decisions made to compare, break, or good-to-go Shift-left:engage Dev withearlier & automatedfeedback
- 15.
- 16. confidential pushDeploymentEvent Pushes Deployment Infoto Entities validateBuildWorker Compares Builds and Approves/Rejects Pipeline pushDeploymentEvent Pushes Deployment Info to Entities validateBuildWorker Validates Production and Approves/Rejects Pipeline handleProblemNotification Executes Auto-Remediating Actions, e.g: Rollback Build 6 Build 7 Production Production Auto-Approve! Auto-Reject! Auto-Approve! Auto-Reject!
- 17. Introduce auto-remediation Autonomous operations Pushevents Identify remediation actions 4
- 18.
- 19. confidential Auto remediation: pathto autonomouscloud operations Auto Mitigate! 1 CPU Exhausted? Add a new service instance! 3 Issue with BLUE only? Switch back to GREEN! ?Escalateat 2AM? 2 High Garbage Collection? Adjust/Revert Memory Settings! 4 Hung threads? Restart Service! 5 Still ongoing? Initiate Rollback! Escalate ? Still ongoing?5 1 2 3 4 MarkBadCommits UpdateDev Tickets … … Impact Mitigated??
- 20. Automate everything Build autonomoussystems Use Virtual Assistants to run operations Enable applications to react in real-time 5
- 21. The standup Howare we doing from an operational perspective? Do I need to adjust the priorities of the team? Anything important for my team?
- 22. The board meeting Isour digital business growing? Are our digital processes working well for customers ? Are we meeting availability, technical requirements and costs? Are customers adopting new functionalities as expected?
- 23.
- 24.
- 25.
- 26.
- 27. confidential Mary Hi Dirk! Wewant to apologize for the poor performance of our website today. We’re working under high pressure to fix this. We’d like to offer you free shipping and a free descaling set for the coffee maker you bought last week. Dirk Wow – cool, thanks!
- 28. confidential instead of losing you’remaking And, you have a happy customer that will come back for more! 100% 90%
- 29. confidential you’re making And, youhave a happy customer that will come back for more! 90% you’re making 98% What if only 20% of your users are affected and get the discount?
- 30. confidential What you coulddo tomorrow
- 31.
- 32.
- 33. confidential What you coulddo tomorrow should
- 34. confidential Cost Efficiency TeamEfficiency Business Efficiency Build your scorecard Number of tools used Costs to keep the lights on Dev to Ops relationship Time to adoption Delivery team size/Number of manual steps required Failed business transaction
- 35. www.dynatrace.com confidential Team Lead InnovationLab dirk.wallerstorfer@dynatrace.com @wall_dirk Thank you!
- 36. confidential Links Breaking theMonolith: An 8 step recipe https://www.dynatrace.com/news/blog/breaking-the-monolith-an-8-step-recipe/ Fearless Monolith to Microservices Migration – A guided journey (part 1 of n) https://www.dynatrace.com/news/blog/fearless-monolith-to-microservices-migration-a-guided-journey/ AWS DevOps Tutorial: Unbreakable pipeline https://github.com/Dynatrace/AWSDevOpsTutorial Auto remediation / self healing https://www.dynatrace.com/news/blog/set-up-ansible-tower-with-dynatrace-to-enable-your-self-healing- applications/ https://www.dynatrace.com/news/blog/servicenow-and-dynatrace-great-symbiosis-for-self-healing-applications/ https://www.dynatrace.com/news/blog/stackstorm-enables-auto-remediation-dynatrace/