How to write a puppet config: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
= Actually doing it = | = Actually doing it = | ||
To use the CLI, you'll need to be on alpha, where puppet is hosted on Cluster 2. | |||
* 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 = | ||
| Line 27: | Line 33: | ||
* http://libvirt.org/html/ | * http://libvirt.org/html/ | ||
* http://docs.puppetlabs.com/references/latest/configuration.html | * http://docs.puppetlabs.com/references/latest/configuration.html | ||
* http://docs.puppetlabs.com/references/latest/type.html | |||
* http://example42.com/ | |||
[[Category:Sysadmin]] | [[Category:Sysadmin]] | ||
Latest revision as of 19:27, 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
To use the CLI, you'll need to be on alpha, where puppet is hosted on Cluster 2.
- 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?