... | ... | @@ -2108,6 +2108,17 @@ Puppet server and agents. It could still talk with LDAP for the host |
|
|
directory, but at that point it might be better to simply **move all
|
|
|
host metadata into Hiera**.
|
|
|
|
|
|
It would still be nice to retain a dashboard of sorts to show the
|
|
|
different hosts and their configurations. Right now this is
|
|
|
accomplished with the [machines.cgi](https://db.torproject.org/machines.cgi) web interface, but this could
|
|
|
probably be favorably replaced by some static site generator. Gandi
|
|
|
implemented [hieraviz](https://github.com/Gandi/hieraviz) for this (now deprecated) and still maintain
|
|
|
a command-line tool called [hieracles](https://github.com/Gandi/hieracles) that somewhat overlaps with
|
|
|
[cumin](howto/cumin) and [hieraexplain](https://github.com/binford2k/hiera_explain) as well. Finally, a Puppet Dashboard
|
|
|
could replace this, see [issue tpo/tpa/team#31969](https://gitlab.torproject.org/tpo/tpa/team/-/issues/31969) for a discussion
|
|
|
on that, which includes the suggestion of moving the host inventory
|
|
|
display into Grafana, which has already started.
|
|
|
|
|
|
For users, the situation is less clear: we need some sort of dashboard
|
|
|
for users to **manage their email forward** and, if that project ever sees
|
|
|
the light of day, their email (submission, IMAP?) password. It is also
|
... | ... | |