[Pkg-nagios-changes] [SCM] Debian packaging for mod gearman. branch, upstream, updated. e9a5a6997d9dd8b31b433b5bcbad495448db0131

Thu Apr 7 08:06:21 UTC 2011

The following commit has been merged in the upstream branch:
commit 18a620a6ae9491195304b7834ce37ad1d06bcdb1
Author: Sven Nierlein <sven at nierlein.de>
Date:   Mon Mar 7 14:16:24 2011 +0100

    added common scenarios

diff --git a/README.asciidoc b/README.asciidoc
index 7a7cb58..67259c8 100644
--- a/README.asciidoc
+++ b/README.asciidoc
@@ -41,7 +41,7 @@ The NEB module starts a single thread, which monitors the
 'check_results' where all results come in.
 
 ++++
-<a title="mod gearman architecture" rel="lightbox[mod_gm]" href="http://labs.consol.de/wp-content/uploads/2010/09/mod_gearman-e1284455350110.png"><img src="http://labs.consol.de/wp-content/uploads/2010/09/mod_gearman-e1284455350110.png" alt="mod_gearman architecture " width="480" height="300" style="float:none" /></a>
+<a title="mod gearman architecture" rel="lightbox[mod_gm]" href="http://labs.consol.de/wp-content/uploads/2010/09/mod_gearman-e1284455350110.png"><img src="http://labs.consol.de/wp-content/uploads/2010/09/mod_gearman-e1284455350110.png" alt="mod_gearman architecture" width="480" height="300" style="float:none" /></a>
 ++++
 
 A simple example queue would look like:
@@ -109,6 +109,53 @@ worker on each queue to share the load.
 ++++
 
 
+Common Scenarios
+----------------
+
+Load Balancing
+~~~~~~~~~~~~~~
+
+++++
+<a title="Load Balancing" rel="lightbox[mod_gm]"
+href="http://labs.consol.de/wp-content/uploads/2010/09/sample_load_balancing.png"><img
+src="http://labs.consol.de/wp-content/uploads/2010/09/sample_load_balancing.png"
+alt="Load Balancing" width="300" height="125" style="float:none" /></a>
+++++
+
+The easiest variant is a simple load balancing. For example if your
+single nagios box just cannot handle the load, you could just add a
+worker in the same network (or even on the same host) to reduce your
+load on the nagios box. Therefor we just enable hosts, services and
+eventhandler on the server and the worker.
+
+
+Distributed Monitoring
+~~~~~~~~~~~~~~~~~~~~~~
+
+++++
+<a title="Distributed Monitoring" rel="lightbox[mod_gm]" href="http://labs.consol.de/wp-content/uploads/2010/09/sample_distributed.png"><img src="http://labs.consol.de/wp-content/uploads/2010/09/sample_distributed.png" alt="Distributed Monitoring" width="350" height="125" style="float:none" /></a>
+++++
+
+If your checks have to be run from different network segments, then
+you can use the hostgroups (or servicegroups) to define a hostgroup
+for specific worker. The general hosts and services queue is disabled
+for this worker and just the hosts and services from the given
+hostgroup will be processed.
+
+
+Distributed Monitoring with Load Balancing
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+++++
+<a title="Distributed Monitoring with Load Balancing" rel="lightbox[mod_gm]" href="http://labs.consol.de/wp-content/uploads/2010/09/sample_distributed_load_balanced.png"><img src="http://labs.consol.de/wp-content/uploads/2010/09/sample_distributed_load_balanced.png" alt="Distributed Monitoring with Load Balancing" width="350" height="225" style="float:none" /></a>
+++++
+
+Your distributed setup could easily be extended to a load balanced
+setup with just adding more worker of the same config.
+
+
+
+
 Installation
 ------------
 
@@ -659,6 +706,8 @@ Hints
  - If you have some checks which should not run parallel, just setup a
    single worker with --max-worker=1 and they will be executed one
    after another. For example for cpu intesive checks with selenium.
+ - Make sure all your worker have the nagios-plugins available under
+   the same path. Otherwise they could'nt be found by the worker.
 
 
 
diff --git a/docs/README.html b/docs/README.html
index db03812..7f4595b 100644
--- a/docs/README.html
+++ b/docs/README.html
@@ -619,7 +619,7 @@ against the hostgroups and if none matches they will be sent into a
 generic <em>service</em> queue.
 The NEB module starts a single thread, which monitors the
 <em>check_results</em> where all results come in.</p></div>
-<a title="mod gearman architecture" rel="lightbox[mod_gm]" href="http://labs.consol.de/wp-content/uploads/2010/09/mod_gearman-e1284455350110.png"><img src="http://labs.consol.de/wp-content/uploads/2010/09/mod_gearman-e1284455350110.png" alt="mod_gearman architecture " width="480" height="300" style="float:none" /></a>
+<a title="mod gearman architecture" rel="lightbox[mod_gm]" href="http://labs.consol.de/wp-content/uploads/2010/09/mod_gearman-e1284455350110.png"><img src="http://labs.consol.de/wp-content/uploads/2010/09/mod_gearman-e1284455350110.png" alt="mod_gearman architecture" width="480" height="300" style="float:none" /></a>
 <div class="paragraph"><p>A simple example queue would look like:</p></div>
 <div class="listingblock">
 <div class="content">
