Hello all. Probably this question has already been posed in the context of another software, but I am unable to find it. I would like to implement a module which should manage munin-clients as well as the munin-server. Here is what I am thinking about implementing: - There are two classes: munin::client and munin::server - munin::clients'' configuration will be managed automatically. This is easy. - munin::server should also be managed automatically, but here the solution is not so clear to me. Following these pages: http://mail.madstop.com/pipermail/puppet-users/2007-January/000926.html http://reductivelabs.com/trac/puppet/wiki/BracketEditor http://reductivelabs.com/trac/puppet/wiki/SimpleTextRecipes I get the impression that the munin-server has to be the same host than the puppet server. I am thinking of taking the above recipes to generate the munin.conf. But how do I deploy it then? To manage the server and the clients with minimum effort, I thought that it should be enough to have one (or more) nodes in the munin::server class, and nodes in the munin::client class. The idea is now, that for every munin::client, a configuration snipplet is maintained on the puppetmaster. Each munin::server''s munin.conf ist then maintained like in the examples above. I do not know how to implement this. The puppetmaster would have to keep the directory where the node-snipplets reside in sync. For this, it would be necessary, that the puppetmaster generates a munin.conf snipplet locally for every node that is in munin::client. Is this possible? Thanks, and have a nice day, udo.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 26 May 2007, Udo Waechter wrote:> Hello all. > > Probably this question has already been posed in the context of another > software, but I am unable to find it. > > I would like to implement a module which should manage munin-clients as > well as the munin-server. > > Here is what I am thinking about implementing: > > - There are two classes: munin::client and munin::server > - munin::clients'' configuration will be managed automatically. This is > easy. - munin::server should also be managed automatically, but here the > solution is not so clear to me.Take a look at my manifest at http://club.black.co.at:82/svn/manifests/trunk/manifests/classes/munin.pp http://club.black.co.at:82/svn/manifests/trunk/doc/README.munin Regards, David - -- - - hallo... wie gehts heute? - - *hust* gut *rotz* *keuch* - - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGWV9a/Pp1N6Uzh0URAjdCAJ0duxgjMOtUcloZYUAAvJx/zaDXaACfawlJ evtwNNP+5Bht5C7kiEUadY0=KsBx -----END PGP SIGNATURE-----
Thank you for writing this manifest.
I have grabbed it, and it works great. I have also extended it to also
manage Mac OS X munin nodes, where we do not have the munin-node
package, but can use the snmp functionality of munin to get information
from the clients.
I have also made it a module, such that the whole package is distributed
easier.
I have also found an error in the README. I have to use
munin::default_client instead of munin::client as written in the docs.
would be better to refactor the class, such that the README is right
again. I think munin::client is more intuitive.
I am planning to make the module public, but where? I do not have a
publicly available svn repository at hand, I have to think of something
else.
Anyway, one thing that I would like to implement is the possiblility to
also create custom graphs on the munin::host.
To achieve this I still have some questions, and it would be great if
someone could point me into the right direction.
What I would like to have at least: Create graphs for each monitored domain.
Example:
[test.de;Totals]
update no
load1.graph_title Loads side by side
load1.graph_order host1=host1.test.de:load.load
host2=host2.test.de:load.load #all hosts from domain test.de
The main problem that I have is: How do I collect all hosts from a
certain domain? Ideally this should be done on the munin::host.
If the munin::host is able to collect all hostnames and domains of all
the munin::client in the network it could create the
''.graph_order'' line
from the example above.
Using templates, creating the above section would then be as easy as it
looks.
Is this possible in puppet? I guess it is.
An alternative would be to annotate the configuration snipplets that the
munin::clients create with some special comments that contain the
information needed:
- In which graph to add this host itself( "[$domain;Totals]", for
example)
- the id of the graph ("load1", for example)
- the ''graph_order'' field above.
Then, some small parser of those annotations would be needed on the
munin::host, which would add or remove the host to the apropiate graph
in the ''graph_order'' line.
I am experimenting with this alternative right now, lets see what comes out.
Thanks and have a nice day,
udo
David Schmitt wrote:> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Saturday 26 May 2007, Udo Waechter wrote:
>> Hello all.
>>
>> Probably this question has already been posed in the context of another
>> software, but I am unable to find it.
>>
>> I would like to implement a module which should manage munin-clients as
>> well as the munin-server.
>>
>> Here is what I am thinking about implementing:
>>
>> - There are two classes: munin::client and munin::server
>> - munin::clients'' configuration will be managed automatically.
This is
>> easy. - munin::server should also be managed automatically, but here
the
>> solution is not so clear to me.
>
> Take a look at my manifest at
>
> http://club.black.co.at:82/svn/manifests/trunk/manifests/classes/munin.pp
> http://club.black.co.at:82/svn/manifests/trunk/doc/README.munin
>
>
>
>
> Regards, David
>
> - --
> - - hallo... wie gehts heute?
> - - *hust* gut *rotz* *keuch*
> - - gott sei dank kommunizieren wir über ein septisches medium ;)
> -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGWV9a/Pp1N6Uzh0URAjdCAJ0duxgjMOtUcloZYUAAvJx/zaDXaACfawlJ
> evtwNNP+5Bht5C7kiEUadY0> =KsBx
> -----END PGP SIGNATURE-----
> _______________________________________________
> Puppet-users mailing list
> Puppet-users@madstop.com
> https://mail.madstop.com/mailman/listinfo/puppet-users
>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 28 May 2007, Udo Waechter wrote:> Thank you for writing this manifest.Thank you for your feedback!> I have grabbed it, and it works great. I have also extended it to also > manage Mac OS X munin nodes, where we do not have the munin-node > package, but can use the snmp functionality of munin to get information > from the clients. > > I have also made it a module, such that the whole package is distributed > easier. > I have also found an error in the README. I have to use > munin::default_client instead of munin::client as written in the docs. > would be better to refactor the class, such that the README is right > again. I think munin::client is more intuitive.There is already a munin::client define. If you need default parameters, you can just "include munin::default_client", if you need finegrained control use the define directly with "munin::client { blah: port => 4999 }". I have added a bit more about the classes to the README.> I am planning to make the module public, but where? I do not have a > publicly available svn repository at hand, I have to think of something > else.There is always the PRM: http://prmweb.hezmatt.org/ I''m currently stalled on development of my manifests due to my masters thesis, but if you want, I can put your module on my SVN.> Anyway, one thing that I would like to implement is the possiblility to > also create custom graphs on the munin::host. > To achieve this I still have some questions, and it would be great if > someone could point me into the right direction. > > What I would like to have at least: Create graphs for each monitored > domain. > > Example: > [test.de;Totals] > update no > load1.graph_title Loads side by side > load1.graph_order host1=host1.test.de:load.load > host2=host2.test.de:load.load #all hosts from domain test.de > > The main problem that I have is: How do I collect all hosts from a > certain domain? Ideally this should be done on the munin::host. > > If the munin::host is able to collect all hostnames and domains of all > the munin::client in the network it could create the ''.graph_order'' line > from the example above. > Using templates, creating the above section would then be as easy as it > looks. > Is this possible in puppet? I guess it is.Restructure the configfile snippets so that they are exported into a hierarchy as you wish them to have. Probably $NODESDIR/$fqdn/$hostname. Then wirte a small script along the lines of "cd $NODESDIR; for fqdn in "*"; do cd "$fqdn"; for host in "*"; do create_snippet.sh; done; done" Templates are executed on the puppetmaster. You can do this in a template only if you start collecting files there too. I''d rather do it on the munin::host with a little shellscript.> An alternative would be to annotate the configuration snipplets that the > munin::clients create with some special comments that contain the > information needed: > - In which graph to add this host itself( "[$domain;Totals]", for example) > - the id of the graph ("load1", for example) > - the ''graph_order'' field above. > > Then, some small parser of those annotations would be needed on the > munin::host, which would add or remove the host to the apropiate graph > in the ''graph_order'' line. > > I am experimenting with this alternative right now, lets see what comes > out.Great! I''d be delightet to hear more from this! Regards, David - -- - - hallo... wie gehts heute? - - *hust* gut *rotz* *keuch* - - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGWr5f/Pp1N6Uzh0URAtTxAKCf+SVdyF+CYhfvr3y9LW2zzcUw2ACglixu ywlHopMp/hABFqHFovVBeHs=ZIyb -----END PGP SIGNATURE-----
Thijs Oppermann
2007-May-28 17:06 UTC
Re: munin module: manage clients and server''s config
On 28/05/07, Udo Waechter <udo.waechter@uni-osnabrueck.de> wrote:> > > I am planning to make the module public, but where? I do not have a > publicly available svn repository at hand, I have to think of something > else. > >You could start by attaching the files to a post to this list. A lot of us are interested in how others are creating their manifests for puppet. Gr, Thijs _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
Dear all, finally I have found the time to complete the munin-module based on the code written by David Schmitt. I attach the current versionfor all of you to comment on it and please give me feedback. What I have implemented: - munin::client now automatically detects darwin and debian hosts. - darwin hosts are handled via snmp (could also be windows or any other snmp-device) - munin::host additionally is configured to create summary graphs for a domain. - this is implemented via a special syntax and then parsed by a small ruby script to get the configuration one wants to have. currently only load.load is summed up, this can be extended. Please do test the module and tell me what works and what not. I have the following problems: - it seems that the list of hosts is not updated every time puppet runs on the munin::host. The clients are all in the database, but the munin::host does not ''see'' them. - sometimes Puppet::Resource::param is empty, which means that the database somehow got corrupted. I can not really reproduce this error, it simpy happens from time to time. Until now, I have truncated the tables... this is no real solution though. It would be cool to configure the type of summary graphs via the same mechanisms that munin::plugin does. Currently I only have the need for load.load graphs, thus it the current solution is the most simple one. Another thing: the ''remotefile'' function does not seem to be ''module'' aware. I have the strange hack to set ''module => false'' in those calls of this function whcih come from a module... strange, ey? Can someone think of a solution to get rid of this? i did not think very much about it yet, might be the case that I figure it out myself. Hope you enjoy it, udo. Thijs Oppermann wrote:> On 28/05/07, *Udo Waechter* <udo.waechter@uni-osnabrueck.de > <mailto:udo.waechter@uni-osnabrueck.de>> wrote: > > > I am planning to make the module public, but where? I do not have a > publicly available svn repository at hand, I have to think of something > else. > > > > You could start by attaching the files to a post to this list. A lot of > us are interested in how others are creating their manifests for puppet. > > Gr, > Thijs > > > ------------------------------------------------------------------------ > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users_______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
Thijs Oppermann
2007-Jun-07 11:20 UTC
Re: munin module: manage clients and server''s config
Hey Udo, Nice. I''ve been looking at your module, trying it out. I get an error however: err: Invalid parameter ''"module"'' for type ''remotefile'' at /etc/puppet/modules/munin/manifests/init.pp Seems you have customised your remotefile definition? Care to share? ;) Gr, Thijs On 06/06/07, Udo Waechter <udo.waechter@uni-osnabrueck.de> wrote:> > Dear all, > finally I have found the time to complete the munin-module based on the > code written by David Schmitt. > I attach the current versionfor all of you to comment on it and please > give me feedback. > What I have implemented: > > - munin::client now automatically detects darwin and debian hosts. > - darwin hosts are handled via snmp (could also be windows or > any other snmp-device) > - munin::host additionally is configured to create summary graphs for a > domain. > - this is implemented via a special syntax and then parsed by a > small > ruby script to get the configuration one wants to have. > currently only load.load is summed up, this can be extended. > > Please do test the module and tell me what works and what not. > I have the following problems: > - it seems that the list of hosts is not updated every time puppet runs > on the munin::host. The clients are all in the database, but the > munin::host does not ''see'' them. > - sometimes Puppet::Resource::param is empty, which means that the > database somehow got corrupted. I can not really reproduce this error, > it simpy happens from time to time. Until now, I have truncated the > tables... this is no real solution though. > > It would be cool to configure the type of summary graphs via the same > mechanisms that munin::plugin does. > Currently I only have the need for load.load graphs, thus it the current > solution is the most simple one. > > Another thing: the ''remotefile'' function does not seem to be ''module'' > aware. I have the strange hack to set ''module => false'' in those calls > of this function whcih come from a module... strange, ey? > Can someone think of a solution to get rid of this? i did not think very > much about it yet, might be the case that I figure it out myself. > > Hope you enjoy it, > udo. > > Thijs Oppermann wrote: > > On 28/05/07, *Udo Waechter* <udo.waechter@uni-osnabrueck.de > > <mailto:udo.waechter@uni-osnabrueck.de>> wrote: > > > > > > I am planning to make the module public, but where? I do not have a > > publicly available svn repository at hand, I have to think of > something > > else. > > > > > > > > You could start by attaching the files to a post to this list. A lot of > > us are interested in how others are creating their manifests for puppet. > > > > Gr, > > Thijs > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Puppet-users mailing list > > Puppet-users@madstop.com > > https://mail.madstop.com/mailman/listinfo/puppet-users > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users > > >_______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
Thijs Oppermann
2007-Jun-07 11:24 UTC
Re: munin module: manage clients and server''s config
And another: err: Could not find definition file_splice at /etc/puppet/modules/munin/manifests/init.pp I guess this is one of the caveats of using modules: we need to really make sure they are standalone, or otherwise very clearly know and describe what the dependencies are. Gr, Thijs On 07/06/07, Thijs Oppermann <thijso+puppet@gmail.com> wrote:> > Hey Udo, > > Nice. I''ve been looking at your module, trying it out. I get an error > however: > > err: Invalid parameter ''"module"'' for type ''remotefile'' at > /etc/puppet/modules/munin/manifests/init.pp > > Seems you have customised your remotefile definition? Care to share? ;) > > Gr, > Thijs > > On 06/06/07, Udo Waechter < udo.waechter@uni-osnabrueck.de> wrote: > > > > Dear all, > > finally I have found the time to complete the munin-module based on the > > code written by David Schmitt. > > I attach the current versionfor all of you to comment on it and please > > give me feedback. > > What I have implemented: > > > > - munin::client now automatically detects darwin and debian hosts. > > - darwin hosts are handled via snmp (could also be windows or > > any other snmp-device) > > - munin::host additionally is configured to create summary graphs for a > > domain. > > - this is implemented via a special syntax and then parsed by a > > small > > ruby script to get the configuration one wants to have. > > currently only load.load is summed up, this can be extended. > > > > Please do test the module and tell me what works and what not. > > I have the following problems: > > - it seems that the list of hosts is not updated every time puppet runs > > on the munin::host. The clients are all in the database, but the > > munin::host does not ''see'' them. > > - sometimes Puppet::Resource::param is empty, which means that the > > database somehow got corrupted. I can not really reproduce this error, > > it simpy happens from time to time. Until now, I have truncated the > > tables... this is no real solution though. > > > > It would be cool to configure the type of summary graphs via the same > > mechanisms that munin::plugin does. > > Currently I only have the need for load.load graphs, thus it the current > > solution is the most simple one. > > > > Another thing: the ''remotefile'' function does not seem to be ''module'' > > aware. I have the strange hack to set ''module => false'' in those calls > > of this function whcih come from a module... strange, ey? > > Can someone think of a solution to get rid of this? i did not think very > > > > much about it yet, might be the case that I figure it out myself. > > > > Hope you enjoy it, > > udo. > > > > Thijs Oppermann wrote: > > > On 28/05/07, *Udo Waechter* < udo.waechter@uni-osnabrueck.de > > > <mailto:udo.waechter@uni-osnabrueck.de>> wrote: > > > > > > > > > I am planning to make the module public, but where? I do not have > > a > > > publicly available svn repository at hand, I have to think of > > something > > > else. > > > > > > > > > > > > You could start by attaching the files to a post to this list. A lot > > of > > > us are interested in how others are creating their manifests for > > puppet. > > > > > > Gr, > > > Thijs > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > Puppet-users mailing list > > > Puppet-users@madstop.com > > > https://mail.madstop.com/mailman/listinfo/puppet-users > > > > > > _______________________________________________ > > Puppet-users mailing list > > Puppet-users@madstop.com > > https://mail.madstop.com/mailman/listinfo/puppet-users > > > > > > >_______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
David Schmitt
2007-Jun-18 08:24 UTC
Module Dependencies (was: Re: munin module: manage clients and server''s config)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 07 June 2007, Thijs Oppermann wrote:> And another: > > err: Could not find definition file_splice at > /etc/puppet/modules/munin/manifests/init.pp > > I guess this is one of the caveats of using modules: we need to really make > sure they are standalone, or otherwise very clearly know and describe what > the dependencies are.This probably means, that modules shouldn't use anything else than explicitly imported manifests. That way nothing from the "site manifest" can leak into the module. Then we can start collecting all the small comfort defines into a common module or semothing. Since I have now Internet access and time again, I'd volunteer to host and maintain the repo if there is interest. On the other hand, this is perhaps better served in the context of the puppet project? Luke? Regards, David PS: Great work, Udo! I'll take a more in-depth look at it tonight. - -- - - hallo... wie gehts heute? - - *hust* gut *rotz* *keuch* - - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGdkFO/Pp1N6Uzh0URAiBxAJ9NYVRvXfU89gPKbw+OOIg0TWyQOgCgoHe8 gdl4VkSirs+GEFw832RP5nU=JNR0 -----END PGP SIGNATURE----- _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
Luke Kanies
2007-Jun-18 15:45 UTC
Re: Module Dependencies (was: Re: munin module: manage clients and server''s config)
On Jun 18, 2007, at 3:24 AM, David Schmitt wrote:> > This probably means, that modules shouldn''t use anything else than > explicitly > imported manifests. That way nothing from the "site manifest" can > leak into > the module. > > Then we can start collecting all the small comfort defines into a > common > module or semothing. > > Since I have now Internet access and time again, I''d volunteer to > host and > maintain the repo if there is interest. On the other hand, this is > perhaps > better served in the context of the puppet project? Luke?I''ve already promised someone that I''d start hosting modules. My plan has been to use mercurial repositories, one per module, and for now, I''d just have them as plain html with no web site built around them, with the plan of eventually building a site around them so people could upload updates to their own modules. For now, I guess people would register modules, host them somewhere, then I''d write a script to sync them once a day or week or something. I can get this done this week, assuming I actually get fozzie (0.23.0) out the door (test -- please, test!). -- The great thing about television is that if something important happens anywhere in the world, day or night, you can always change the channel. -- From "Taxi" --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
David Lutterkort
2007-Jun-18 18:17 UTC
Re: Module Dependencies (was: Re: munin module: manage clients and server''s config)
On Mon, 2007-06-18 at 10:45 -0500, Luke Kanies wrote:> On Jun 18, 2007, at 3:24 AM, David Schmitt wrote: > > > > This probably means, that modules shouldn''t use anything else than > > explicitly > > imported manifests. That way nothing from the "site manifest" can > > leak into > > the module. > > > > Then we can start collecting all the small comfort defines into a > > common > > module or semothing. > > > > Since I have now Internet access and time again, I''d volunteer to > > host and > > maintain the repo if there is interest. On the other hand, this is > > perhaps > > better served in the context of the puppet project? Luke? > > I''ve already promised someone that I''d start hosting modules. My > plan has been to use mercurial repositories, one per module, and for > now, I''d just have them as plain html with no web site built around > them, with the plan of eventually building a site around them so > people could upload updates to their own modules.In terms of packaging, I''d like to add that as something like a puppet-stdlib package (at least for the modules that are clearly of general interest) - I am not sure though if this scheme would make sure that all the modules that get pulled are tested and known to work with the current puppet release. Would putting them into the puppet svn make that cleaner ? David
Luke Kanies
2007-Jun-20 22:23 UTC
Re: Module Dependencies (was: Re: munin module: manage clients and server''s config)
On Jun 18, 2007, at 1:17 PM, David Lutterkort wrote:> In terms of packaging, I''d like to add that as something like a > puppet-stdlib package (at least for the modules that are clearly of > general interest) - I am not sure though if this scheme would make > sure > that all the modules that get pulled are tested and known to work with > the current puppet release. Would putting them into the puppet svn > make > that cleaner ?Hmm. Well, it''d make it easier to know whether a given module works with the current release, but I''m not sure it''s the right solution. I expect it will make sense for packagers to have a stdlib in the main package or a separate one, but I''m not sure it makes sense to keep them in Puppet''s SVN repo. I want to make them less centralized, not more. -- Ours is the age that is proud of machines that think and suspicious of men who try to. -- H. Mumford Jones --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Hi, sorry I was occupied with other things for long. Thijs Oppermann wrote:> Nice. I''ve been looking at your module, trying it out. I get an error > however: > > err: Invalid parameter ''"module"'' for type ''remotefile'' at > /etc/puppet/modules/munin/manifests/init.pp > > Seems you have customised your remotefile definition? Care to share? ;)Yes I have customized it to this definition: define remotefile($owner = root, $server = "puppetmaster", $group = false, $mode, $source, $backup = false, $recurse = false, $checksum = md5, $module = "files") { $server_real = $hostname ? { default => $server } $real_group = $group ? { default => $operatingsystem ? { debian => "root", darwin => "staff", } } $module_real = $module ? { false => "", default => "$module/", } file { $name: mode => $mode, owner => $owner, group => $real_group, backup => $backup, source => "puppet://$server_real/$module_real$source", recurse => $recurse, checksum => $checksum, } } the "module => false" option is really a quick hack, and also terribly misnamed, since this parameter must be set to "false" in modules. It enables the remotefile to also look for modules'' file sources, though. Now that I think of it, I guess setting module => "" in modules should also do the trick. Bye, udo
You need the bracket editor from David Schmitt here: http://reductivelabs.com/trac/puppet/wiki/BracketEditor http://club.black.co.at/david/puppet/file_splice and the "define file_splice": http://mail.madstop.com/pipermail/puppet-users/2007-January/000926.html Have fun, udo. Thijs Oppermann wrote:> And another: > > err: Could not find definition file_splice at > /etc/puppet/modules/munin/manifests/init.pp > > I guess this is one of the caveats of using modules: we need to really > make sure they are standalone, or otherwise very clearly know and > describe what the dependencies are. > > Gr, > Thijs > > On 07/06/07, *Thijs Oppermann* <thijso+puppet@gmail.com > <mailto:thijso+puppet@gmail.com>> wrote: > > Hey Udo, > > Nice. I''ve been looking at your module, trying it out. I get an > error however: > > err: Invalid parameter ''"module"'' for type ''remotefile'' at > /etc/puppet/modules/munin/manifests/init.pp > > Seems you have customised your remotefile definition? Care to share? ;) > > Gr, > Thijs > > > On 06/06/07, *Udo Waechter* < udo.waechter@uni-osnabrueck.de > <mailto:udo.waechter@uni-osnabrueck.de>> wrote: > > Dear all, > finally I have found the time to complete the munin-module based > on the > code written by David Schmitt. > I attach the current versionfor all of you to comment on it and > please > give me feedback. > What I have implemented: > > - munin::client now automatically detects darwin and debian hosts. > - darwin hosts are handled via snmp (could also be > windows or > any other snmp-device) > - munin::host additionally is configured to create summary > graphs for a > domain. > - this is implemented via a special syntax and then > parsed by a small > ruby script to get the configuration one wants to have. > currently only load.load is summed up, this can be extended. > > Please do test the module and tell me what works and what not. > I have the following problems: > - it seems that the list of hosts is not updated every time > puppet runs > on the munin::host. The clients are all in the database, but the > munin::host does not ''see'' them. > - sometimes Puppet::Resource::param is empty, which means that the > database somehow got corrupted. I can not really reproduce this > error, > it simpy happens from time to time. Until now, I have truncated the > tables... this is no real solution though. > > It would be cool to configure the type of summary graphs via the > same > mechanisms that munin::plugin does. > Currently I only have the need for load.load graphs, thus it the > current > solution is the most simple one. > > Another thing: the ''remotefile'' function does not seem to be > ''module'' > aware. I have the strange hack to set ''module => false'' in those > calls > of this function whcih come from a module... strange, ey? > Can someone think of a solution to get rid of this? i did not > think very > much about it yet, might be the case that I figure it out myself. > > Hope you enjoy it, > udo. > > Thijs Oppermann wrote: > > On 28/05/07, *Udo Waechter* < udo.waechter@uni-osnabrueck.de > <mailto:udo.waechter@uni-osnabrueck.de> > > <mailto: udo.waechter@uni-osnabrueck.de > <mailto:udo.waechter@uni-osnabrueck.de>>> wrote: > > > > > > I am planning to make the module public, but where? I do > not have a > > publicly available svn repository at hand, I have to think > of something > > else. > > > > > > > > You could start by attaching the files to a post to this list. > A lot of > > us are interested in how others are creating their manifests > for puppet. > > > > Gr, > > Thijs > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Puppet-users mailing list > > Puppet-users@madstop.com <mailto:Puppet-users@madstop.com> > > https://mail.madstop.com/mailman/listinfo/puppet-users > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com <mailto:Puppet-users@madstop.com> > https://mail.madstop.com/mailman/listinfo/puppet-users > <https://mail.madstop.com/mailman/listinfo/puppet-users> > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users