A general landscape on devops practice

1. DevOps Landscape
Tools matter, but humans are the key.

2. https://xebialabs.com/periodic-table-of-devops-tools/

3. That’s all folks!

4. Just kidding!

5. Let’s start…
with some history.

7. 17 years ago!

9. Sadly, we focus
on tools instead of
practices and patterns.

10. Culture:
What happens when
the boss is away.

12. DevOps:
Nothing new,
old stuff in 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 step build!
• 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!
• Infrastructure provisioning
• Tools
• Shell scripting!
• Jenkins!
• Terraform
• Nomad
• Rancher

22. Configure
• Manager the environment 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. Easy?

25. Roadmap?

26. Some ideas
• Don’t believe 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. Large scale
implementation

28. Details
• Peru’s Federal Tax 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. Build a Culture

31. People is key

32. That’s all folks!