| 1 | = Puppet = |
| 2 | |
| 3 | MF/PL is moving toward puppet as a system administration infrastructure. |
| 4 | |
| 5 | |
| 6 | == administering puppet == |
| 7 | |
| 8 | puppet can be intimidating. If you want to help with the administration, here's instructions to get started: |
| 9 | |
| 10 | === setting up a development environment === |
| 11 | |
| 12 | Get the configuration: |
| 13 | |
| 14 | {{{ |
| 15 | git clone git://git.mayfirst.org/mfpl/puppet |
| 16 | cd puppet |
| 17 | git submodule init |
| 18 | git submodule update |
| 19 | }}} |
| 20 | |
| 21 | And as the superuser, install the tools: |
| 22 | {{{ |
| 23 | apt-get install puppet-common |
| 24 | }}} |
| 25 | |
| 26 | then copy and update the sample configs to refer to your current environment: |
| 27 | {{{ |
| 28 | cp puppet.conf.sample puppet.conf |
| 29 | cp fileserver.conf.sample fileserver.conf |
| 30 | $EDITOR puppet.conf fileserver.conf |
| 31 | }}} |
| 32 | |
| 33 | some important changes to consider: |
| 34 | |
| 35 | * repoint `[files] path` in `fileserver.conf` |
| 36 | * make a simple `var` dir for your dev puppetmaster to stash its data |
| 37 | * repoint all the explicit dirs in `puppet.conf` to the `var` dir |
| 38 | |
| 39 | Then you can launch the puppet master as a non-privileged user from the checked-out directory: |
| 40 | |
| 41 | {{{ |
| 42 | puppet master --confdir=$(pwd) --no-daemonize --verbose |
| 43 | }}} |