All Projects → tazjin → puppet-masterless

tazjin / puppet-masterless

Licence: MIT License
A simple skeleton/template for a masterless Puppet setup using systemd.

Programming Languages

Puppet
460 projects
shell
77523 projects
ruby
36898 projects - #4 most used programming language

Masterless Puppet with systemd

This repository is intended as a sort of "template" for masterless Puppet setups on systemd-based distributions. This exact setup has been used on CentOS, but it should work on many other distributions (such as Debian >= 8) as well.

This setup is opinionated and requires that the infrastructure adheres to things such as a strict naming schema and version-controlled Puppet manifests in a git repository.

Bootstrapping

To bootstrap this repository on a machine, make sure you have installed Puppet as well as librarian-puppet.

# On Debian 8+
apt-get install puppet librarian-puppet git

# On CentOS 7+ (EPEL required)
yum install epel-release git && yum install puppet
gem install librarian-puppet

Make sure that the root user has an SSH key that can access your git-repo. On BitBucket, you can use the deployment-key feature for read-only access keys.

Clone the repository using git to the destination folder, /etc/puppet. You may have to remove this folder first.

rm -rf /etc/puppet && git clone [email protected]:company/puppet.git /etc/puppet

After this, you may proceed by running Puppet manually once. This should set up everything:

puppet apply --modulepath /etc/puppet/modules /etc/puppet/manifests

You should now have a host with a masterless Puppet setup. Use this for example to create a base image that other machines can be created from.

Hostnames

Hostnames are used to determine the role of a machine. Therefore you need to stick to the strict host naming schema defined in role.rb. You may amend the regular expression in that module to fit your needs.

More documentation

Please see puppet.md for more detailed documentation on this Puppet setup.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].