These are the puppet classes driving the hosts running oftc.net. The actual host->class mapping is done in LDAP and is not part of this repository. The hieradata is also in a separate repository.
Currently, too much code is placed under modules/oftc/, please add new stuff as
a separate module (unless trivial). Ideally, the oftc::whatever namespace
should only be used as entry points from the LDAP puppetClass records.
apt-get install puppet ruby-ldap
Get puppet schema: https://github.com/puppetlabs/puppet/blob/master/ext/ldap/puppet.schema
For developing and testing changes to oftc-puppet, it is best to create your own "environment" (in puppet speak). In your $HOME on the puppet master, do:
HOME$ git clone [email protected]:oftc/oftc-puppet.git
HOME$ cd oftc-puppet
oftc-puppet$ git clone /srv/git/oftc-hieradata-private.git/ hieradata
oftc-puppet$ sudo ln -s $HOME/oftc-puppet /etc/puppet/environments/$USER
oftc-puppet$ sudo ln -s $HOME/oftc-puppet/hieradata/oftc.yaml /etc/puppet/hieradata/$USER.yaml
oftc-puppet$ ... hack away ...
On the host in question, do sudo puppet agent -t --environment $USER
(alias: pat --environment $USER). The only thing that can't be tested without
pushing first is changes to hieradata/$HOST.yaml. Also, the list of puppet
classes from LDAP is fixed and not configurable per environment.
oftc-puppet$ git commit && git push
oftc-puppet/hieradata$ git commit && git push