@@ -698,6 +698,30 @@ worker which covers the other queues. There can be more than one
 worker on each queue to share the load.</p></div>
 <a title="mod gearman queues" rel="lightbox[mod_gm]" href="http://labs.consol.de/wp-content/uploads/2010/09/mod_gearman_queues.png"><img src="http://labs.consol.de/wp-content/uploads/2010/09/mod_gearman_queues.png" alt="mod_gearman architecture " width="360" height="270" style="float:none" /></a>
 </div>
+<h2 id="_common_scenarios">Common Scenarios</h2>
+<div class="sectionbody">
+<h3 id="_load_balancing">Load Balancing</h3><div style="clear:left"></div>
+<a title="Load Balancing" rel="lightbox[mod_gm]"
+href="http://labs.consol.de/wp-content/uploads/2010/09/sample_load_balancing.png"><img
+src="http://labs.consol.de/wp-content/uploads/2010/09/sample_load_balancing.png"
+alt="Load Balancing" width="300" height="125" style="float:none" /></a>
+<div class="paragraph"><p>The easiest variant is a simple load balancing. For example if your
+single nagios box just cannot handle the load, you could just add a
+worker in the same network (or even on the same host) to reduce your
+load on the nagios box. Therefor we just enable hosts, services and
+eventhandler on the server and the worker.</p></div>
+<h3 id="_distributed_monitoring">Distributed Monitoring</h3><div style="clear:left"></div>
+<a title="Distributed Monitoring" rel="lightbox[mod_gm]" href="http://labs.consol.de/wp-content/uploads/2010/09/sample_distributed.png"><img src="http://labs.consol.de/wp-content/uploads/2010/09/sample_distributed.png" alt="Distributed Monitoring" width="350" height="125" style="float:none" /></a>
+<div class="paragraph"><p>If your checks have to be run from different network segments, then
+you can use the hostgroups (or servicegroups) to define a hostgroup
+for specific worker. The general hosts and services queue is disabled
+for this worker and just the hosts and services from the given
+hostgroup will be processed.</p></div>
+<h3 id="_distributed_monitoring_with_load_balancing">Distributed Monitoring with Load Balancing</h3><div style="clear:left"></div>
+<a title="Distributed Monitoring with Load Balancing" rel="lightbox[mod_gm]" href="http://labs.consol.de/wp-content/uploads/2010/09/sample_distributed_load_balanced.png"><img src="http://labs.consol.de/wp-content/uploads/2010/09/sample_distributed_load_balanced.png" alt="Distributed Monitoring with Load Balancing" width="350" height="225" style="float:none" /></a>
+<div class="paragraph"><p>Your distributed setup could easily be extended to a load balanced
+setup with just adding more worker of the same config.</p></div>
+</div>
 <h2 id="_installation">Installation</h2>
 <div class="sectionbody">
 <h3 id="_omd">OMD</h3><div style="clear:left"></div>
@@ -1500,6 +1524,12 @@ If you have some checks which should not run parallel, just setup a
    after another. For example for cpu intesive checks with selenium.
 </p>
 </li>
+<li>
+<p>
+Make sure all your worker have the nagios-plugins available under
+   the same path. Otherwise they could&#8217;nt be found by the worker.
+</p>
+</li>
 </ul></div>
 </div>
 <h2 id="_download">Download</h2>
@@ -1569,7 +1599,7 @@ The source is available at GitHub: <a href="http://github.com/sni/mod_gearman">h
 <div id="footnotes"><hr /></div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2011-03-05 16:22:31 CEST
+Last updated 2011-03-07 14:19:11 CEST
 </div>
 </div>
 </body>
diff --git a/docs/sample_distributed.png b/docs/sample_distributed.png
new file mode 100644
index 0000000..ac6b48a
Binary files /dev/null and b/docs/sample_distributed.png differ
diff --git a/docs/sample_distributed.pptx b/docs/sample_distributed.pptx
new file mode 100644
index 0000000..775ec59
Binary files /dev/null and b/docs/sample_distributed.pptx differ
diff --git a/docs/sample_distributed_load_balanced.png b/docs/sample_distributed_load_balanced.png
new file mode 100644
index 0000000..a6f845a
Binary files /dev/null and b/docs/sample_distributed_load_balanced.png differ
diff --git a/docs/sample_distributed_load_balanced.pptx b/docs/sample_distributed_load_balanced.pptx
new file mode 100644
index 0000000..77d6bb1
Binary files /dev/null and b/docs/sample_distributed_load_balanced.pptx differ
diff --git a/docs/sample_load_balancing.png b/docs/sample_load_balancing.png
new file mode 100644
index 0000000..ca84744
Binary files /dev/null and b/docs/sample_load_balancing.png differ
diff --git a/docs/sample_load_balancing.pptx b/docs/sample_load_balancing.pptx
new file mode 100644
index 0000000..a1a5696
Binary files /dev/null and b/docs/sample_load_balancing.pptx differ

-- 
Debian packaging for mod gearman.

