# Puppetboard
[](https://pypi.org/project/puppetboard/)
[](https://pypi.org/project/puppetboard/)
/badge.svg)
[](https://codecov.io/gh/voxpupuli/puppetboard)
[](http://voxpupuli.org)
Puppetboard is a web interface to [PuppetDB](https://puppet.com/docs/puppetdb/latest/index.html) aiming to replace
the reporting functionality of [Puppet Enterprise console (previously: Puppet Dashboard)](https://puppet.com/docs/pe/latest/console_accessing.html)
for the open source Puppet.
See [more screenshots here](#more-screenshots).
## Table of Contents
* [Requirements](#requirements)
* [Installation](#installation)
* [Configuration](#configuration)
* [Getting Help](#getting-help)
* [Contributing](#contributing)
* [Legal](#legal)
## Requirements<a id="requirements"></a>
* PuppetDB v. 5.2-8.*
* (**Note**: PuppetDB 8.1.0 is not supported because of [this bug](https://github.com/puppetlabs/puppetdb/issues/3866). Please update to 8.1.1+.)
* Python 3.9-3.13 or Docker
## Installation<a id="installation"></a>
Puppetboard is packaged and available on PyPI.
### With Puppet module
There is a [Puppet module](https://forge.puppetlabs.com/puppet/puppetboard) originally written by
[Spencer Krum](https://github.com/nibalizer) and currently maintained by [Voxpupuli](https://voxpupuli.org/)
that takes care of installing the Puppetboard for you.
To see how to get it working with RedHat/Centos 7 check out these [docs](https://github.com/voxpupuli/puppetboard/blob/master/docs/EL7.md).
### Using Docker
We provide an official Docker image in:
* [GitHub Container Registry](https://github.com/orgs/voxpupuli/packages/container/package/puppetboard),
* [Dockerhub](https://hub.docker.com/r/voxpupuli/puppetboard).
You can run the app on your PuppetDB host with this command:
```bash
docker run -it \
-e PUPPETDB_HOST=localhost \
-e PUPPETDB_PORT=8080 \
-e SECRET_KEY=XXXXXXXX \
--net=host \
ghcr.io/voxpupuli/puppetboard
```
Note: you must provide a secret key! Generate one for example by running `ruby -e "require 'securerandom'; puts SecureRandom.hex(32)"`.
Optionally you can set `PUPPETBOARD_URL_PREFIX` env variable to a value like `/puppetboard` to run the app under a URL prefix.
You can use the following Puppet Code to have Puppetboard managed by Puppet:
```puppet
include docker
docker::image { 'ghcr.io/voxpupuli/puppetboard': }
docker::run { 'puppetboard':
image => 'ghcr.io/voxpupuli/puppetboard',
env => [
'PUPPETDB_HOST=127.0.0.1',
'PUPPETDB_PORT=8080',
'PUPPETBOARD_PORT=8088',
'SECRET_KEY=XXXXXXXX',
],
net => 'host',
}
```
If you want to have all features enabled, you must use SSL talking to PuppetDB:
```puppet
file { '/etc/puppetboard':
ensure => directory,
}
file { '/etc/puppetboard/key.pem':
ensure => file,
mode => '0644',
source => "/etc/puppetlabs/puppet/ssl/private_keys/${facts['networking']['fqdn']}.pem",
}
file { '/etc/puppetboard/cert.pem':
ensure => file,
mode => '0644',
source => "/etc/puppetlabs/puppet/ssl/certs/${facts['networking']['fqdn']}.pem",
}
include docker
docker::image { 'ghcr.io/voxpupuli/puppetboard': }
docker::run { 'puppetboard':
image => 'ghcr.io/voxpupuli/puppetboard',
volumes => ['/etc/puppetboard:/etc/puppetboard:ro'],
env => [
'PUPPETDB_HOST=puppet', # this must be the certname or DNS_ALT_NAME of the PuppetDB host
'PUPPETDB_PORT=8081',
'PUPPETBOARD_PORT=8080',
'ENABLE_CATALOG=true',
'PUPPETDB_SSL_VERIFY=false',
'PUPPETDB_KEY=/etc/puppetboard/key.pem',
'PUPPETDB_CERT=/etc/puppetboard/cert.pem',
'SECRET_KEY=XXXXXXXX',
'DEFAULT_ENVIRONMENT=*',
],
net => 'host',
}
```
Within an air gapped environment you want to load all content from your local puppetboard web service.
Add: `'OFFLINE_MODE=true',` to the `env` parameter list of the `docker::run` Puppet type.
We also provide the Dockerfile, so you can build the image yourself:
```bash
docker build -t puppetboard .
```
### Using Red Hat OpenShift
The included OpenShift template file helps in the creation of the Puppetboard web interface by adopting a source-to-image methodology.
You can run the app on your OpenShift environment with these commands:
```bash
# Import the template into OpenShift
oc create -f puppetboard-s2i-template.yaml
# Create the Puppetboard application and supporting Pods.
oc new-app -p PUPPETDB_HOST=puppetdb.fqdn.com \
--template=puppetboard-template
```
This will build a puppetboard application that queries a PuppetDB database at puppetdb.fqdn.com.
Optionally you can set other environment variables to fit your needs:
```bash
oc new-app -p PUPPETDB_HOST=puppetdb.fqdn.com \
-p PUPPETDB_PORT=3456 \
-p PUPPETBOARD_SOURCE_REPOSITORY_REF="v5.4.0" \
-p PUPPETBOARD_SERVICE_NAME=prod_puppetboard \
--template=puppetboard-template
```
This will build Puppetboard version v5.4.0 that queries the PuppetDB server on TCP/3456.
The following is a list of OpenShift parameters that you can pass to the ``oc`` command to customize the application:
- `PUPPETBOARD_SERVICE_NAME`: This is the name that will be used for application. Deployment Configs, Build Configs
Services, Routes and Pods will use this value for their names as well. You can instantiate multiple applications
by using different names in ``oc new-app``. Defaults to 'puppetboard'.
- `PUPPETDB_HOST`: This is the name of the PuppetDB host that Puppetboard will query for its reports. Defaults to 'puppetdb'.
- `PUPPETDB_PORT`: This is tcp port on the `PUPPETDB_HOST` for queries. Defaults to '8080'.
- `PUPPETBOARD_SECRET_KEY`: Identical to `SECRET_KEY` (below). Defaults to 'Secr3t_K3y'.
- `PUPPETBOARD_PORT`: The TCP port on which the Puppetboard docker image presents the web interface. This is not the
user-facing web interface. Rather, it's the port that the OpenShift route forwards **to**.
- `SERVICE_PORT`: The TCP port on which the Puppetboard service offers its user-facing web interface on OpenShift. Defaults to '80'.
- `PUPPETBOARD_SOURCE_REPOSITORY_URL`: The URL to the Puppetboard repository. Defaults to 'https://github.com/voxpupuli/puppetboard.git'.
- `PUPPETBOARD_SOURCE_REPOSITORY_REF`: The branch/tag/ref for Puppetboard. Defaults to 'master'.
### From a package
Actively maintained packages:
* [FreeBSD](https://www.freshports.org/www/py-puppetboard/)
maintained by [Romain Tartière](https://github.com/smortex)
* [OpenBSD](https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/www/puppetboard/)
maintained by [Sebastian Reitenbach](https://github.com/buzzdeee)
### Manually
You can also install the package from PyPI and configure a WSGI-capable application server to serve it.
We recommend using virtualenv to provide a separate environment for the app.
```bash
virtualenv -p python3 venv
. venv/bin/activate
pip install puppetboard
```
Please see [an article about more deployment setups here](https://github.com/voxpupuli/puppetboard/blob/master/docs/Deployment-setups.md).
## Configuration<a id="configuration"></a>
### Puppet agents
The default value of `usecacheonfailure = true` configuration setting for Puppet agents causes Puppet runs to always succeed,
event if there are catalog compilation failures f.e. because of a syntax error in your code. This is because in such
cases with this setting Puppet will just use a cached working catalog and report the run to PuppetDB as successful.
(Although with an error visible in the Puppet run log.)
Therefore, to show the nodes with a catalog compilation as failed in Puppetboard you need to set
`usecacheonfailure = false` in your nodes' `puppet.conf`.
### PuppetDB
Of course you need to configure your Puppet Server to store the Puppet run reports in PuppetDB.
If you haven't done that already please follow the [PuppetDB documentation](https://puppet.com/docs/puppetdb/latest/connect_puppet_server.html)
about this.
If you run Puppetboard on a different host than PuppetDB then you may want to configure the certificate
allow-list for which certificates are allowed to access data from PuppetDB.
Please read more about this feature in the [PuppetDB documentation here](https://puppet.com/docs/puppetdb/latest/configure.html#certificate-allowlist).
### App settings
Puppetboard will look for a file pointed at by the `PUPPETBOARD_SETTINGS` environment variable.
The file has to be identical to
[default_settings.py](https://github.com/voxpupuli/puppetboard/blob/master/puppetboard/default_settings.py)
but should only override the settings you need changed.
If you run PuppetDB and Puppetboard on the same machine the default settings provided will be enough to get you started
and you won't need a custom settings file.
Assuming your webserver and PuppetDB machine are not identical you will at least have to change the following settings:
- `PUPPETDB_HOST`
- `PUPPETDB_PORT`
By default PuppetDB requires SSL to be used when a non-local client wants to connect. Therefore you'll also have to
supply the following settings:
- `PUPPETDB_SSL_VERIFY = True`
- `PUPPETDB_KEY = /path/to/private/keyfile.pem`
- `PUPPETDB_CERT = /path/to/public/keyfile.crt`
When using the Puppetboard Docker image, you may also pass Puppetboard it's certificate contents via these environment
variables, either as a multiline string or pre-base64 encoded. This can be useful where the certificate is stored in a
secrets store i.e. AWS SSM Parameter Store.
```
PUPPETDB_CERT="-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----"
```
```
PUPPETDB_CERT=LS0tLS1CRUdJTiBSU0EgUFJJVkFURSBLRVktLS0tLQouLi4KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQ==
```
For information about how to generate the correct keys please refer to the
[pypuppetdb documentation](https://pypuppetdb.readthedocs.io/en/latest/connecting.html#ssl). Alternatively it is possible
to explicitly specify the protocol to be used setting the `PUPPETDB_PROTO` variable.
Other settings that might be interesting, in no particular order:
- `SECRET_KEY`: set this to a long string, **the same for each application replica**, and keep it secret. Refer to
[Flask documentation](https://flask.palletsprojects.com/en/2.1.x/quickstart/#sessions), section
"How to generate good secret keys" for more info. Cannot be an empty string, which is the default.
- `FAVORITE_ENVS`: an ordered list of Puppet environment names that will be shown immediately after "All Environments"
and before other environments (which are sorted by name) in the dropdown for choosing the environment shown
in the top-right of the UI. Environments listed here that do not really exist in your deployment are silently ignored.
- `SHOW_ERROR_AS`: `friendly` or `raw`. The former makes Puppet run errors in Report and Failures views shown
in a modified, (arguably) more user-friendly form. The latter shows them as they are.
Defaults to `friendly`.
- `CODE_PREFIX_TO_REMOVE`: what code path that should be shortened in "Friendly errors" to "…" for readability.
A regexp. Defaults to `/etc/puppetlabs/code/environments(/.*?/modules)?`.
- `PUPPETDB_TIMEOUT`: Defaults to 20 seconds, but you might need to increase this value. It depends on how big the
results are when querying PuppetDB. This behaviour will change in a future release when pagination will be introduced.
- `UNRESPONSIVE_HOURS`: The amount of hours since the last check-in after which a node is considered unresponsive.
- `LOGLEVEL`: A string representing the loglevel. It defaults to `'info'` but can be changed to `'warning'` or
`'critical'` for less verbose logging or `'debug'` for more information.
- `ENABLE_QUERY`: Defaults to `True` causing a Query tab to show up in the web interface allowing users to write
and execute arbitrary queries against a set of endpoints in PuppetDB. Change this to `False` to disable this.
See `ENABLED_QUERY_ENDPOINTS` to fine-tune which endpoints are allowed.
- `ENABLED_QUERY_ENDPOINTS`: If `ENABLE_QUERY` is `True`, allow to fine tune the endpoints of PuppetDB APIs that
can be queried. It must be a list of strings of PuppetDB endpoints for which the query is enabled.
See the `QUERY_ENDPOINTS` constant in the `puppetboard.app` module for a list of the available endpoints.
- `GRAPH_TYPE`: Specify the type of graph to display. Default is
pie, other good option is donut. Other choices can be found here:
[C3.js documentation](https://c3js.org/examples.html#chart)
- `GRAPH_FACTS`: A list of fact names to tell PuppetBoard to generate a pie-chart on the fact page. With some fact
values being unique per node, like ipaddress, uuid, and serial number, as well as structured facts it was no longer
feasible to generate a graph for everything.
- `INVENTORY_FACTS`: A list of tuples that serve as the column header and the fact name to search for to create
the inventory page. If a fact is not found for a node then `undef` is printed.
- `INVENTORY_FACT_TEMPLATES`: A mapping between fact name and jinja template to customize display
- `ENABLE_CATALOG`: If set to `True` allows the user to view a node's latest catalog. This includes all managed
resources, their file-system locations and their relationships, if available. Defaults to `False`.
- `REFRESH_RATE`: Defaults to `30` the number of seconds to wait until the index page is automatically refreshed.
- `DEFAULT_ENVIRONMENT`: Defaults to `'production'`, as the name suggests, load all information filtered by this
environment value.
- `REPORTS_COUNT`: Defaults to `10` the limit of the number of reports to load on the node or any reports page.
- `OFFLINE_MODE`: If set to `True` load static assets (jquery, semantic-ui, etc) from the local web server instead
of a CDN. Defaults to `False`.
- `DAILY_REPORTS_CHART_ENABLED`: Enable the use of daily chart graphs when looking at dashboard and node view.
- `DAILY_REPORTS_CHART_DAYS`: Number of days to show history for on the daily report graphs.
- `DISPLAYED_METRICS`: Metrics to show when displaying node summary. Example: `'resources.total'`, `'events.noop'`.
- `TABLE_COUNT_SELECTOR`: Configure the dropdown to limit number of hosts to show per page.
- `LITTLE_TABLE_COUNT`: Default number of reports to show when when looking at a node.
- `NORMAL_TABLE_COUNT`: Default number of nodes to show when displaying reports and catalog nodes.
- `LOCALISE_TIMESTAMP`: If set to `True` then timestamps are shown using your browser's timezone. Otherwise UTC is used. Defaults to `True`.
- `WITH_EVENT_NUMBERS`: If set to `True` then Overview and Nodes list shows exact number of changed resources
in the last report. Otherwise shows only 'some' string if there are resources with given status. Setting this
to `False` gives performance benefits, especially in big Puppet environments (more than few hundreds of nodes).
Defaults to `True`.
- `ENABLE_CLASS`: If set to `True` allows the user to view the number of resource events (number of changed resources in the last report) grouped by class.
The resource events are grouped by their status ('failure', 'success', 'noop').
- `CLASS_EVENTS_STATUS_COLUMNS`: A mapping between the status of the resource events and the name of the columns of the table to display.
- `CACHE_TYPE`: Specifies which type of caching object to use when `SCHEDULER_ENABLED` is set to `True`.
The cache is used for the classes view (`ENABLE_CLASS` is set to `True`) which requires parsing the events of all the latest reports to group them by Puppet class.
If the last report is present in the cache, we do not parse the events, which avoids unnecessary processing.
If you configure more than one worker, you must use a shared backend (e.g. `MemcachedCache`) to allow the sharing of the cache between the processes.
Indeed, the `SimpleCache` type does not allow sharing the cache between processes, it uses the process memory to store the cache.
Defaults to `SimpleCache`.
- `CACHE_DEFAULT_TIMEOUT`: Cache lifetime in second. Defaults to `3600`.
- `SCHEDULER_ENABLED`: If set to `True` then a scheduler instance is created in order to execute scheduled jobs. Defaults to `False`.
- `SCHEDULER_JOBS`: List of the scheduled jobs to trigger within a worker.
A job can for example be used to compute a result to be cached. This is the case for the classes view which uses a job to pre-compute at regular intervals the results to be displayed.
Each scheduled job must contain the following fields: `id`, `func`, `trigger`, `seconds`.
- `SCHEDULER_LOCK_BIND_PORT`: Specifies an available port that allows a single worker to listen on it.
This allows to configure scheduled jobs in a single worker. Defaults to `49100`.
## Getting Help<a id="getting-help"></a>
For questions or bug reports you can file an [issue](https://github.com/voxpupuli/puppetboard/issues).
## Contributing<a id="contributing"></a>
### Development
Puppetboard relies on the [pypuppetdb](https://pypi.org/project/pypuppetdb/) library to fetch data from PuppetDB
and is built with the help of the [Flask](https://flask.palletsprojects.com) microframework.
If you wish to hack on Puppetboard you should fork/clone the Github repository and then install the requirements through:
```bash
pip install --upgrade wheel setuptools
python setup.py develop
pip install --upgrade -r requirements-test.txt
mypy --install-types --non-interactive puppetboard/ test/
```
You're advised to do this inside a virtualenv specifically created to work on Puppetboard as to not pollute your global Python installation.
You can run the tests with:
```bash
pytest --cov=. --cov-report=xml --strict-markers --mypy puppetboard test
pylint --errors-only puppetboard test
```
You can run the app it in development mode by simply executing:
```bash
flask run
```
You can specify listening host and port with environment variables or command line otions:
```bash
export FLASK_RUN_HOST=0.0.0.0
export FLASK_RUN_PORT=8000
flask run
```
or
```bash
flask run --host '0.0.0.0' --port '8000'
```
Use `PUPPETBOARD_SETTINGS` to change the different settings or patch `default_settings.py` directly.
Take care not to include your local changes on that file when submitting patches for Puppetboard.
Place a `settings.py` file inside the base directory of the git repository that will be used, if the environment
variable is not set.
We welcome contributions to this project. However, there are a few ground rules contributors should be aware of.
### License
This project is licensed under the Apache v2.0 License. As such, your contributions, once accepted, are automatically
covered by this license.
### Commit messages
Write decent commit messages. Don't use swear words and refrain from uninformative commit messages as 'fixed typo'.
The preferred format of a commit message:
docs/quickstart: Fixed a typo in the Nodes section.
If needed, elaborate further on this commit. Feel free to write a
complete blog post here if that helps us understand what this is
all about.
Fixes #4 and resolves #2.
If you'd like a more elaborate guide on how to write and format your commit messages have a look at [this post
by Tim Pope](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
### Build a release
please see: [RELEASE.md](RELEASE.md)
## More Screenshots<a id="more-screenshots"></a>
* Overview / Index / Homepage
* Nodes view, all active nodes
* Single node page / overview
* Report view
* Facts view
* Single fact, with graphs
* All nodes that have this fact with that value
* Query view - results as table
* Query view - results as JSON
* Metrics view
* Single metric
* Inventory view
* Classes view, group the resource events of the last reports by Puppet class
* Class view, list the nodes with almost one resource event for a given class
# Legal<a id="legal"></a>
The app code is licensed under the [Apache License, Version 2.0](./LICENSE).
The favicon has been created based on the icon created by [Jonathan Coutiño](https://thenounproject.com/ralts01/)
under the [Attribution 3.0 Unported (CC BY 3.0) license](https://creativecommons.org/licenses/by/3.0/),
downloaded from the [Noun Project](https://thenounproject.com).
Raw data
{
"_id": null,
"home_page": "https://github.com/voxpupuli/puppetboard",
"name": "puppetboard",
"maintainer": null,
"docs_url": null,
"requires_python": "<4.0,>=3.9",
"maintainer_email": null,
"keywords": "puppet, puppetdb, puppetboard",
"author": "Vox Pupuli",
"author_email": "voxpupuli@groups.io",
"download_url": "https://files.pythonhosted.org/packages/79/8e/acd9a26841387a6f0a5905b5b9944fb1a857d873f749eaa13b30c9e137fb/puppetboard-6.0.1.tar.gz",
"platform": null,
"description": "# Puppetboard\n\n[](https://pypi.org/project/puppetboard/)\n[](https://pypi.org/project/puppetboard/)\n/badge.svg)\n[](https://codecov.io/gh/voxpupuli/puppetboard)\n[](http://voxpupuli.org)\n\n\nPuppetboard is a web interface to [PuppetDB](https://puppet.com/docs/puppetdb/latest/index.html) aiming to replace\nthe reporting functionality of [Puppet Enterprise console (previously: Puppet Dashboard)](https://puppet.com/docs/pe/latest/console_accessing.html)\nfor the open source Puppet.\n\n\n\nSee [more screenshots here](#more-screenshots).\n\n## Table of Contents\n\n* [Requirements](#requirements)\n* [Installation](#installation)\n* [Configuration](#configuration)\n* [Getting Help](#getting-help)\n* [Contributing](#contributing)\n* [Legal](#legal)\n\n## Requirements<a id=\"requirements\"></a>\n\n* PuppetDB v. 5.2-8.*\n * (**Note**: PuppetDB 8.1.0 is not supported because of [this bug](https://github.com/puppetlabs/puppetdb/issues/3866). Please update to 8.1.1+.)\n* Python 3.9-3.13 or Docker\n\n## Installation<a id=\"installation\"></a>\n\nPuppetboard is packaged and available on PyPI.\n\n### With Puppet module\n\nThere is a [Puppet module](https://forge.puppetlabs.com/puppet/puppetboard) originally written by\n [Spencer Krum](https://github.com/nibalizer) and currently maintained by [Voxpupuli](https://voxpupuli.org/)\nthat takes care of installing the Puppetboard for you.\n\nTo see how to get it working with RedHat/Centos 7 check out these [docs](https://github.com/voxpupuli/puppetboard/blob/master/docs/EL7.md).\n\n### Using Docker\n\nWe provide an official Docker image in:\n* [GitHub Container Registry](https://github.com/orgs/voxpupuli/packages/container/package/puppetboard),\n* [Dockerhub](https://hub.docker.com/r/voxpupuli/puppetboard).\n\nYou can run the app on your PuppetDB host with this command:\n\n```bash\ndocker run -it \\\n -e PUPPETDB_HOST=localhost \\\n -e PUPPETDB_PORT=8080 \\\n -e SECRET_KEY=XXXXXXXX \\\n --net=host \\\n ghcr.io/voxpupuli/puppetboard\n```\nNote: you must provide a secret key! Generate one for example by running `ruby -e \"require 'securerandom'; puts SecureRandom.hex(32)\"`.\n\nOptionally you can set `PUPPETBOARD_URL_PREFIX` env variable to a value like `/puppetboard` to run the app under a URL prefix.\n\nYou can use the following Puppet Code to have Puppetboard managed by Puppet:\n\n```puppet\ninclude docker\n\ndocker::image { 'ghcr.io/voxpupuli/puppetboard': }\n\ndocker::run { 'puppetboard':\n image => 'ghcr.io/voxpupuli/puppetboard',\n env => [\n 'PUPPETDB_HOST=127.0.0.1',\n 'PUPPETDB_PORT=8080',\n 'PUPPETBOARD_PORT=8088',\n 'SECRET_KEY=XXXXXXXX',\n ],\n net => 'host',\n}\n```\n\nIf you want to have all features enabled, you must use SSL talking to PuppetDB:\n\n```puppet\nfile { '/etc/puppetboard':\n ensure => directory,\n}\nfile { '/etc/puppetboard/key.pem':\n ensure => file,\n mode => '0644',\n source => \"/etc/puppetlabs/puppet/ssl/private_keys/${facts['networking']['fqdn']}.pem\",\n}\nfile { '/etc/puppetboard/cert.pem':\n ensure => file,\n mode => '0644',\n source => \"/etc/puppetlabs/puppet/ssl/certs/${facts['networking']['fqdn']}.pem\",\n}\n\ninclude docker\n\ndocker::image { 'ghcr.io/voxpupuli/puppetboard': }\n\ndocker::run { 'puppetboard':\n image => 'ghcr.io/voxpupuli/puppetboard',\n volumes => ['/etc/puppetboard:/etc/puppetboard:ro'],\n env => [\n 'PUPPETDB_HOST=puppet', # this must be the certname or DNS_ALT_NAME of the PuppetDB host\n 'PUPPETDB_PORT=8081',\n 'PUPPETBOARD_PORT=8080',\n 'ENABLE_CATALOG=true',\n 'PUPPETDB_SSL_VERIFY=false',\n 'PUPPETDB_KEY=/etc/puppetboard/key.pem',\n 'PUPPETDB_CERT=/etc/puppetboard/cert.pem',\n 'SECRET_KEY=XXXXXXXX',\n 'DEFAULT_ENVIRONMENT=*',\n ],\n net => 'host',\n}\n```\n\nWithin an air gapped environment you want to load all content from your local puppetboard web service.\nAdd: `'OFFLINE_MODE=true',` to the `env` parameter list of the `docker::run` Puppet type.\n\nWe also provide the Dockerfile, so you can build the image yourself:\n```bash\ndocker build -t puppetboard .\n```\n\n### Using Red Hat OpenShift\n\nThe included OpenShift template file helps in the creation of the Puppetboard web interface by adopting a source-to-image methodology.\n\nYou can run the app on your OpenShift environment with these commands:\n\n```bash\n# Import the template into OpenShift\noc create -f puppetboard-s2i-template.yaml \n\n# Create the Puppetboard application and supporting Pods.\noc new-app -p PUPPETDB_HOST=puppetdb.fqdn.com \\\n --template=puppetboard-template\n```\n\nThis will build a puppetboard application that queries a PuppetDB database at puppetdb.fqdn.com.\n\nOptionally you can set other environment variables to fit your needs:\n\n```bash\noc new-app -p PUPPETDB_HOST=puppetdb.fqdn.com \\\n -p PUPPETDB_PORT=3456 \\\n -p PUPPETBOARD_SOURCE_REPOSITORY_REF=\"v5.4.0\" \\\n -p PUPPETBOARD_SERVICE_NAME=prod_puppetboard \\\n --template=puppetboard-template\n```\n\nThis will build Puppetboard version v5.4.0 that queries the PuppetDB server on TCP/3456.\n\nThe following is a list of OpenShift parameters that you can pass to the ``oc`` command to customize the application:\n\n- `PUPPETBOARD_SERVICE_NAME`: This is the name that will be used for application. Deployment Configs, Build Configs \n Services, Routes and Pods will use this value for their names as well. You can instantiate multiple applications\n by using different names in ``oc new-app``. Defaults to 'puppetboard'.\n- `PUPPETDB_HOST`: This is the name of the PuppetDB host that Puppetboard will query for its reports. Defaults to 'puppetdb'.\n- `PUPPETDB_PORT`: This is tcp port on the `PUPPETDB_HOST` for queries. Defaults to '8080'.\n- `PUPPETBOARD_SECRET_KEY`: Identical to `SECRET_KEY` (below). Defaults to 'Secr3t_K3y'.\n- `PUPPETBOARD_PORT`: The TCP port on which the Puppetboard docker image presents the web interface. This is not the\n user-facing web interface. Rather, it's the port that the OpenShift route forwards **to**. \n- `SERVICE_PORT`: The TCP port on which the Puppetboard service offers its user-facing web interface on OpenShift. Defaults to '80'.\n- `PUPPETBOARD_SOURCE_REPOSITORY_URL`: The URL to the Puppetboard repository. Defaults to 'https://github.com/voxpupuli/puppetboard.git'.\n- `PUPPETBOARD_SOURCE_REPOSITORY_REF`: The branch/tag/ref for Puppetboard. Defaults to 'master'.\n\n### From a package\n\nActively maintained packages:\n\n* [FreeBSD](https://www.freshports.org/www/py-puppetboard/)\n maintained by [Romain Tarti\u00e8re](https://github.com/smortex)\n* [OpenBSD](https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/www/puppetboard/)\n maintained by [Sebastian Reitenbach](https://github.com/buzzdeee)\n\n### Manually\n\nYou can also install the package from PyPI and configure a WSGI-capable application server to serve it.\n\nWe recommend using virtualenv to provide a separate environment for the app.\n\n```bash\nvirtualenv -p python3 venv\n. venv/bin/activate\npip install puppetboard\n```\n\nPlease see [an article about more deployment setups here](https://github.com/voxpupuli/puppetboard/blob/master/docs/Deployment-setups.md).\n\n## Configuration<a id=\"configuration\"></a>\n\n### Puppet agents\n\nThe default value of `usecacheonfailure = true` configuration setting for Puppet agents causes Puppet runs to always succeed,\nevent if there are catalog compilation failures f.e. because of a syntax error in your code. This is because in such\ncases with this setting Puppet will just use a cached working catalog and report the run to PuppetDB as successful.\n(Although with an error visible in the Puppet run log.)\n\nTherefore, to show the nodes with a catalog compilation as failed in Puppetboard you need to set\n`usecacheonfailure = false` in your nodes' `puppet.conf`.\n\n### PuppetDB\n\nOf course you need to configure your Puppet Server to store the Puppet run reports in PuppetDB.\nIf you haven't done that already please follow the [PuppetDB documentation](https://puppet.com/docs/puppetdb/latest/connect_puppet_server.html)\nabout this.\n\nIf you run Puppetboard on a different host than PuppetDB then you may want to configure the certificate\nallow-list for which certificates are allowed to access data from PuppetDB.\nPlease read more about this feature in the [PuppetDB documentation here](https://puppet.com/docs/puppetdb/latest/configure.html#certificate-allowlist).\n\n### App settings\n\nPuppetboard will look for a file pointed at by the `PUPPETBOARD_SETTINGS` environment variable.\nThe file has to be identical to\n[default_settings.py](https://github.com/voxpupuli/puppetboard/blob/master/puppetboard/default_settings.py)\nbut should only override the settings you need changed.\n\nIf you run PuppetDB and Puppetboard on the same machine the default settings provided will be enough to get you started\nand you won't need a custom settings file.\n\nAssuming your webserver and PuppetDB machine are not identical you will at least have to change the following settings:\n\n- `PUPPETDB_HOST`\n- `PUPPETDB_PORT`\n\nBy default PuppetDB requires SSL to be used when a non-local client wants to connect. Therefore you'll also have to\nsupply the following settings:\n\n- `PUPPETDB_SSL_VERIFY = True`\n- `PUPPETDB_KEY = /path/to/private/keyfile.pem`\n- `PUPPETDB_CERT = /path/to/public/keyfile.crt`\n\nWhen using the Puppetboard Docker image, you may also pass Puppetboard it's certificate contents via these environment\nvariables, either as a multiline string or pre-base64 encoded. This can be useful where the certificate is stored in a\nsecrets store i.e. AWS SSM Parameter Store.\n\n```\nPUPPETDB_CERT=\"-----BEGIN CERTIFICATE-----\n...\n-----END CERTIFICATE-----\"\n```\n\n```\nPUPPETDB_CERT=LS0tLS1CRUdJTiBSU0EgUFJJVkFURSBLRVktLS0tLQouLi4KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQ==\n```\n\nFor information about how to generate the correct keys please refer to the\n[pypuppetdb documentation](https://pypuppetdb.readthedocs.io/en/latest/connecting.html#ssl). Alternatively it is possible\nto explicitly specify the protocol to be used setting the `PUPPETDB_PROTO` variable.\n\nOther settings that might be interesting, in no particular order:\n\n- `SECRET_KEY`: set this to a long string, **the same for each application replica**, and keep it secret. Refer to\n [Flask documentation](https://flask.palletsprojects.com/en/2.1.x/quickstart/#sessions), section\n \"How to generate good secret keys\" for more info. Cannot be an empty string, which is the default.\n- `FAVORITE_ENVS`: an ordered list of Puppet environment names that will be shown immediately after \"All Environments\"\n and before other environments (which are sorted by name) in the dropdown for choosing the environment shown\n in the top-right of the UI. Environments listed here that do not really exist in your deployment are silently ignored.\n- `SHOW_ERROR_AS`: `friendly` or `raw`. The former makes Puppet run errors in Report and Failures views shown\n in a modified, (arguably) more user-friendly form. The latter shows them as they are.\n Defaults to `friendly`.\n- `CODE_PREFIX_TO_REMOVE`: what code path that should be shortened in \"Friendly errors\" to \"\u2026\" for readability.\n A regexp. Defaults to `/etc/puppetlabs/code/environments(/.*?/modules)?`.\n- `PUPPETDB_TIMEOUT`: Defaults to 20 seconds, but you might need to increase this value. It depends on how big the\n results are when querying PuppetDB. This behaviour will change in a future release when pagination will be introduced.\n- `UNRESPONSIVE_HOURS`: The amount of hours since the last check-in after which a node is considered unresponsive.\n- `LOGLEVEL`: A string representing the loglevel. It defaults to `'info'` but can be changed to `'warning'` or\n `'critical'` for less verbose logging or `'debug'` for more information.\n- `ENABLE_QUERY`: Defaults to `True` causing a Query tab to show up in the web interface allowing users to write\n and execute arbitrary queries against a set of endpoints in PuppetDB. Change this to `False` to disable this.\n See `ENABLED_QUERY_ENDPOINTS` to fine-tune which endpoints are allowed.\n- `ENABLED_QUERY_ENDPOINTS`: If `ENABLE_QUERY` is `True`, allow to fine tune the endpoints of PuppetDB APIs that\n can be queried. It must be a list of strings of PuppetDB endpoints for which the query is enabled.\n See the `QUERY_ENDPOINTS` constant in the `puppetboard.app` module for a list of the available endpoints.\n- `GRAPH_TYPE`: Specify the type of graph to display. Default is\n pie, other good option is donut. Other choices can be found here:\n [C3.js documentation](https://c3js.org/examples.html#chart)\n- `GRAPH_FACTS`: A list of fact names to tell PuppetBoard to generate a pie-chart on the fact page. With some fact\n values being unique per node, like ipaddress, uuid, and serial number, as well as structured facts it was no longer\n feasible to generate a graph for everything.\n- `INVENTORY_FACTS`: A list of tuples that serve as the column header and the fact name to search for to create\n the inventory page. If a fact is not found for a node then `undef` is printed.\n- `INVENTORY_FACT_TEMPLATES`: A mapping between fact name and jinja template to customize display\n- `ENABLE_CATALOG`: If set to `True` allows the user to view a node's latest catalog. This includes all managed\n resources, their file-system locations and their relationships, if available. Defaults to `False`.\n- `REFRESH_RATE`: Defaults to `30` the number of seconds to wait until the index page is automatically refreshed.\n- `DEFAULT_ENVIRONMENT`: Defaults to `'production'`, as the name suggests, load all information filtered by this\n environment value.\n- `REPORTS_COUNT`: Defaults to `10` the limit of the number of reports to load on the node or any reports page.\n- `OFFLINE_MODE`: If set to `True` load static assets (jquery, semantic-ui, etc) from the local web server instead\n of a CDN. Defaults to `False`.\n- `DAILY_REPORTS_CHART_ENABLED`: Enable the use of daily chart graphs when looking at dashboard and node view.\n- `DAILY_REPORTS_CHART_DAYS`: Number of days to show history for on the daily report graphs.\n- `DISPLAYED_METRICS`: Metrics to show when displaying node summary. Example: `'resources.total'`, `'events.noop'`.\n- `TABLE_COUNT_SELECTOR`: Configure the dropdown to limit number of hosts to show per page.\n- `LITTLE_TABLE_COUNT`: Default number of reports to show when when looking at a node.\n- `NORMAL_TABLE_COUNT`: Default number of nodes to show when displaying reports and catalog nodes.\n- `LOCALISE_TIMESTAMP`: If set to `True` then timestamps are shown using your browser's timezone. Otherwise UTC is used. Defaults to `True`.\n- `WITH_EVENT_NUMBERS`: If set to `True` then Overview and Nodes list shows exact number of changed resources\n in the last report. Otherwise shows only 'some' string if there are resources with given status. Setting this\n to `False` gives performance benefits, especially in big Puppet environments (more than few hundreds of nodes).\n Defaults to `True`.\n- `ENABLE_CLASS`: If set to `True` allows the user to view the number of resource events (number of changed resources in the last report) grouped by class.\n The resource events are grouped by their status ('failure', 'success', 'noop').\n- `CLASS_EVENTS_STATUS_COLUMNS`: A mapping between the status of the resource events and the name of the columns of the table to display.\n- `CACHE_TYPE`: Specifies which type of caching object to use when `SCHEDULER_ENABLED` is set to `True`.\n The cache is used for the classes view (`ENABLE_CLASS` is set to `True`) which requires parsing the events of all the latest reports to group them by Puppet class.\n If the last report is present in the cache, we do not parse the events, which avoids unnecessary processing.\n If you configure more than one worker, you must use a shared backend (e.g. `MemcachedCache`) to allow the sharing of the cache between the processes.\n Indeed, the `SimpleCache` type does not allow sharing the cache between processes, it uses the process memory to store the cache.\n Defaults to `SimpleCache`.\n- `CACHE_DEFAULT_TIMEOUT`: Cache lifetime in second. Defaults to `3600`.\n- `SCHEDULER_ENABLED`: If set to `True` then a scheduler instance is created in order to execute scheduled jobs. Defaults to `False`.\n- `SCHEDULER_JOBS`: List of the scheduled jobs to trigger within a worker.\n A job can for example be used to compute a result to be cached. This is the case for the classes view which uses a job to pre-compute at regular intervals the results to be displayed.\n Each scheduled job must contain the following fields: `id`, `func`, `trigger`, `seconds`.\n- `SCHEDULER_LOCK_BIND_PORT`: Specifies an available port that allows a single worker to listen on it.\n This allows to configure scheduled jobs in a single worker. Defaults to `49100`.\n\n## Getting Help<a id=\"getting-help\"></a>\n\nFor questions or bug reports you can file an [issue](https://github.com/voxpupuli/puppetboard/issues).\n\n## Contributing<a id=\"contributing\"></a>\n\n### Development\n\nPuppetboard relies on the [pypuppetdb](https://pypi.org/project/pypuppetdb/) library to fetch data from PuppetDB\nand is built with the help of the [Flask](https://flask.palletsprojects.com) microframework.\n\nIf you wish to hack on Puppetboard you should fork/clone the Github repository and then install the requirements through:\n\n```bash\npip install --upgrade wheel setuptools\npython setup.py develop\npip install --upgrade -r requirements-test.txt\nmypy --install-types --non-interactive puppetboard/ test/\n```\n\nYou're advised to do this inside a virtualenv specifically created to work on Puppetboard as to not pollute your global Python installation.\n\nYou can run the tests with:\n```bash\npytest --cov=. --cov-report=xml --strict-markers --mypy puppetboard test\npylint --errors-only puppetboard test\n```\n\nYou can run the app it in development mode by simply executing:\n\n```bash\nflask run\n```\n\nYou can specify listening host and port with environment variables or command line otions:\n\n```bash\nexport FLASK_RUN_HOST=0.0.0.0\nexport FLASK_RUN_PORT=8000\n\nflask run\n```\n\nor\n\n```bash\nflask run --host '0.0.0.0' --port '8000'\n```\n\n\nUse `PUPPETBOARD_SETTINGS` to change the different settings or patch `default_settings.py` directly.\nTake care not to include your local changes on that file when submitting patches for Puppetboard.\nPlace a `settings.py` file inside the base directory of the git repository that will be used, if the environment\nvariable is not set.\n\nWe welcome contributions to this project. However, there are a few ground rules contributors should be aware of.\n\n### License\n\nThis project is licensed under the Apache v2.0 License. As such, your contributions, once accepted, are automatically\ncovered by this license.\n\n### Commit messages\n\nWrite decent commit messages. Don't use swear words and refrain from uninformative commit messages as 'fixed typo'.\n\nThe preferred format of a commit message:\n\n docs/quickstart: Fixed a typo in the Nodes section.\n\n If needed, elaborate further on this commit. Feel free to write a\n complete blog post here if that helps us understand what this is\n all about.\n\n Fixes #4 and resolves #2.\n\nIf you'd like a more elaborate guide on how to write and format your commit messages have a look at [this post\nby Tim Pope](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).\n\n### Build a release\n\nplease see: [RELEASE.md](RELEASE.md)\n\n## More Screenshots<a id=\"more-screenshots\"></a>\n\n* Overview / Index / Homepage\n\n\n\n* Nodes view, all active nodes\n\n\n\n* Single node page / overview\n\n\n\n* Report view\n\n\n\n* Facts view\n\n\n\n* Single fact, with graphs\n\n\n\n* All nodes that have this fact with that value\n\n\n\n* Query view - results as table\n\n\n\n* Query view - results as JSON\n\n\n\n* Metrics view\n\n\n\n* Single metric\n\n\n\n* Inventory view\n\n\n\n* Classes view, group the resource events of the last reports by Puppet class\n\n\n\n* Class view, list the nodes with almost one resource event for a given class\n\n\n\n# Legal<a id=\"legal\"></a>\n\nThe app code is licensed under the [Apache License, Version 2.0](./LICENSE).\n\nThe favicon has been created based on the icon created by [Jonathan Couti\u00f1o](https://thenounproject.com/ralts01/)\nunder the [Attribution 3.0 Unported (CC BY 3.0) license](https://creativecommons.org/licenses/by/3.0/),\ndownloaded from the [Noun Project](https://thenounproject.com).\n\n",
"bugtrack_url": null,
"license": "Apache-2.0",
"summary": "Web frontend for PuppetDB",
"version": "6.0.1",
"project_urls": {
"Homepage": "https://github.com/voxpupuli/puppetboard",
"Repository": "https://github.com/voxpupuli/puppetboard"
},
"split_keywords": [
"puppet",
" puppetdb",
" puppetboard"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "2506bae9086cdac13b5536e677d45969321664d231ac67e3171a0d30265e89f5",
"md5": "009dfea7d4748cfcd843d8abf49525c9",
"sha256": "3d32e11a7a08cfb7e42cd0d0101bcbe6e652864965b2b588e6d78e8dff1dd99f"
},
"downloads": -1,
"filename": "puppetboard-6.0.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "009dfea7d4748cfcd843d8abf49525c9",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": "<4.0,>=3.9",
"size": 2415403,
"upload_time": "2025-02-13T15:41:32",
"upload_time_iso_8601": "2025-02-13T15:41:32.947365Z",
"url": "https://files.pythonhosted.org/packages/25/06/bae9086cdac13b5536e677d45969321664d231ac67e3171a0d30265e89f5/puppetboard-6.0.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "798eacd9a26841387a6f0a5905b5b9944fb1a857d873f749eaa13b30c9e137fb",
"md5": "66d3841f8b7de0de22fdd84078aa0d91",
"sha256": "45b4c4ed813d724b4bb596232ce43d7620bc7e8d7e8334fdd9101aeb2e5a59ee"
},
"downloads": -1,
"filename": "puppetboard-6.0.1.tar.gz",
"has_sig": false,
"md5_digest": "66d3841f8b7de0de22fdd84078aa0d91",
"packagetype": "sdist",
"python_version": "source",
"requires_python": "<4.0,>=3.9",
"size": 2383971,
"upload_time": "2025-02-13T15:41:35",
"upload_time_iso_8601": "2025-02-13T15:41:35.539224Z",
"url": "https://files.pythonhosted.org/packages/79/8e/acd9a26841387a6f0a5905b5b9944fb1a857d873f749eaa13b30c9e137fb/puppetboard-6.0.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-02-13 15:41:35",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "voxpupuli",
"github_project": "puppetboard",
"travis_ci": false,
"coveralls": true,
"github_actions": true,
"requirements": [
{
"name": "certifi",
"specs": [
[
"==",
"2025.1.31"
]
]
},
{
"name": "charset-normalizer",
"specs": [
[
"==",
"3.4.1"
]
]
},
{
"name": "click",
"specs": [
[
"==",
"8.1.8"
]
]
},
{
"name": "commonmark",
"specs": [
[
"==",
"0.9.1"
]
]
},
{
"name": "Flask",
"specs": [
[
"==",
"3.1.0"
]
]
},
{
"name": "Flask-APScheduler",
"specs": [
[
"==",
"1.13.1"
]
]
},
{
"name": "Flask-Caching",
"specs": [
[
"==",
"2.3.0"
]
]
},
{
"name": "Flask-WTF",
"specs": [
[
"==",
"1.2.2"
]
]
},
{
"name": "idna",
"specs": [
[
"==",
"3.10"
]
]
},
{
"name": "itsdangerous",
"specs": [
[
"==",
"2.2.0"
]
]
},
{
"name": "Jinja2",
"specs": [
[
"==",
"3.1.5"
]
]
},
{
"name": "MarkupSafe",
"specs": [
[
"==",
"3.0.2"
]
]
},
{
"name": "packaging",
"specs": [
[
"==",
"24.2"
]
]
},
{
"name": "pyparsing",
"specs": [
[
"==",
"3.2.1"
]
]
},
{
"name": "pypuppetdb",
"specs": [
[
"==",
"3.2.0"
]
]
},
{
"name": "requests",
"specs": [
[
"==",
"2.32.3"
]
]
},
{
"name": "typing_extensions",
"specs": [
[
"==",
"4.12.2"
]
]
},
{
"name": "urllib3",
"specs": [
[
"==",
"2.3.0"
]
]
},
{
"name": "Werkzeug",
"specs": [
[
"==",
"3.1.3"
]
]
},
{
"name": "WTForms",
"specs": [
[
"==",
"3.2.1"
]
]
},
{
"name": "zipp",
"specs": [
[
"==",
"3.21.0"
]
]
}
],
"lcname": "puppetboard"
}
JSON
