How to write a puppet config: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 12: | Line 12: | ||
* location where puppet configs are stored, a) in the foreman interface, b) on disk | * location where puppet configs are stored, a) in the foreman interface, b) on disk | ||
How to find out where the modules are kept | |||
puppet config print modulepath | |||
More information | |||
puppet config print all | |||
= Deployment = | = Deployment = |
Revision as of 18:13, 14 May 2014
Here is everything you need to know to write a puppet configuration for libvirt, our hypervisor. This is based on a workshop with Teague Sterling on May 14, 2014.
Background
- what is puppet
- what are puppet configs
- why do I need to write them?
- what is my best alternative if I don't write a puppet config?
Actually doing it
- location where puppet configs are stored, a) in the foreman interface, b) on disk
How to find out where the modules are kept
puppet config print modulepath
More information
puppet config print all
Deployment
- DEPLOY
- did it deploy everywhere? How to test that systematically?
What might go wrong
- What if it breaks?
- How to roll back?