zenoss/manifests/sample-init.pp zenoss/plugins/puppet/provider/zenoss.rb zenoss/plugins/puppet/type/zenoss_host.rb @@ -1,13 +1,24 @@ 1 Automatically add Puppet clients to Zenoss -1.1 How devices are added in Zenoss with Puppet +1.1 Setup the module + +1. Copy the 'zenoss' module to the other puppet modules. +2. Adapt the 'manifests/sample-init.pp' acording to your needs an rename it to 'init.pp'. + This is only a sample! +3. There are several parameters that are provided by Facter, you need to take care of that too (see the 'inzenoss' parameter for more information). +4. The parameter 'zenosstype' is a so called "munge value" you may want to change that too (see 'zenoss/plugins/puppet/type/zenoss_host.rb') + +1.2 How devices are added in Zenoss with Puppet In short: 1. Puppet clients with puppet class zenoss::client export their properties as Zenoss_host type to the puppet master database. 2. The puppet client with the puppet class zenoss::server iterates through all the Zenoss_host types in the puppet master DB and runs the logic provided by the Zenoss_host type and the Zenoss provider, which adds puppet clients to zenoss that were not added yet. +3. See "sample-init.pp" for an sample init.pp configuration. + +1.3 How this plugin works -1.1.1 Zenoss_host type +1.3.1 Zenoss_host type The Zenoss_host type is a puppet type which represents a host that is managed by puppet and should be monitored by zenoss: @@ -21,7 +32,7 @@ The retrieve method of a property returns the current state of the property. Thu The defaultto value specifies what the state of the property should be and the method attached to the target state (value) of the property specifies how this state can be achieved (e.g. how a host is added to Zenoss). These methods normally execute functionality implemented in the provider. -1.1.2 Zenoss provider +1.3.2 Zenoss provider The Zenoss provider provides the implementation of the methods to check whether a host was already added, to add a host as a device and to rename a device. @@ -29,7 +40,7 @@ modules/zenoss/plugins/puppet/provider/zenoss_host/zenoss.rb It doesn't execute anything on its own; it is always called by the Zenoss_host type if necessary. -1.1.3 Zenoss module manifest +1.3.3 Zenoss module manifest In the manifest is specified that a Zenoss_host type for every puppet managed host with the puppet class zenoss::client is exported to the puppet master database. It also specifies a puppet class zenoss::server which is configured to iterate through all Zenoss_host types in the puppet master database and check if the properties are set correctly, i.e. if the host was already added to and renamed in zenoss. @@ -58,3 +69,5 @@ This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License version 3 as published by the Free Software Foundation. + + README plugins/puppet/provider/zenoss.rb plugins/puppet/type/zenoss_host.rb 1b7458fb8d8c17504a76ec62349c8dfc548226db Bob the Builder bobthebuilder@constructionsite.com http://github.com/mamba/puppet-zenoss/commit/25e43e2050c19faee68642ac7f0fae06a407b5a7 25e43e2050c19faee68642ac7f0fae06a407b5a7 2009-11-06T02:53:16-08:00 2009-11-06T02:53:16-08:00 switched to a more complete module structure, provided sample init.pp and added short installation instructions 30d892f06018cb94788ceca277b9fc7ade153452 Bob the Builder bobthebuilder@constructionsite.com