What does it take to be a good DevOps Engineer - Tamil / Vadivelu edition 0.1

Talk at Sri Sairam Engineering College (my alma-mater) to the 2nd and 3rd year CSE students on the topic of devops.

Please avoid this deck if you do not know or do not relate to the tamil actor Vadivelu, his comedy and the meme's he's used to rake up a storm with!

Transcript

1. WHAT does it take to be A DevOps Engineer ?
2. Instructions for next 1.5 hours KEEP YOUR MIC ON - REDUCE MIC VOLUME. RAISE HAND TO ASK QUESTIONS. I CAN SEE IF YOU RAISE HANDS! EVERYONE LEARNS TOGETHER. OR I’VE FAILED ALL OF YOU AND WASTED A LOT OF TIME! TAMIL, TELUGU, KANNADA, MALAYALAM, MARATHI, HINDI, ITALIAN AND ENGLISH ARE FINE. BUT LETS RESTRICT IT TO TANGLISH TODAY! 2
3. hello! I’m Ashwin! Seasoned DevOps practitioner! Director of DevOps & Infra @ Verloop https://cruisemaniac.com | mail@cruisemaniac.com 3
4. 0. Understand the rules to win the game! 4
5. 1. Who is a DevOps Engineer ? 5
6. “ A DevOps Engineer works with developers and the IT staff to oversee code releases. 6
8. WHO CONTD.. ✘ System and Network knowledge ✘ Scripting and Coding passion ✘ People and collaborative skills 8
9. 2. Let’s dig deeper... 9
10. DETAILS, FACTS, FIGURES Tools You’re an engineer. Always carry tools. Agility How quickly can you adapt to help deliver software? Culture Culture eats strategy for breakfast... 10
11. 3. CULTURE 11
12. Culture Devs are from Venus, Ops are from Mars 12
13. Culture... 13
14. Journey. Not Goal! A never-ending process of continual improvement. Do.. Rinse.. Repeat.. Culture... Idea - Inception level! Small cross-functional teams own the entire delivery process. You’re learning. Or. You’re losing. 14
15. Some more Culture.. Define responsibilities.. Share responsibilities.. Communicate more than required.. Work together.. Anticipate failure.. Dont blame.. Understand.. 15
16. 4. AGILITY 16
17. Agility Every organization is a technology organization.. Whether you know it or not.. 17
19. Agility Contd.. Faster orgs will eat larger orgs with bajji and kara chutney! Embrace Change! Plan for unplanned work! Failure is the new normal.. Understand your devs.. Question your assumptions.. Question everyone’s assumptions.. 19
21. 5. TOOLS 21
22. Tools If the only tool you have is a hammer, It’s hard to drink rathna cafe sambar! 22
23. Reinforce Behaviour Help an organization collaborate better. Allow employees to cross boundaries. Tools should enable you.. They should not define you! Enhance team capabilities Allow teams to understand what they cannot see. Help plan and course-correct 23
25. What should you get started on? 25
26. Operating Systems 26
27. Kernel management Process, I/O and Memory Management Threading, Concurrency, Race conditions Virtualization and Containerisation - cgroups File systems - Native + Distributed Computer Architecture 27
28. Networking 28
29. IPV4 / IPV6, CIDR Blocks, Network ranges, classes DNS Subnets, Addressing, Network Segmentation Routing, Network components - Gateways, VPNs Firewalls, security - TLS 1/1.1/1.2 WAN architectures - Load balancing, HA, Proxies, CDNs 29
30. Scripting && AUTOMATION 30
31. Focus on shell scripting. Nothing is faster than a shell script Learn how automation works. Learn multiple automation tools - Ansible + Chef Learn SSH like the back of your hand! Version control is GOD! Every other tool will change to or behave like git. Configure your laptops using a script. 31
33. Languages 33
34. Understand at least 2 programming languages Learn to write non-trivial code Understand how to deploy this code on a server - virtualbox / docker Understand databases at their algorithmic level. How does replication work? 34 Write non-trivial database scripts - PL/SQL / Stored Procedures
36. CLOUD 36
37. GROK at least 1 cloud. Preferably AWS Create a virtual machine. Deploy code. Deploy using automation - CI / CD - Jenkins, Ansible Learn 2 IaC tools - Terraform + aws-cli Practice scaling. 37 Tie everything together - Network + Code + Machines + Database - On the cloud. CI / CD THIS!!!
38. Monitoring 38
39. Knowing is everything. Your systems should tell you if they’re not fine. Learn Prometheus + Cloudwatch Differentiate between idle state and load state Know what is failure load. 39 Performance testing and capacity planning
41. thanks! Any questions? You can find me at @cruisemaniac mail@cruisemaniac.com 41