Version information
Start using this module
Add this module to your Puppetfile:
mod 'nibalizer-puppetboard', '2.5.0'
Learn more about managing modules with a PuppetfileDocumentation
puppetboard
This is the puppetboard puppet module.
Puppetboard is a puppet dashboard
https://github.com/nedap/puppetboard
Installation
puppet module install nibalizer-puppetboard
Dependencies
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
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',
}
Usage
Declare the base puppetboard manifest:
class { 'puppetboard': }
Apache
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': }
Apache (with Reverse Proxy)
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/
ReverseProxy /pboard/ http://dashes.acme:5000/pboard/
ProxyPassReverse /pboard/ http://dashes.acme:5000/pboard/
Redhat
RedHat 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",
}
Apache, RedHat and a non-standard port
# Configure Apache on this server
class { 'apache': }
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',
}
Using SSL to the PuppetDB host
If you would like to use certificate auth into the PuppetDB service, use any of the configurations from above and set the following parameters to your puppetboard class.
class { 'puppetboard':
manage_virtualenv => true,
puppetdb_host => 'puppet.example.com',
puppetdb_port => '8081',
puppetdb_key => "/var/lib/puppet/ssl/private_keys/${::certname}.pem",
puppetdb_ssl => 'True',
puppetdb_cert => "/var/lib/puppet/ssl/certs/${::certname}.pem",
}
Note that the above only works 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:
class { 'puppetboard':
manage_virtualenv => true,
puppetdb_host => 'puppet.example.com',
puppetdb_port => '8081',
puppetdb_key => "/var/lib/puppet/ssl/private_keys/${::certname}.pem",
puppetdb_ssl => "'/var/lib/puppet/ssl/certs/ca.pem'",
puppetdb_cert => "/var/lib/puppet/ssl/certs/${::certname}.pem",
}
License
Apache 2
Contact
Email: krum.spencer@gmail.com IRC: #puppetboard and #puppet on freenode
Attribution
The core of this module was based on Hunter Haugen's puppetboard-vagrant repo.
Support
Please log tickets and issues on github.
Dependencies
- puppetlabs/stdlib (>= 3.0.0)
- stankevich/python (>= 1.1.4)
- puppetlabs/vcsrepo (>= 0.1.2)