Functionality #17363
Mis à jour par Antoine Beaupré il y a environ 11 ans
i've reviewed the upstream shared module for backupninja and it looks good!
a few things are not upstream:
* squeeze backup version (we should use the class parameter)
* the whole $multiple_backups hack needs to be ported, probably by using an override for the '$home/rdiff-backup/' directory instead of the hack and fixing the monitoring script to avoid having to look in the "multibackups" (but simply look for rdiff-backup-data directories)
* the real_hostname parameter for the rdiff define is dropped (but it seems unused)
* the backup checking script can send directly to the nagios server and have parameters for delays, that would need to be ported as well
* the /srv/backups default is changed`
class parameters are only in lavamind's refactor branch: https://gitlab.com/shared-puppet-modules-group/backupninja/tree/march2015-refactor
donc en bref, next steps, pour le déploiement:
# -attendre une heure que puppet roule partout-
# -rerouler rerouler puppet sur alexandrie- alexandrie
# -rm /etc/nagios3/conf.d/nagios_service.cfg- rm /etc/nagios3/conf.d/nagios_service.cfg
# -rerouler rerouler puppet sur nagios0- nagios0
# vérifier qu'on a pas des checks de backups en double
# rouler /usr/local/checkbackups -s nagios0.koumbit.net -d /srv/backups et vérifier /var/log/nagios3/nagios.log pour des messages comme:
<pre>
[1429740034] Warning: Passive check result was received for service 'backups' on host 'sciencepresse.koumbit.net', but the host could not be found!
</pre>
pour le merge, il resterait à réviser le diff (voir sommaire ici), trouver une façon de désactiver les checks nagios de façon globale (site_backupninja?) et déployer le module upstream direct.
a few things are not upstream:
* squeeze backup version (we should use the class parameter)
* the whole $multiple_backups hack needs to be ported, probably by using an override for the '$home/rdiff-backup/' directory instead of the hack and fixing the monitoring script to avoid having to look in the "multibackups" (but simply look for rdiff-backup-data directories)
* the real_hostname parameter for the rdiff define is dropped (but it seems unused)
* the backup checking script can send directly to the nagios server and have parameters for delays, that would need to be ported as well
* the /srv/backups default is changed`
class parameters are only in lavamind's refactor branch: https://gitlab.com/shared-puppet-modules-group/backupninja/tree/march2015-refactor
donc en bref, next steps, pour le déploiement:
# -attendre une heure que puppet roule partout-
# -rerouler rerouler puppet sur alexandrie- alexandrie
# -rm /etc/nagios3/conf.d/nagios_service.cfg- rm /etc/nagios3/conf.d/nagios_service.cfg
# -rerouler rerouler puppet sur nagios0- nagios0
# vérifier qu'on a pas des checks de backups en double
# rouler /usr/local/checkbackups -s nagios0.koumbit.net -d /srv/backups et vérifier /var/log/nagios3/nagios.log pour des messages comme:
<pre>
[1429740034] Warning: Passive check result was received for service 'backups' on host 'sciencepresse.koumbit.net', but the host could not be found!
</pre>
pour le merge, il resterait à réviser le diff (voir sommaire ici), trouver une façon de désactiver les checks nagios de façon globale (site_backupninja?) et déployer le module upstream direct.