Version Controlling Foreman & Puppet

configuration-managementforemangitpuppetpuppetmaster

I have just setup Foreman for the first time & am not sure how to go about putting all of my configurations under version control. I know I can use Git for each module I install on my Puppet master but would prefer a more holistic solution that encompasses not just modules but also what classes are associated with each host and any variables set on the hosts. Any suggestions would be greatly appreciated along with related workflows. In case it's relevant, I do have GitLab setup as a central Git server on site and plan to setup a CI server such as Jenkins soon.

Best Answer

There is a plugin to keep your infrastructure definition in Foreman, pretty much a serialized version of your data in Git, and upload (and change your infrastructure) changes. Maybe that'd be useful for you

https://github.com/marianitadn/foregit

Related Solutions

Puppet-master/foreman “undefined method `[]’ for nil:NilClass on node” after update

Between Puppet 2 and 3, config.ru (used by Passenger to run the Puppet master under Apache) needs updating as Puppet's initialisation changed.

See the release notes here for the diff: Puppet 3 release notes: Puppet Master Rack Configuration Is Changed

Foreman's installer sets this file up at /etc/puppet/rack/config.ru, but Debian users using puppetmaster-passenger may find it under /usr/share/puppet/rack/puppetmasterd/.

Foreman users should also note the change to sudoers required for Puppet CA integration: Upgrade Puppet from v2 to v3 gotchas.

“Run Puppet” function in Foreman works inconsistently

I tried a number of ways to get kick running reliably but couldn't and it's deprecated anyway so I moved on to puppetssh. That required configuring smart-proxy's SSH keys, the foreman-proxy user and its sudo rights. There isn't a lot of documentation on this puppet run method and the DEBUG logging in foreman-proxy doesn't include any command output so it was hard to tell where/how something was failing.

By default, the foreman-proxy user doesn't have a shell (on RHEL) and wouldn't be able to run /usr/bin/ssh. A simple usermod -s /bin/bash did the trick but that seems like a security risk to me. On top of that, different sudo rights are necessary to run it so I had to change foreman-proxy ALL = NOPASSWD: /usr/bin/puppet kick to foreman-proxy ALL = NOPASSWD: /usr/bin/ssh. After that it was just a matter of configuring the ssh command.

In my case, we deployed a user account and SSH keys for running Puppet commands with sudo on client machines. I copied the private key to some place foreman-proxy could use it (eg: /etc/foreman-proxy/puppetssh/id_rsa) and configured the puppetssh parameters in /etc/foreman-proxy/settings.yml like so:

:puppetssh_command: /usr/bin/sudo /usr/bin/puppet agent -t --no-usecacheonfailure
:puppetssh_user: puppetssh
:puppetssh_keyfile: /etc/foreman-proxy/puppetssh/id_rsa

Best Answer

Related Solutions

Puppet-master/foreman “undefined method `[]’ for nil:NilClass on node” after update

“Run Puppet” function in Foreman works inconsistently

Related Topic