deploy a puppet dashboard

it would be useful to have a way to browse reports and facts in the cluster. there's a lot of information in the PuppetDB that's only visible when you inspect the database, and it would help to have a way to browse this and diagnose issues with puppet.

added component::internal services/tor sysadmin team owner::anarcat priority::medium severity::normal status::assigned type::project labels

I started working on Puppetboard is a "web interface to PuppetDB aiming to replace the reporting functionality of Puppet Dashboard, except with a simpler interface, written in Python (instead of Ruby). It's also a "readonly" interface whereas the Puppet dashboard also acts as an ENC (External Node Classifier), which can assign classes to roles and so on.

There's a planned Debian package for puppetboard in debian bug#754796. It requires a Python package from Debian testing (bullseye) which might be a blocker, and also ships with unaudited Javascript code (semantic-ui and tablesort). I have not audited the puppetboard code itself, but it's maintained by the voxpupuli community which we already somewhat trust with other modules.

I'll see if my latest update brings any activity in the debian package. Hopefully we can set that up using neat little debian package instead of something too hacky.

Trac:
Parent: N/A to #30881 (moved)

remove from checklist, as i want to close that ticket and it will be open forever if it depends on all the tickets generated from it.

Trac:
Parent: #30881 (moved) to N/A

now that i think of it, it seems to me it would be much, much better to reuse our existing monitoring infrastructure for this. and of course, there is a (two, actually) prometheus exporter for Puppet:

https://dev.to/camptocamp-ops/getting-puppet-report-metrics-from-puppetdb-6bp

so that would be worth researching before going crazy with debian packaging...

one thing prometheus cannot do is keep a copy of structured facts and reports per host, so that is somewhere the puppet dashbaord still has an edge...