The previous article has the salt installation process and the Salt module, not clear can go to look, this article mainly realizes nginx+php uses the logrotate to carry on the cutting to the log, then simply uses under the Salt this tool;
The architecture is as follows:
The following. pp files are under/etc/puppet/modules/logrotate/manifests, as follows
Init.pp
Class Logrotate (
$backup _nginx = "/data/backup/log/nginx",
$nginx _log = "/data/log/nginx",
$ Nginx_pid = "/usr/local/nginx/nginx.pid",
$base _cron = "/home/cron/logrotate",
# $backup _nginx_ dir = ["/data", "/data/backup", "/data/backup/log", "/data/backup/log/nginx"],
# $base _cron_dir = ["/home/ Cron ","/home/cron/logrotate "],
$backup _php ="/data/backup/log/php ",
$php _log ="/usr/local/ Php/var/log ",
$php _pid ="/usr/local/php/var/run/php-fpm.pid "
) {case
$operatingsystem {
centos:{
include logrotate::base
include Logrotate::addcrons
}
}
Base.pp
Class Logrotate::base {
package {"Logrotate":
ensure => present
}
# file {['/data ', '/data/ Backup ","/data/backup/log ","/data/backup/log/nginx "]:
file {" $backup _nginx ":
ensure => present,
}
# file {["/home/cron", "/home/cron/logrotate"]:
file {"$base _cron":
ensure => present,
}
file {"$backup _php":
ensure => present
}
}