release new nagios stuff, should be much more modular now and using native types by puppet

1 files changed, 24 insertions, 13 deletions

diff --git a/README b/README
index 8739944..6385353 100644
--- a/README
+++ b/README
@@ -1,36 +1,47 @@
+Introduction/Notes
+==================
+
+This modules was inspired and based on the work of David Schmitt
+The immerda project group adapted and improved this module. 
+Mainly we made it using the new native puppet nagios commands
+as well we made it more modular to fit for multidistro usage.
+However as we used Centos, we couldn't test the original Debian
+extension of David Schmitt, integration of more distros have to prove
+this concept.
+
 Overview
 ========
 
-To use the nagios2 resources, activate storeconfigs on the puppetmaster.
+To use the nagios resources, activate storeconfigs on the puppetmaster.
 
 Monitor
 -------
 
-On one node the "nagios2" class has to be included. This installes nagios2 and
-apache2 and configures the cgi on http://node/nagios2/
+On one node the "nagios" class has to be included. This installes nagios and
+apache2 and installs the cgi 
 
 
 Hosts
 -----
 
-On a node which shall be monitored with nagios, include the "nagios2::target".
+On a node which shall be monitored with nagios, include the "nagios::target".
 This just creates a host declaration for this hosts "$fqdn".
 Set the $nagios_parent variable in the node scope for enabling the reachability
-features of nagios2. If a node needs more customisation, use the
-"nagios2::host" component directly.
+features of nagios. If a node needs more customisation, use the
+"nagios::host" component directly.
 
-To monitor hosts not managed by puppet, add "nagios2::extra_host"s to the
+To monitor hosts not managed by puppet, add "nagios::extra_host"s to the
 monitoring node. These can be used as intermediate $nagios_parent's
 
 
 Services
 --------
 
-Services can be monitored by using the "nagios2::service" component.
+Services can be monitored by using the "nagios::service" component.
 
 The simplest form is::
 
-	nagios2::service { check_dns: }
+	nagios::service { check_dns: }
 
 The intention being obviously to put such declarations into a component defining
 a service, thereby being automatically applied together with all instances of
@@ -57,7 +68,7 @@ Consistency/Validation/Verification
 After convergance of the configuration, the system is obviously consistent.
 That is, all defined services are monitored. The problem is though, that it is
 neither automatically valid - it is not guaranteed that all components declare a
-nagios2::service - and even if the configuration is valid it definitly is
+nagios::service - and even if the configuration is valid it definitly is
 unverified, since that is always a judgment call for an external observer.
 
 
@@ -69,10 +80,10 @@ Usage example::
 
 node nagios {
 
-	include nagios2
+	include nagios
 
 	# Declare another nagios command
-	nagios2::command { http_port: command_line
+	nagios::command { http_port: command_line
 => '/usr/lib/nagios/plugins/check_http -p $ARG1$ -H $HOSTADDRESS$ -I
 $HOSTADDRESS$'
 
@@ -100,7 +111,7 @@ node target {
 	include apache2
 
 	# This actually does this somewhere:
-	#nagios2::service { "http_${apache2_port}":
+	#nagios::service { "http_${apache2_port}":
 	#       check_command => "http_port!${apache2_port}"
 	#}