Documentation by YARD 0.9.9
+Documentation by YARD 0.9.16
Alphabetic Index
@@ -93,6 +93,11 @@ +File Listing
-
@@ -176,9 +183,7 @@
diff --git a/CHANGELOG.md b/CHANGELOG.md index 3e837a1..2a12acb 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,502 +8,582 @@ Changelog of Git Changelog.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
|Repo Name| version | Build
-Status|
-|---|---|---|---|
-|cd_nrpe| 0.0.1.1 | {Build
-Status/]|
|Repo Name| version | Build Status| |—|—|—|—| |cd_nrpe|
+0.0.1.1 | |
INSTALLATION -* install nrpe binaries
+INSTALLATION * install nrpe binaries
-CONFIGURATION -* manage NRPE service user properties -* manage directory -structure (file system permissions, selinux context) through parameters -* -manage configuration files through parameters: - * nrpe.conf - * nrpe.cfg -* -manage sudo role for nagios user on NRPE clients -* manage dynamic NRPE -check command definitions -* manage iptables (optional) -* manage selinux +
CONFIGURATION * manage NRPE service user properties * manage directory +structure (file system permissions, selinux context) through parameters * +manage configuration files through parameters: * nrpe.conf * nrpe.cfg * +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
+SERVICE * manage NRPE service
All dependencies must be included in the catalogue.
cd_resources +href="https://gitlab.confdroid.com/12WW1160/cd_resources">cd_resources to manage YUM repositories.
cd_firewall or puppetlabs firewall to manage iptables
cd_stdlib or +
cd_stdlib or puppetlabs stdlib to facilitate concat
cd_concat or +
cd_concat or puppetlabs concat for concatenating files
via site.pp or nodes.pp
node 'example.example.net' {
- include cd_puppetdb
+ include nrpe
}
-In order to apply parameters through Foreman, cd_nrpe::params must be added to the host or hostgroup in @@ -204,7 +189,7 @@ details about class deployment on Confdroid.com.
The following parameters are editable via params.pp or through ENC (recommended). Values changed will take immediate effect at next puppet run. Services will be restarted where neccessary. If you -want to override parameters, the module must be +want to override parameters, the module must be specifically declared to hosts when using ENC.
The full list
@@ -230,7 +215,7 @@ through this modules. Defaults to true.
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
@@ -252,24 +237,17 @@ 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 directly within Puppet modules or -profiles, so any node running the particular service controlled by the -module will automatically get the required check commands defined as well, -while nodes not running the service also do not contain the command check. -The same then is true for Nagios checks, so you would have both the NRPE -command definition and the Nagios check contained in Puppet modules or -profiles to have it in once location.
+Defining commands is as simple as that:
+cd_nrpe::commands::definitions { 'check_users': ne_check_cmd
+=> 'check_users', ne_cmd_argstring => '-w $ARG1$
+-c $ARG2$', } It is very recommendable to define such
+commands directly within Puppet modules or profiles, so any node running
+the particular service controlled by the module will automatically get the
+required check commands defined as well, while nodes not running the
+service also do not contain the command check. The same then is true for
+Nagios checks, so you would have both the NRPE command definition and the
+Nagios check contained in Puppet modules or profiles to have it in once
+location.
ConfDroid as entity is entirely independent from Puppet. We provide custom configuration modules, written for specific purposes and specific -environments. -The modules are tested and supported only as documented, and +environments. The modules are tested and supported only as documented, and require testing in designated environments (i.e. lab or development environments) for parameter tuning etc. before deploying into production environments.
cd_nrpe::main::exec.pp Module name: cd_nrpe Author: Arne Teuke +(arne_teuke@ConfDroid.com)
+ +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/.
+ +
+ + + +23 +24 +25 +26 +27 +28 +29 +30 +31 +32 +33 +34 +35 +36 +37 +38 +39 +40+ |
+
+ # File 'manifests/main/exec.pp', line 23
+
+class cd_nrpe::main::exec (
+
+) inherits cd_nrpe::params {
+
+ # create policy file fpr sudo selinux policy
+# exec { 'create_nrpe_pp':
+# command => template($ne_checkmodule_nrpe_erb),
+# user => 'root',
+# creates => $ne_nrpe_pp_file,
+# notify => Exec['import_nrpe_policy'],
+# }
+
+ # execute policy file
+# exec { 'import_nrpe_policy':
+# command => template
+#
+# }
+}
+ |
+