814e4be128
This introduces two new roles for managing the backup-server and hosts that we wish to back up. Firstly the "backup" role runs on hosts we wish to backup. This generates and configures a separate ssh key for running bup and installs the appropriate cron job to run the backup daily. The "backup-server" job runs on the backup server (or, indeed servers). It creates users for each backup host, accepts the remote keys mentioned above and initalises bup. It is then ready to receive backups from the remote hosts. This eliminates a fairly long-standing requirement for manual setup of the backup server users and keys; this section is removed from the documentation. testinfra coverage is added. Change-Id: I9bf74df351e056791ed817180436617048224d2c
16 lines
571 B
ReStructuredText
16 lines
571 B
ReStructuredText
Setup backup server
|
|
|
|
This role configures backup server(s) in the ``backup-server`` group
|
|
to accept backups from remote hosts.
|
|
|
|
Note that the ``backup`` role must have run on each host in the
|
|
``backup`` group before this role. That role will create a
|
|
``bup_user`` tuple in the hostvars for for each host consisting of the
|
|
required username and public key.
|
|
|
|
Each required user gets a separate home directory in ``/opt/backups``.
|
|
Their ``authorized_keys`` file is configured with the public key to
|
|
allow the remote host to log in and only run ``bup``.
|
|
|
|
**Role Variables**
|