Be a Master Chef: Crafting Recipes for Reliable Infrastructure

Transcript

1. Be a Master Chef Kumar Abhijeet Product Engineer Crafting Recipes for Reliable Infrastructure
3. Fabricating DBaaS@Gojek DevOps/Ruby Enthusiast Home Gym Owner Musician
4. A G E N D A Chef - What and Why How Chef Works Chaos and Standards Solving the chaos puzzle Guiding Principles Future of Chef
5. Configuration Management Tool Suite Solves the configuration problem in the IaC ecosystem Automates deployment and server management Mostly used in VM workloads Chef - What?
6. What does Configuration Management even mean?
7. Maintaining systems in a desired state Consistent state across all systems Enforcing policy and standards Avoid outages by eliminating misconfigurations Configuration Management - What?
8. Why do we need Configuration Management?
9. Performing System Administration at scale Eliminate human error from systems Automated Infra == Resilient Infra Cloud adoption and management made easy Configuration Management - Why?
10. Why are we discussing about Chef in a Ruby Meetup?
11. How does Chef work?
14. Let’s picture an application system
15. Rails Server VMs Patroni VMs API Traffic LB
19. Rails Server VMs Patroni VMs API Traffic LB
23. Rails Server VMs Patroni VMs API Traffic LB
24. Rails Server VMs Patroni VMs API Traffic LB
26. Load Compile Converge Cleanup Chef - Loading Process
28. Bad Code Good Code
29. Idempotence Multiple applications of the same action do not have side effects on the system state Doesn’t get added to the resource collection Convergence Bring the system state in line with a defined policy. Changes are made on the system only if they need to be made. Convergence & Idempotence
30. Idempotent Convergent Idempotent means not taking actions when they aren't needed, Convergent means it "settles" on a specific final state. - coderanger(aka Noah Kantrowitz)
31. Idempotent Convergent
32. Scalable Easier to rollback Predictable Efficient Convergence & Idempotence - Why?
34. Data Driven Configurations Manage Systems, not Records Utilize Service Discovery Extensible Abstractions Guiding Principles
35. ........
36. ........
40. POSIX Compatible
41. POSIX and Windows Compatible
43. Cloud Native Movement Mature Container Orchestration Toolings Business Strategy? Better Alternatives Future of Chef
44. Thank you! Link to the deck and related resources =>