aboutsummaryrefslogtreecommitdiff
path: root/manifests
AgeCommit message (Collapse)Author
2008-08-08fix remove, should default to false instead of 'no'Micah Anderson
2008-08-08adding the ability to specify how much maildir backups to keepMicah Anderson
2008-08-08standardize the spacing/indentationMicah Anderson
2008-08-06update to latest backupninjaMicah Anderson
2008-08-01fix one screw up from last commit.Pietro
2008-07-31change permissions to octals.Pietro
2008-07-31standardize formattingMicah Anderson
2008-07-31allow for a resource override of managing the ssh directoryMicah Anderson
2008-07-31remove extraneous curly braceMicah Anderson
2008-07-31enable the ability to override if the ssh directory is managed or not, inMicah Anderson
situations where there is a system-wide /etc/ssh/authorized_keys directory, this will likely not be managed by the backupninja module, and managing it here will result in duplicate definitions
2008-07-31change to standardized formattingMicah Anderson
2008-07-31more formatting changesMicah Anderson
2008-07-31fix directory bug that was causing the home directory to be prepended to the ↵Micah Anderson
beginning of the $sshdir
2008-07-31move to standardized spacing and indentationMicah Anderson
2008-07-31add missing parameter for Backupninja::Rdiff typeMicah Anderson
2008-07-31re-add accidentally removed opening braceMicah Anderson
2008-07-31setup the backupninja module to enable specification of the locationMicah Anderson
of the ssh authorized_keys directories and files so that if you are not using the standard location for authorized_keys files ($HOME/.ssh/authorized_keys) and instead using the /etc/ssh/sshd_config option "AuthorizedKeysFile" you can then specify where that will be. For example, if your /etc/ssh/sshd_config has: AuthorizedKeysFile /etc/ssh/authorized_keys/$u then you could specify in the rdiff-backup definition the following parameters: ... ssh_dir => "/etc/ssh/authorized_keys", authorized_keys_file => "${hostname}", to create the file /etc/ssh/authorized_keys/${hostname} instead of the default location (if unspecifed, the default is used).
2008-07-08add some error checks to make sure necessary values are setMicah Anderson
2008-07-08unset some default values that probably shouldn't be setMicah Anderson
2008-07-08forgot the when parameter which is needed for this handlerMicah Anderson
2008-07-08changing order so it doesnt use the same one as the sys handler.Pietro
2008-07-08sh backupninja handler.Pietro
2008-07-08make new maildir piece to backupninja moduleMicah Anderson
2008-06-05config option should be vservers pluralMicah Anderson
2008-06-05Add vsinclude option to rdiff handlerMicah Anderson
2008-06-03installkey uses true value now insteadMicah Anderson
2008-06-03fix incorrect variable definitionMicah Anderson
2008-06-03add a way to override the automatic tag creation based on hostnameMicah Anderson
set the backuptag on crabgrass to not use the default one, otherwise it wont be collected
2008-06-03add vserver support to backupninja configMicah Anderson
add vsnames support to mysql config
2008-05-31fix the case, 'doit' is no longer used, also set installuser to be default ↵Micah Anderson
as true
2008-05-30remove call that cannot be instantiated because the server class has not ↵Micah Anderson
been evaluated at this point
2008-05-30change from installkeys to installkeyMicah Anderson
when you have two rdiff-backup calls, then the User is a Duplicate definition, i think the only way to do it is to have a variable that you can set to turn off user handling (which we make $installuser and $usermanage be consistant with $installkey and $keymanage), which is set true by default, but when you have a second rdiff call on a host, you can set it to false
2008-05-30change the backupninja::client::key definition to use the $user variableMicah Anderson
change the $host variable to no longer use the $user variable, that way multiple rdiff's can be instantiated for a particular host, with different name variables in order to do that, the class also has to have the $installkeys variable that can be passed to backupninja::client::key so that the second rdiff instantiation would set installkeys => false, otherwise there will be an attempt to duplicate the resource
2008-05-30fix backupninja rdiff server sandbox to enable multiple rdiff definitions ↵Micah Anderson
differentiated by their name variable
2008-05-22remove debugging infoMicah Anderson
2008-05-22fix up the key creationRiseup
2008-05-22fix missing colonMicah Anderson
2008-05-22oops, one more curly brace fixMicah Anderson
2008-05-22fix missing curly braces, and also fix up indentationMicah Anderson
2008-05-22try to manage the backupninja keys in a sane way, but might be totally insaneMicah Anderson
2008-05-21create puffin backup ssh auth keysMicah Anderson
get rid of the ninjareport directory configure v.admin's ssh-key auth to kakapo move v.admin's backups into the /crypt/serverbackups directory on kakapo setup puffin to do ninjareport fix backupserver_tag
2008-05-21fix backupkeys variableMicah Anderson
2008-05-21fix the tags up so that the host can be overridden if your backup host ↵Micah Anderson
declaration doesn't agree with your $fqdn
2008-05-21flip the override variables, when setting these, you are going to want to setMicah Anderson
$backupdir, not $backupdir_override
2008-05-21create a new backadmin ssh keyMicah Anderson
move backup keys into a 'backupkeys' directory make a ninjareport directory to contain the pieces for ninjareport move the backupninja::server definition for kakapo into site.pp, including the $backupdir definition add a backupkeys piece to the backupninja::server module which should install the key
2008-05-21I dont like how any of this is done, but it needs to be working again,Micah Anderson
and then made better later. The ninjareport is a pretty bad way of collecting all the backupninja reports into one email called the 'ninjareport' which contains all the hosts with backupninja problems, and a notice about any hosts that haven't reported in for a while. The way it works is each participating host has a limited command ssh key installed in /root/.ssh/id_rsa which enables it to rsync its /var/log/backupninja.log to ninja@admin:/var/lib/backupninja/reports/$hostname.log. After the backup runs on the host, it does this rsync. On v.admin, there is a /var/lib/backupninja/.ssh/authorized_keys which has the ssh public key part of each host's ssh key, command-limited to only allow an rsync of their backupninja.log file. There is a cronjob there that runs once a day and collects new logs and does some basic figuring and then collects those all into one email. There are *many* ways that this needs to be improved. From the puppet side, the approach is all wrong, and there is a lot of dupliacted configuration that is being done, it needs to be turned into a define and export and collection needs to be done. The whole thing needs to be redesigned from the ground up, but I don't have the mental space to do it right now, and it needs to work :(
2008-05-20harmonize spacing to be consistantMicah Anderson
2008-05-20Some backupninja module updates from anarcat:Micah Anderson
Wed Apr 30 16:22:48 EDT 2008 anarcat@koumbit.org * remove read permissions on backup directory on group so that a sandbox user can't read other people's directories Wed Apr 30 16:01:53 EDT 2008 anarcat@koumbit.org * default the sandbox host to local ($fqdn) and depend on the sandbox directory properly Thu Mar 13 18:49:38 EDT 2008 anarcat@koumbit.org * create the backup directory along with the user
2008-05-17fix missing class implosionMicah Anderson
2008-05-17fix syntax errorsMicah Anderson