- Overview
- Setup
- Usage
- Number of Reports
- Offline Mode
- Set Default Environment
- Disable SELinux
- Development
This is the puppetboard puppet module.
Puppetboard is an open source puppet dashboard
https://github.com/voxpupuli/puppetboard
puppet module install puppet-puppetboard
Note Oracle linux 5 on puppet versions 4.6.0 to 4.7.1 has pip package problem which will cause an error trying to install puppetboard.
Note that this module no longer explicitly requires the puppetlabs apache module. If you want to use the apache functionality of this module you will have to specify that the apache module is installed with:
puppet module install puppetlabs-apache
On RedHat type systems, EPEL may also need to be configured; you can use the stahnma/epel module if you don't already have it configured.
This module also requires the git and virtualenv packages. These can be enabled in the module by:
class { 'puppetboard':
manage_git => true,
manage_virtualenv => true,
}
or by:
class { 'puppetboard':
manage_git => 'latest',
manage_virtualenv => 'latest',
}
Declare the base puppetboard manifest:
class { 'puppetboard': }NOTE: In order to have reports present in the dashboard, report storage must be enabled on the Puppet master node. This is not the default behavior, so it mush be enabled.
See https://docs.puppet.com/puppetdb/latest/connect_puppet_master.html#enabling-report-storage for instructions on report storage.
By default, puppetboard displays only 10 reports. This number can be controlled to set the number of reports to show.
class { 'puppetboard':
reports_count => 40
}
If you are running puppetboard in an environment which does not have network access to public CDNs, puppet board can load static assets (jquery, semantic-ui, tablesorter, etc) from the local web server instead of a CDN:
class { 'puppetboard':
offline_mode => true,
}by default, puppetboard defaults to "production" environment. This can be set to default to a different environment.
class { 'puppetboard':
default_environment => 'customers',
}or to default to "All environments":
class { 'puppetboard':
default_environment => '*',
}class { 'puppetboard':
manage_selinux => false,
}If you want puppetboard accessible through Apache and you're able to use the
official puppetlabs/apache Puppet module, this module contains two classes
to help configuration.
The first, puppetboard::apache::vhost, will use the apache::vhost
defined-type to create a full virtual host. This is useful if you want
puppetboard to be available from http://pboard.example.com:
# Configure Apache on this server
class { 'apache': }
class { 'apache::mod::wsgi': }
# Configure Puppetboard
class { 'puppetboard': }
# Access Puppetboard through pboard.example.com
class { 'puppetboard::apache::vhost':
vhost_name => 'pboard.example.com',
port => 80,
}The second, puppetboard::apache::conf, will create an entry in
/etc/apache2/conf.d (or /etc/httpd/conf.d, depending on your distribution).
This is useful if you simply want puppetboard accessible from
http://example.com/puppetboard:
# Configure Apache
# Ensure it does *not* purge configuration files
class { 'apache':
purge_configs => false,
mpm_module => 'prefork',
default_vhost => true,
default_mods => false,
}
class { 'apache::mod::wsgi': }
# Configure Puppetboard
class { 'puppetboard': }
# Access Puppetboard from example.com/puppetboard
class { 'puppetboard::apache::conf': }You can also relocate puppetboard to a sub-URI of a Virtual Host. This is useful if you want to reverse-proxy puppetboard, but are not planning on dedicating a domain just for puppetboard:
class { 'puppetboard::apache::vhost':
vhost_name => 'dashes.acme',
wsgi_alias => '/pboard',
}In this case puppetboard will be available (on the default) on http://dashes.acme:5000/pboard. You can then reverse-proxy to it like so:
Redirect /pboard /pboard/
ProxyPass /pboard/ http://dashes.acme:5000/pboard/
ProxyPassReverse /pboard/ http://dashes.acme:5000/pboard/Using the puppetlabs/apache module:
apache::vhost { 'example.acme':
port => '80',
docroot => '/var/www/html',
redirect_source => [ '/pboard' ],
redirect_dest => [ '/pboard/' ],
proxy_pass => [
{
'path' => '/pboard/',
'url' => 'http://dashes.acme:5000/pboard/',
},
],
}RedHat/CentOS has restrictions on the /etc/apache directory that require wsgi to be configured to use /var/run.
class { 'apache::mod::wsgi':
wsgi_socket_prefix => "/var/run/wsgi",
}
# Configure Apache on this server
class { 'apache': }
class { 'apache::mod::version': }
class { 'apache::mod::wsgi':
wsgi_socket_prefix => "/var/run/wsgi",
}
# Configure Puppetboard
class { 'puppetboard': }
# Access Puppetboard through pboard.example.com, port 8888
class { 'puppetboard::apache::vhost':
vhost_name => 'puppetboard.example.com',
port => '8888',
}If you want to use the latest version of Puppet Board you'll need to run Python 3.6+.
By default RHEL 7 has Python 2.7 installed, so you'll need to install a Python 3 and
the compatible version of mod_wsgi (the mod_wsgi module must be compiled to support
the specific version of Python you're running).
$mod_wsgi_package_name = 'rh-python36-mod_wsgi'
package { ['python3', 'python3-pip', 'python3-devel', 'python36-virtualenv']:
ensure => present,
}
# configure apache
class { 'apache':
purge_configs => false,
mpm_module => 'prefork',
default_vhost => false,
default_mods => false,
}
# configure mod_wsgi for python3
class { 'apache::mod::wsgi':
mod_path => 'modules/mod_rh-python36-wsgi.so',
package_name => $mod_wsgi_package_name,
wsgi_socket_prefix => '/var/run/wsgi',
}
# create symlinks from the isolated Red Hat directory into the
# standard Apache paths so that it can pick up the module and config
file { '/etc/httpd/conf.modules.d/10-rh-python36-wsgi.conf':
ensure => 'link',
target => '/opt/rh/httpd24/root/etc/httpd/conf.modules.d/10-rh-python36-wsgi.conf',
require => Package[$mod_wsgi_package_name],
}
file { '/usr/lib64/httpd/modules/mod_rh-python36-wsgi.so':
ensure => 'link',
target => '/opt/rh/httpd24/root/usr/lib64/httpd/modules/mod_rh-python36-wsgi.so ',
require => Package[$mod_wsgi_package_name],
}
class { 'puppetboard':
# use python3 when setting up the virtualenv for puppetboard
virtualenv_python => '3',
# specify other parameters here
}NOTE Below are the Yum repos needed for the various packages above.
On CentOS you'll need to package centos-release-scl-rh or manage
the SCL repos with the bodgit/scl module.
| OS | package | repo |
|---|---|---|
| RHEL 7 | python3 |
rhel-7-server-rpms |
| RHEL 7 | python3-pip |
rhel-7-server-rpms |
| RHEL 7 | python3-devel |
rhel-7-server-optional-rpms |
| RHEL 7 | python36-virtualenv |
EPEL |
| RHEL 7 | rh-python36-mod_wsgi |
rhel-server-rhscl-7-rpms |
| CentOS 7 | python3 |
base/7 |
| CentOS 7 | python3-pip |
base/7 |
| CentOS 7 | python3-devel |
base/7 |
| CentOS 7 | python36-virtualenv |
EPEL |
| CentOS 7 | rh-python36-mod_wsgi |
centos-sclo-rh |
If you would like to use certificate auth into the PuppetDB service you must configure puppetboard to use a client certificate and private key.
You have two options for the source of the client certificate & key:
- Generate a new certificate, signed by the puppetmaster CA
- Use the existing puppet client certificate
If you choose option 1, generate the new certificates on the CA puppet master as follows:
sudo puppet cert generate puppetboard.example.com
Note: this name cannot conflict with an existing certificate name.
The new certificate and private key can be found in $certdir/.pem and $privatekeydir/.pem on the CA puppet master. If you are not running puppetboard on the CA puppet master you will need to copy the certificate and key to the node running puppetboard.
Here's an example, using new certificates:
$ssl_dir = '/var/lib/puppetboard/ssl'
$puppetboard_certname = 'puppetboard.example.com'
class { 'puppetboard':
manage_virtualenv => true,
puppetdb_host => 'puppetdb.example.com',
puppetdb_port => 8081,
puppetdb_key => "${ssl_dir}/private_keys/${puppetboard_certname}.pem",
puppetdb_ssl_verify => "${ssl_dir}/certs/ca.pem",
puppetdb_cert => "${ssl_dir}/certs/${puppetboard_certname}.pem",
}If you are re-using the existing puppet client certificates, they will already exist on the node (assuming puppet has been run and the client cert signed by the puppet master). However, the puppetboaard user will not have permission to read the private key unless you add it to the puppet group.
Here's a complete example, re-using the puppet client certs:
$ssl_dir = $::settings::ssldir
$puppetboard_certname = $::certname
class { 'puppetboard':
groups => 'puppet',
manage_virtualenv => true,
puppetdb_host => 'puppetdb.example.com',
puppetdb_port => 8081,
puppetdb_key => "${ssl_dir}/private_keys/${puppetboard_certname}.pem",
puppetdb_ssl_verify => "${ssl_dir}/certs/ca.pem",
puppetdb_cert => "${ssl_dir}/certs/${puppetboard_certname}.pem",
}Note that both the above approaches only work if you have the Puppet CA root certificate added to the root certificate authority file used by your operating system. If you want to specify the location to the Puppet CA file ( you probably do) you have to use the syntax below. Currently this is a bit of a gross hack, but it's an open issue to resolve it in the Puppet module:
$ssl_dir = $::settings::ssldir
$puppetboard_certname = $::certname
class { 'puppetboard':
groups => 'puppet',
manage_virtualenv => true,
puppetdb_host => 'puppetdb.example.com',
puppetdb_port => 8081,
puppetdb_key => "${ssl_dir}/private_keys/${puppetboard_certname}.pem",
puppetdb_ssl_verify => "${ssl_dir}/certs/ca.pem",
puppetdb_cert => "${ssl_dir}/certs/${puppetboard_certname}.pem",
}As of PuppetDB 6.9.1 the /metrics/v2 API is only accessible on the loopback/localhost
interface of the PuppetDB server. This requires you to run puppetboard locally on
that host and configure puppetdb_host to 127.0.0.1:
$ssl_dir = $::settings::ssldir
$puppetboard_certname = $::certname
class { 'puppetboard':
groups => 'puppet',
manage_virtualenv => true,
puppetdb_host => '127.0.0.1',
puppetdb_port => 8081,
puppetdb_key => "${ssl_dir}/private_keys/${puppetboard_certname}.pem",
puppetdb_ssl_verify => "${ssl_dir}/certs/ca.pem",
puppetdb_cert => "${ssl_dir}/certs/${puppetboard_certname}.pem",
}NOTE In order for SSL to verify properly in this setup, you'll need your
Puppet SSL certificate to have an IP Subject Alternative Name setup
for 127.0.0.1, otherwise the certificate verification will fail.
You can set this up in your puppet.conf with the dns_alt_names
configuration option, documented here.
[main]
dns_alt_names = puppetdb,puppetdb.domain.tld,puppetboard,puppetboard.domain.tld,IP:127.0.0.1NOTE If you need to regenerate your existing cert to add DNS Alt Names follow the documentation here:
# remove the existing agent certs
puppetserver ca clean --certname <CERTNAME_OF_YOUR_PUPPETDB>
puppet ssl clean
# stop our services
puppet resource service puppetserver ensure=stopped
puppet resource service puppetdb ensure=stopped
# regenerate our cert
puppetserver ca generate --certname <CERTNAME> --subject-alt-names puppetdb,puppetdb.domain.tld,puppetboard,puppetboard.domain.tld,IP:127.0.0.1 --ca-client
# copy the cert into the PuppetDB directory
cp /etc/puppetlabs/puppet/ssl/certs/<CERTNAME>.pem /etc/puppetlabs/puppetdb/ssl/public.pem
cp /etc/puppetlabs/puppet/ssl/private_keys/<CERTNAME>.pem /etc/puppetlabs/puppetdb/ssl/private.pem
# restart our services
puppet resource service puppetdb ensure=running
puppet resource service puppetserver ensure=runningThis module is maintained by Vox Pupuli. Voxpupuli welcomes new contributions to this module, especially those that include documentation and rspec tests. We are happy to provide guidance if necessary.
Please see CONTRIBUTING for more details.
Please log tickets and issues on github.
- Spencer Krum [email protected]
- Voxpupuli Team
- The core of this module was based on Hunter Haugen's puppetboard-vagrant repo.