Difference between revisions of "Configuration Management with Puppet: Part 1"
From Gridkaschool
(→Agenda) |
(→Abstract) |
||
| Line 1: | Line 1: | ||
| − | |||
| − | == Abstract == |
||
| − | |||
| − | The idea is to give the participants first an idea about the |
||
| − | puppet language. Next we show how to use puppet in the |
||
| − | client/server setup but without git. |
||
| − | |||
| − | we will create for all participants local environments on the puppetmaster |
||
| − | where they can create their manifests. |
||
| − | |||
| − | They also have to create locally the node definitions on the puppetmaster. |
||
| − | |||
| − | Before Step 8 we change the puppetmaster configuration, to a git-o-lite |
||
| − | setup. |
||
| − | |||
| − | Before Step 10 we change the puppetmaster configuration, to use a ENC |
||
| − | |||
== Agenda == |
== Agenda == |
||
Revision as of 13:54, 14 August 2014
Agenda
- Introduction (Sven)
- Hands-On
- login to vm
- write simple manifest and apply
- Puppet Client/Server
- Hands-On
- login to puppetmaster
- write node definition
- write simple manifest in user environment
- execute puppet agent call on vm
- GIT basics
- Hands-On
- clone repository
- branch
- change file
- commit
- push
- Puppet with GIT
- Hands-On
- Write an real world example
- push with git to pm
- run puppet agent on vm
- Hiera
- Hands-On
- Enhance example from 7 with hiera
Step 11: ENC
Step 12: Hands-On - Configure Machine with an ENC
