baserock/baserock/infrastructure.git - gitlab.com: baserock/infrastructure.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	baserock_database: Update on top of Fedora 23, redeploy	Sam Thursfield	2016-02-19	1	-12/+3
\| \| \| \|	Change-Id: I9a25d9aad540c291aaea45f00e38065981ff3f50
*	baserock_storyboard: Upgrade to latest and use Ansible for deployment	Pedro Alvarez	2016-01-22	1	-0/+5
\| \| \| \|	Change-Id: If4578c0d97aa2aee1a1a7e57bb7e2c42917ba077
*	baserock_backup: Update backup script	Sam Thursfield	2015-12-23	1	-4/+10
\| \| \| \| \| \| \| \| \| \| \| \|	Storyboard now has its own MySQL database (the current version won't work with the MariaDB database that we were using before, due to lack of some feature). Also, the script should NOT update the timestamp files if a backup actually failed. The actual errors will be in the journal but it's more convenient to use the timestamps to see if some backups aren't working. Change-Id: Ifbd541518da18a1d273638d5a432c64f68172cb4
*	baserock_backup: Make backups run automatically	Sam Thursfield	2015-05-22	2	-0/+27
\| \| \| \| \| \| \| \|	This should have happened already, but I forgot that 'crond' won't be running automatically. The backup VM hosted at Codethink was powered off and back on at some point, backups didn't run after that point. Change-Id: I10f6b73c2947631001040099074f373a9ea5464e
*	Add a simple data backup mechanism	Sam Thursfield	2015-03-30	3	-0/+58
	The technique used is: create a new SSH key for backup automation, and authorize it to log in as 'root' to instances. To reduce potential harm if the key somehow gets compromised, it is limited to logging in from a single IP, and it is limited to running the 'backup-snapshot' program on the instances. Inside each instance, the `backup-snapshot` script is used as a wrapper for the `rsync --server` process. This script pauses running services, takes a snapshot of the data volume, and then runs the RSync server. Change-Id: I3c98ffe3dc2fa1373bd0df2388145636e491bf57