majic-ansible-roles Files · roles/backup

Files @ a5d38f30094b

Branch filter:

Location: majic-ansible-roles/roles/backup_client/defaults/main.yml - annotation

a5d38f30094b 791 B text/x-yaml Show Source Show as Raw Download as Raw

branko

MAR-132: Workarounds for wsgi_website Python virtual environment in Debian Stretch:

- Manually install setuptools in Python virtual environment on Debian
Stretch, otherwise the pkg-resources==0.0.0 package will mess with
pip freeze etc.
- Add back installation of futures package, even on Python 3 (since it
does not cause any harm).
- A small cleanup of how requirements are treated will be done in
separate ticket.

a45dcc06530a
a45dcc06530a
d61d01c00362
3498d77cad32
19020779a000
d61d01c00362
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
279640b2178c
bfafd526bfc3
bfafd526bfc3
279640b2178c
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3

---

backup_additional_encryption_keys: []
backup_client_username: "bak-{{ ansible_fqdn | replace('.', '_') }}"
backup_server_destination: /duplicity
backup_server_port: 2222

# Internal parameters.

# GnuPG 2 binary in Debian Jessie and Debian Stretch is different. Additionally,
# Debian Jessie duply configuration expects short keys, while Debian Stretch
# expects long keys. We set-up parameters for this here in a bit of a workaround
# way instead of setting facts within the playbook.
backup_client_gnupg_details:
  jessie:
    binary: gpg2
    cutoff: '8'
  stretch:
    binary: gpg
    cutoff: '0'

gnupg_binary: "{{ backup_client_gnupg_details[ansible_distribution_release]['binary'] }}"
gnupg_key_cutoff: "{{ backup_client_gnupg_details[ansible_distribution_release]['cutoff'] }}"