User:David/GTALUG July 14th puppet: Difference between revisions
No edit summary |
No edit summary |
||
Line 82: | Line 82: | ||
30. Inline documentation on types | 30. Inline documentation on types | ||
31. Managing packages | 31. Managing packages EXAMPLE | ||
32. | 32. Managing services EXAMPLE | ||
33. Managing files EXAMPLE | |||
Revision as of 15:07, 6 July 2015
based on http://www.example42.com/tutorials/PuppetTutorial/#slide-0
time goal: 40 minutes.
abstract:
Puppet is a tool for doing configuration management. This talk will go over what pupet is, what it can do and how to do it. There is more than one way to do it . and some lessons have been learned in the field and from the community. Slides / Notes
1. What is Puppet
2. Configuration Management advantages
3. References and Ecosystem
also see : #puppet
4. Software related to Puppet:
5.Installation
6. Puppet Versions
- why use the ditros version?
- why use puppetlabs version?
- PE ? Puppet enterprise.
7. Puppet Language
8. Resource Types (Types)
9. Simple samples of resources
10.More Complex examples of resources
11. Resource Abstraction Layer
12. Classes
13. Defines HOMEWORK
14. Variables
15. User Variables
16. Nodes - Default classification
17. Nodes - Alternative approaches
- On an External Node Classifier (ENC)
- With hiera_include HOMEWORK
18. The Catalog
19. Operational modes
- Masterless - puppet apply
- Master / Client - puppet agent
talking topics:
- push v pull
- dev versus test versus prod.
20. Masterless setup
21. Master / Client Setup
22. Certificates management
23. Certificates management - First run
24. Puppet configuration: puppet.conf
25. Main configuration options
26. Common command-line parameters
27. Useful paths
28. Other configuration files: HOMEWORK
29. Online documentation on types
30. Inline documentation on types
31. Managing packages EXAMPLE
32. Managing services EXAMPLE
33. Managing files EXAMPLE
To be spliced in:
A. work flow. day to day work.
B. Puppet file / Librarian, module management , r10k.
C.
Future talks:
I. Configuration management
II. Ansible