summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPedro Alvarez <pedro.alvarez@codethink.co.uk>2015-11-05 15:10:12 +0000
committerPedro Alvarez <pedro.alvarez@codethink.co.uk>2015-11-05 15:12:08 +0000
commit2b4b8a07e0306c2ff9231eca040d5b65fbafbd2d (patch)
treedc1e23163b9b33a9481c42b5bafc0b7ca23c2b18
parent5a024dfef4b3714e7a1d1be2f04de55efdb95b75 (diff)
downloadinfrastructure-2b4b8a07e0306c2ff9231eca040d5b65fbafbd2d.tar.gz
README.mdwn: Add commands needed to have backups working
Change-Id: Ib239a561eaaaa0a5a0ae91af2ee45889ae2e30b3
-rw-r--r--README.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/README.mdwn b/README.mdwn
index 8c914aa1..c7318691 100644
--- a/README.mdwn
+++ b/README.mdwn
@@ -120,6 +120,16 @@ Instances themselves are not backed up. In the event of a crisis we will
redeploy them from the infrastructure.git repository. There should be nothing
valuable stored outside of the data volumes that are backed up.
+To prepare the infrastructure to run the backup scripts you will need to run
+the following playbooks:
+
+ ansible-playbook -i hosts baserock_frontend/instance-backup-config.yml
+ ansible-playbook -i hosts baserock_database/instance-backup-config.yml
+ ansible-playbook -i hosts baserock_gerrit/instance-backup-config.yml
+
+NOTE: to run these playbooks you need to have the public ssh key of the backups
+instance in `keys/backup.key.pub`.
+
Deployment with Packer
----------------------