Configuration Management Tools

Very basic introduction to the Configuration Management Tools for the group Las Palmas DevOps.

Transcript

1. SCM Software Configuration Management
2. Captain Obvious alert!
3. This is why... Let’s talk about the basics
4. what are Software Configurations ?
5. The system behavior Hardware configurations System configurations Applications settings Organization policies
6. Configurations ≈ Policies The port 80 must be open The user X must have access MySQL database must be running Ping must be blocked
7. what does Software Configurations look like?
8. Configurations
9. Configurations
10. Configurations
11. Configurations
12. Configurations
13. Configurations
14. Configurations
15. Configurations
16. what is a SCM system?
17. SCM Systems Provisioning Change management
18. SCM on Modern Systems
19. From 1 machine to many
20. Working on the wrong server
21. From 1 sysadmin to many
22. Who did what?
23. What do we need? All changes documented All changes must be repeatable All changes in one place Accesibles for anyone All changes must be traceable
24. What does traceable mean? What have been changed? When have been changed? Who made the change?
25. What do we do? Configuration by hand Wiki One or few scripts Better scripts + Wiki Better scripts + Git/Svn Custom SCM (script+git+ssh loop)
26. How is a modern SCM? Declarative Abstract Idempotent Convergent
27. How is a modern SCM? Declarative Abstract Idempotent Convergent What NOT How
28. How is a modern SCM? Declarative Abstract Idempotent Convergent How it should behave Rely on the tool for the implementation
29. How is a modern SCM? Declarative Abstract Idempotent Convergent Only take action if it’s needed
30. How is a modern SCM? Declarative Abstract Idempotent Convergent Each resource takes care of itself
31. Key concepts Modern SCM
32. Modern SCM’s concepts Resources Nodes/Minions Recipes/Manifests/Playbooks Inventory Roles/Profiles
33. Some extras do we have time?
34. Avoid manual processes They are error prone
36. But be careful ;-)
37. Make Apps SCM friendly Separate data from code Allow to use ENV variables Set default options But allow overwrite them with conffiles
38. Do NOT hardcode settings!!! Ever!
39. Make Apps SCM friendly Use the dependency managers Composer Bundler Pip npm Maven
40. Make Apps SCM friendly Use flags to activate features Use standard formats Think about settings per environment
41. Recomendations Start small Think in policies not in manual changes Use Vagrant for developing policies
42. Recomendations
43. Popular SCMs CFEngine Puppet Chef Ansible
44. SCM vs Deploy Tools Debate