ReleaseEngineering:Puppet:Dashboard
Contents
Assumptions
It is assumed that the EPEL repository is setup and that the puppet (and puppet-master) packages were installed from there.
Puppet-master and the dependencies should be at their latest versions
Installation
On the puppetmaster:
Puppetlabs has just recently setup a yum repo with custom RPMs of puppet-dashboard. Add this to a repo file in /etc/yum.repos.d/
[puppetlabs] name=Puppet Labs Packages baseurl=http://yum.puppetlabs.com/base/ enabled=1 gpgcheck=1 gpgkey=http://yum.puppetlabs.com/RPM-GPG-KEY-reductive
Install with
yum install puppet-dashboard
Add a mysql database, then configure the database accordingly in /usr/share/puppet-dashboard/config/database.yml (the production database is key here, don't configure all 3 to use the same database!) If you're using a remote database, be sure to add a "host: <hostname>" entry.
Edit /etc/sysconfig/puppetmaster, and set the following:
PUPPETMASTER_EXTRA_OPTS="--reports puppet_dashboard"
(if there are any current reports configured, add puppet_dashboard with a comma)
Edit /etc/sysconfig/puppet-dashboard, and append:
RAILS_ENV=production
Then
cp /usr/share/puppet-dashboard/lib/puppet/puppet_dashboard.rb /usr/lib/ruby/site_ruby/1.8/puppet/reports/ /etc/init.d/puppetmaster restart chkconfig puppet-dashboard on /etc/init.d/puppet-dashboard start
If there is a firewall running on the puppetmaster server, open up TCP 3000
On the clients:
Add the following to [puppetd] in /etc/puppet/puppet.conf:
report = true
If puppet is being called from the command line or a script, you must simply append --report
to the command.
Usage
Simply visit http://puppetmaster:3000/ (currently no user authentication, that is in the works)
Problems
If you run into the following, you need to upgrade ruby, ruby-libs, etc. first:
Transaction Check Error: file /usr/lib/ruby/1.8/net/pop.rb from install of ruby-libs-1.8.5-5.el5_4.8 conflicts with file from package ruby-libs-1.8.5-5.el5_2.6