fuel-library/deployment/puppet/rsyslog
Bogdan Dobrelya df3ee5b1c3 Align ActionQueue rsyslog params in templates
The changes accepted in fix should be aligned
with other templates we use for client.conf and
server.conf then installing and configuring rsyslog.

Related-bug: #1339659

Change-Id: I9108b0fb992f3dd5a68f3b9d39d78705e243d9fb
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
2014-08-15 10:48:27 +03:00
..
examples Added example for rsyslog module 2014-03-28 17:04:12 +02:00
files Fix rsyslog defaults typo for ubuntu 2014-04-14 16:27:06 +03:00
manifests Update logfile ownership for syslog in Ubuntu 2014-07-16 12:27:30 +03:00
spec [FUEL-286] Added syslog option 2013-01-11 13:41:04 +04:00
templates Align ActionQueue rsyslog params in templates 2014-08-15 10:48:27 +03:00
tests [FUEL-286] Added syslog option 2013-01-11 13:41:04 +04:00
.project Add project files 2013-04-01 14:15:04 +04:00
Modulefile [FUEL-286] Added syslog option 2013-01-11 13:41:04 +04:00
README.md [FUEL-286] Added syslog option 2013-01-11 13:41:04 +04:00

puppet-rsyslog

================

Manage rsyslog client and server via Puppet

REQUIREMENTS

  • Puppet >=2.6 if using parameterized classes
  • Currently supports Ubuntu >=11.04 & Debian running rsyslog >=4.5

USAGE

Client

Using default values

    class { 'rsyslog::client': }

Variables and default values

    class { 'rsyslog::client':
        log_remote     => true,
        remote_type    => 'tcp',
        log_local      => false,
        log_auth_local => false,
        custom_config  => undef,
        server         => 'log',
        port           => '514',
    }

Server

Using default values

    class { 'rsyslog::server': }

Variables and default values

    class { 'rsyslog::server':
        enable_tcp                => true,
        enable_udp                => true,
        server_dir                => '/srv/log/',
        custom_config             => undef,
        high_precision_timestamps => false,
    }

Both can be installed at the same time.

PARAMETERS

The following lists all the class parameters this module accepts.

RSYSLOG::SERVER CLASS PARAMETERS    VALUES         DESCRIPTION
--------------------------------------------------------------
enable_tcp                          true,false     Enable TCP listener. Defaults to true.
enable_udp                          true,false     Enable UDP listener. Defaults to true.
server_dir                          STRING         Folder where logs will be stored on the server. Defaults to '/srv/log/'
custom_config                       STRING         Specify your own template to use for server config. Defaults to undef. Example usage: custom_config => 'rsyslog/my_config.erb'
high_precision_timestamps           true,false     Whether or not to use high precision timestamps.

RSYSLOG::CLIENT CLASS PARAMETERS    VALUES         DESCRIPTION
--------------------------------------------------------------
log_remote                          true,false     Log Remotely. Defaults to true.
remote_type                         'tcp','udp'    Which protocol to use when logging remotely. Defaults to 'tcp'.
log_local                           true,false     Log locally. Defualts to false.
log_auth_local                      true,false     Just log auth facility locally. Defaults to false.
custom_config                       STRING         Specify your own template to use for client config. Defaults to undef. Example usage: custom_config => 'rsyslog/my_config.erb
server                              STRING         Rsyslog server to log to. Will be used in the client configuration file.

Other notes

Due to a missing feature in current RELP versions (InputRELPServerBindRuleset option), remote logging is using TCP. You can switch between TCP and UDP. As soon as there is a new RELP version which supports setting Rulesets, I will add support for relp back.