recommit for updates in build 4

This commit is contained in:
Jenkins ConfDroid
2018-12-07 18:19:09 +01:00
parent 6b566a5bb2
commit 68e5bec0d7
21 changed files with 418 additions and 496 deletions

View File

@@ -6,7 +6,7 @@
<title>
File: README
&mdash; Documentation by YARD 0.9.12
&mdash; Documentation by YARD 0.9.16
</title>
@@ -58,12 +58,9 @@
</div>
<div id="content"><div id='filecontents'>
<p>|Repo Name| version | Build
Status|
|---|---|---|---|
|<code>cd_nrpe</code>| 0.0.1.1 | <a
href="https://pipelines.confdroid.com/buildStatus/icon?job=cd_nrpe">{Build
Status</a>/]|</p>
<p>|Repo Name| version | Build Status| |—|—|—|—| |<code>cd_nrpe</code>|
0.0.1.1 | <a href="https://pipelines.confdroid.com/job/cd_nrpe/"><img
src="https://pipelines.confdroid.com/buildStatus/icon?job=cd_nrpe"></a>|</p>
<h3 id="label-Synopsis">Synopsis</h3>
@@ -85,65 +82,54 @@ production!!! __**</code></p>
<h3 id="label-Table+of+Contents">Table of Contents</h3>
<ul><li>
<p><a href="#features">Features</a></p>
<p><a href="#label-Features">Features</a></p>
</li><li>
<p><a
href="https://gitlab.confdroid.com/12WW1160/cd_nrpe/blob/master/REPOSTRUCTURE.md">Repo
Structure</a></p>
</li><li>
<p><a href="#repo-documentation">Repo Documention</a></p>
<p><a href="#label-Repo+documentation">Repo Documention</a></p>
</li><li>
<p><a href="#dependencies">Dependencies</a></p>
<p><a href="#label-Dependencies">Dependencies</a></p>
</li><li>
<p><a href="#deployment">Deployment</a></p>
<p><a href="#label-Deployment">Deployment</a></p>
</li><li>
<p><a href="#native-puppet-deployment">native Puppet deployment</a></p>
<p><a href="#label-Native+puppet+deployment">native Puppet deployment</a></p>
</li><li>
<p><a href="#through-foreman">through Foreman</a></p>
<p><a href="#label-Through+foreman">through Foreman</a></p>
</li><li>
<p><a href="#parameters">Parameters</a></p>
<p><a href="#label-Parameters">Parameters</a></p>
</li><li>
<p><a href="#managing-check-commands">Managing Check Commands</a></p>
<p><a href="#label-Managing+check+commands">Managing Check Commands</a></p>
</li><li>
<p><a href="#selinux">SELINUX</a></p>
<p><a href="#label-Selinux">SELINUX</a></p>
</li><li>
<p><a href="#known-problems">Known Problems</a></p>
<p><a href="#label-Known+problems">Known Problems</a></p>
</li><li>
<p><a href="#support">Support</a></p>
<p><a href="#label-Support">Support</a></p>
</li><li>
<p><a href="#tests">Tests</a></p>
<p><a href="#label-Tests">Tests</a></p>
</li><li>
<p><a
href="https://gitlab.confdroid.com/12WW1160/cd_nrpe/blob/master/CHANGELOG.md">Changelog</a></p>
</li><li>
<p><a href="https://confdroid.com/contact/">Contact Us</a></p>
</li><li>
<p><a href="#disclaimer">Disclaimer</a></p>
<p><a href="#label-Disclaimer">Disclaimer</a></p>
</li></ul>
<h3 id="label-Features">Features</h3>
<p>INSTALLATION
* install nrpe binaries</p>
<p>INSTALLATION * install nrpe binaries</p>
<p>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
<p>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)</p>
<p>SERVICE
* manage NRPE service</p>
<p>SERVICE * manage NRPE service</p>
<h3 id="label-Repo+Structure">Repo Structure</h3>
@@ -185,10 +171,10 @@ Only if you want to override settings declare it specifically.</p>
<p>via site.pp or nodes.pp</p>
<pre class="code ruby"><code class="ruby">node &#39;example.example.net&#39; {
include cd_puppetdb
include nrpe
}</code></pre>
<h4 id="label-through+Foreman%3A">through Foreman:</h4>
<h4 id="label-through+Foreman-3A">through Foreman:</h4>
<p>In order to apply parameters through Foreman,
<strong>cd_nrpe::params</strong> must be added to the host or hostgroup in
@@ -203,7 +189,7 @@ details about class deployment on Confdroid.com</a>.</p>
<p>The following parameters are editable via params.pp or through ENC
(<strong>recommended</strong>). Values changed will take immediate effect
at next puppet run. Services will be restarted where neccessary. If you
want to override parameters, the <a href="#through-foreman">module must be
want to override parameters, the <a href="#label-Through+foreman">module must be
specifically declared to hosts when using ENC</a>.</p>
<p>The <a href="https://confdroid.com/2017/07/cd_nrpe-parameters/">full list
@@ -229,7 +215,7 @@ through this modules. Defaults to <code>true</code>.</p>
rules. Defaults to <code>true</code>.</p>
</li><li>
<p><code>$ne_enable_ssl</code> : Whether to allow SSL settings. See <a
href="#konwn-problems">known problems</a> for more details.</p>
href="#label-Konwn+problems">known problems</a> for more details.</p>
</li><li>
<p><code>$ne_allow_sudo : Whether to allow the nagios / nrpe user to
use sudo by default. Controls both the
@@ -251,24 +237,17 @@ all commands are set via argument strings, where possible.</p>
<p>The commands are created within /etc/nrpe.d/command.cfg , every set of
instructions creates a new line.</p>
<p>Defining commands is as simple as
that:
&lt;code&gt;
cd_nrpe::commands::definitions { &#39;check_users&#39;:
ne_check_cmd =&gt; &#39;check_users&#39;,
ne_cmd_argstring
=&gt; &#39;-w $ARG1$ -c $ARG2$&#39;,
}
&lt;/code&gt;
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.</p>
<p>Defining commands is as simple as that: <code>
cd_nrpe::commands::definitions { &#39;check_users&#39;: ne_check_cmd
=&gt; &#39;check_users&#39;, ne_cmd_argstring =&gt; &#39;-w $ARG1$
-c $ARG2$&#39;, } </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.</p>
<h3 id="label-SELINUX">SELINUX</h3>
@@ -348,8 +327,7 @@ with PuppetDB (see tests/UTF_Files)</p>
<p>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.</p>