Bits and pieces of Tor Project infrastructure information
A collection of information looking for a better place, perhaps after being expanded a bit to deserve their own page.
- We use Bacula to make backups, with one host running a director (currently bacula-director-01.tpo) and another host for storage (currently brulloi.tpo).
- There are
WALfiles, the latter for incremental backups.
- The logs found in
/var/log/bacula/seem mostly empty, just like the systemd journals.
The director runs
/etc/bacula/dsa-clientsfor a list of clients to back up. This file is populated by puppet (puppetdb
$bacula::tag_bacula_dsa_client_list) and will list clients until they're being deactivated in puppet.
tor-puppet/modules/bacula/manifests/client.ppgives an idea of where things are at on backup clients.
- Clients run the Bacula File Daemon,
Example from a vhost template
<% if scope.function_onion_global_service_hostname(['crm-2018.torproject.org']) -%> <Virtualhost *:80> ServerName <%= scope.function_onion_global_service_hostname(['crm-2018.torproject.org']) %> Use vhost-inner-crm-2018.torproject.org <% end -%>
Function defined in
onionbalance-services.yamlis populated through