Downloaded 14 times
Uploaded byDomingo Suarez Torres
Devops Landscape
This document provides an overview of DevOps tools and practices categorized into different stages: plan, code, build, test, package, release, configure, and monitor. It emphasizes that tools are not as important as culture and practices. The document also discusses challenges faced in large-scale DevOps implementations like at Peru's Federal Tax Collection Office and opportunities to improve practices around source control, testing, continuous integration, packaging, and deployment. Overall, the document stresses the importance of building a collaborative culture over relying on specific tools.
More Related Content
![Building a Cloud-Native Company in 2020 [DevOps Days Buffalo]](https://cdn.slidesharecdn.com/ss_thumbnails/buildingacloud-nativecompanyin2020updateddevopsdaysbuffalo-211020062108-thumbnail.jpg?width=640&height=640&fit=bounds)
Devops Landscape
- 1. DevOps Landscape Tools matter,but humans are the key.
- 2.
- 3.
- 4.
- 5. Let’s start… with somehistory.
- 7.
- 9. Sadly, we focus ontools instead of practices and patterns.
- 10. Culture: What happens when theboss is away.
- 12. DevOps: Nothing new, old stuffin Millennials’ times.
- 13. • Government laws •Corporate rules, policies. • Personal habits
- 15. Categories 1. Plan 2. Code 3.Build 4. Test 5. Package 6. Release 7. Configure 8. Monitor
- 16. Plan • Key factors •Functional specification • Up to date schedule • Predictive vs adaptative • Tools • Scrum/Kanban boards
- 17. Code • SCM • Git •Branching (Feature branches, Pull requests) • Distributed • Code review • Tools • GitHub, BitBucket, GitLabs
- 18. Build • One stepbuild! • Automatic • CLI based • Tools • Gradle, Maven, Make
- 19. Test • Types • Unit •Integration • Functional (User Acceptance) • Stress • Load • Automated! • Tools • TDD, BDD, ATDD • JUnit, Spock • Selenium (Functional)
- 20. Package • Binary • Automated •Repository • Linux Containers • Promotable (Same package, different environment) • Tools • Linux Containers (Docker, rkt, CRI) • NPM • Maven
- 21. Release • Automated! • Infrastructureprovisioning • Tools • Shell scripting! • Jenkins! • Terraform • Nomad • Rancher
- 22. Configure • Manager theenvironment specific settings • Secure access • Easy administration and distribution • Tools • SCM • Vault • HCM
- 23. Monitor • Metrics! • Extract,Transform & Load • Data retention • Tools • New Relic • Datadog • Nagios • ELK • InfluxDB + Grafana, Telegraft, Cronogaft • Prometheus
- 24.
- 25.
- 26. Some ideas • Don’tbelieve in vendors (nor suites) • No silver bullets. There is no a ultimate methodology • Start simple, eat a slice not the whole pie • Choose a simple product to begin learning • Prepare yourself to fail big time! • If you start winning, perhaps you have biased evaluation. • Double check. Ask for advice.
- 27.
- 28. Details • Peru’s FederalTax Collection Office • Microservices architecture (Java) • Single Page Application • Docker containers • Kubernetes for container orchestration
- 29. Opportunities • Git underused •No feature branch. • No remote mirroring • Lack of automated tests • CI underused • Packaging • Tiny Storage • Deployment • Manually performed
- 30.
- 31.
- 32.