+
@@ -171,7 +176,7 @@
diff --git a/doc/file.README.html b/doc/file.README.html
index d40a22c..89ef340 100644
--- a/doc/file.README.html
+++ b/doc/file.README.html
@@ -132,9 +132,13 @@ structure (file system permissions, selinux context) through parameters
manage configuration files through parameters:
* nrpe.conf
* nrpe.cfg
- *
-commands.cfg (optional)
-* manage iptables (optionals )
+*
+manage sudo role for nagios user on NRPE clients
+* manage dynamic NRPE
+check command definitions
+* manage iptables (optional)
+* manage selinux
+rule exceptions (optional)
SERVICE
* manage NRPE service
@@ -213,16 +217,65 @@ through this modules. Defaults to true.
$ne_include_selinux : Whether to manage selinux exception
rules. Defaults to true.
+
+
$ne_enable_ssl : Whether to allow SSL settings. See known problems for more details.
+
+
$ne_allow_sudo : Whether to allow the nagios / nrpe user to
+use sudo by default. Controls both the
+settingcommand_prefixand application of a sudo rule. Defaults
+tofalse` as it usually is not required for most of the checks.
Managing Check Commands
+
In order to connect a Nagios monitoring server to clients through NRPE, you
+must define commands and the desired argument strings on the clients. The
+default NRPE installation comes with a few examples of such commands, which
+are also included in this module. However, every environment is very
+different in their requirements and Nagios via Puppet is all about the
+ability to dynamicically set command arguments based on default variables /
+overrides. For that reason no hard-coded commands are included, but instead
+all commands are set via argument strings, where possible.
+
+
The commands are created within /etc/nrpe.d/command.cfg , every set of
+instructions creates a new line.
+
+
Defining commands is as simple as
+that:
+<code>
+`cd_nrpe::commands::definitions` {
+'check_users':
+ `ne_check_cmd` =>
+'check_users',
+ `ne_cmd_argstring` => '-w $ARG1$ -c
+$ARG2$',
+ }
+</code>
+It is very recommendable to define such
+commands within Puppet modules controlling services, so any node running
+the particular service will automatically get the required check commands
+defined as well, while nodes not running the service also do not contain
+the command check.
+
SELINUX
All files and directories are configured with correct selinux context. If
selinux is disabled, these contexts are ignored.
Known Problems
+
+
SSL/TLS support: Version 3 of NRPE supposedly has support for SSL/ TLs.
+However, at the time of writing this module, this seems to be buggy, as I
+was unable to start the NRPE service as soon as the
+ssl_cert_file line was uncommented in teh configuration file,
+despite having valid certs in the right position on the node. This happened
+when installing manually, not through this Puppet module. For that reason I
+included the $ne_enable_ssl boolean parameter, which is set to
+false by default, hence disabling SSL/TLS options until this
+has been fixed upstream, or a valid workaround has been found. Setting this
+option to true will include all SSL / TLS settings.
+
Support
@@ -277,7 +330,7 @@ environments.
diff --git a/doc/index.html b/doc/index.html
index b88e6a3..2ed5f17 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -132,9 +132,13 @@ structure (file system permissions, selinux context) through parameters
manage configuration files through parameters:
* nrpe.conf
* nrpe.cfg
- *
-commands.cfg (optional)
-* manage iptables (optionals )
+*
+manage sudo role for nagios user on NRPE clients
+* manage dynamic NRPE
+check command definitions
+* manage iptables (optional)
+* manage selinux
+rule exceptions (optional)
SERVICE
* manage NRPE service
@@ -213,16 +217,65 @@ through this modules. Defaults to true.
$ne_include_selinux : Whether to manage selinux exception
rules. Defaults to true.
+
+
$ne_enable_ssl : Whether to allow SSL settings. See known problems for more details.
+
+
$ne_allow_sudo : Whether to allow the nagios / nrpe user to
+use sudo by default. Controls both the
+settingcommand_prefixand application of a sudo rule. Defaults
+tofalse` as it usually is not required for most of the checks.
Managing Check Commands
+
In order to connect a Nagios monitoring server to clients through NRPE, you
+must define commands and the desired argument strings on the clients. The
+default NRPE installation comes with a few examples of such commands, which
+are also included in this module. However, every environment is very
+different in their requirements and Nagios via Puppet is all about the
+ability to dynamicically set command arguments based on default variables /
+overrides. For that reason no hard-coded commands are included, but instead
+all commands are set via argument strings, where possible.
+
+
The commands are created within /etc/nrpe.d/command.cfg , every set of
+instructions creates a new line.
+
+
Defining commands is as simple as
+that:
+<code>
+`cd_nrpe::commands::definitions` {
+'check_users':
+ `ne_check_cmd` =>
+'check_users',
+ `ne_cmd_argstring` => '-w $ARG1$ -c
+$ARG2$',
+ }
+</code>
+It is very recommendable to define such
+commands within Puppet modules controlling services, so any node running
+the particular service will automatically get the required check commands
+defined as well, while nodes not running the service also do not contain
+the command check.
+
SELINUX
All files and directories are configured with correct selinux context. If
selinux is disabled, these contexts are ignored.
Known Problems
+
+
SSL/TLS support: Version 3 of NRPE supposedly has support for SSL/ TLs.
+However, at the time of writing this module, this seems to be buggy, as I
+was unable to start the NRPE service as soon as the
+ssl_cert_file line was uncommented in teh configuration file,
+despite having valid certs in the right position on the node. This happened
+when installing manually, not through this Puppet module. For that reason I
+included the $ne_enable_ssl boolean parameter, which is set to
+false by default, hence disabling SSL/TLS options until this
+has been fixed upstream, or a valid workaround has been found. Setting this
+option to true will include all SSL / TLS settings.
+ Class manages all aspects of configuring selinux for NRPE.
+
+
Overview
+
+
+
+
cd_nrpe::selinux::config.pp # Module name: cd_nrpe
+Author: Arne Teuke
+(arne_teuke@ConfDroid.com)
+
+
License:
+
+
This file is part of cd_nrpe.
+
+
cd_nrpe is used for providing automatic configuration of NRPE
+ Copyright
+(C) 2016 ConfDroid (copyright@ConfDroid.com)
+ This program is free
+software: you can redistribute it and/or modify
+ it under the terms of the
+GNU General Public License as published by
+ the Free Software Foundation,
+either version 3 of the License, or
+ (at your option) any later version.
+
+
This program is distributed in the hope that it will be useful,
+ but
+WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY
+or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License
+for more details.
+
+
You should have received a copy of the GNU General Public License
+ along
+with this program. If not, see www.gnu.org/licenses/.
+
+
\ No newline at end of file
diff --git a/doc/puppet_defined_types/cd_nrpe_3A_3Acommands_3A_3Adefinitions.html b/doc/puppet_defined_types/cd_nrpe_3A_3Acommands_3A_3Adefinitions.html
index 78443bd..4227fdf 100644
--- a/doc/puppet_defined_types/cd_nrpe_3A_3Acommands_3A_3Adefinitions.html
+++ b/doc/puppet_defined_types/cd_nrpe_3A_3Acommands_3A_3Adefinitions.html
@@ -173,6 +173,25 @@ the custom location
, i.e. -w $ARG1$ -c
$ARG2$. See the arguments in th eman pages for the
checks.
+
+
+
+
+