[Puppet Users] Re: New Puppet report processors...
These will be most useful!! Thank you. How can I test that these are functioning? I have setup the XMPP as well as modified that to send emails. However when I purposely cause a puppet run to fail I do not receive either email or jabber message. Thanks - Trey On May 31, 10:09 am, James Turnbull ja...@puppetlabs.com wrote: Hi all On my TODO list for about a year now has been a tutorial on how easy it is to write Puppet report processors and how much more you can do with them than just email/log/store Puppet report data. Rather than write a whole tutorial I decided to create a whole series of examples of report processors that should: a) Provide some immediate solutions that you can deploy right now, and b) Provide good examples of things you can do with report processing that you can take, fork and modify. All of them are released under the Apache 2.0 license. In that spirit I've created ten new report processors: 1. Reports failed runs to an IRC channel -https://github.com/jamtur01/puppet-irc 2. Reports failed runs and logs to PagerDuty -https://github.com/jamtur01/puppet-pagerduty 3. Reports failed runs to Jabber/XMPP -https://github.com/jamtur01/puppet-xmpp 4. Reports failed runs to Twitter -https://github.com/jamtur01/puppet-twitter 5. Reports failed runs and logs to Campfire -https://github.com/jamtur01/puppet-campfire 6. Reports failed runs to Twilio -https://github.com/jamtur01/puppet-twilio 7. Reports failed runs to Boxcar -https://github.com/jamtur01/puppet-boxcar 8. Reports failed runs to HipChat -https://github.com/jamtur01/puppet-hipchat 9. Sends metrics to a Ganglia server via gmetric -https://github.com/jamtur01/puppet-ganglia 10. Reports failed runs to Growl -https://github.com/jamtur01/puppet-growl Comments, feedback, testing and ideas for other integrations all welcomed. Regards James -- James Turnbull Puppet Labs 1-503-734-8571 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Client vs server storeconfigs
On Fri, Jun 3, 2011 at 10:12 PM, Sirtaj Singh Kang sirtaj.k...@gmail.comwrote: Thanks for the reply Ohad, On 04-Jun-11, at 9:43 AM, Ohad Levy wrote: [snip] the database exists only on the server side Okay. I am seeing /var/lib/puppet/state/clientconfigs.sqlite3 even on machines running only the agent. I have [main] ... storeconfigs = true thin_storeconfigs = true dbadapter = sqlite3 on all machines, with the master overriding with dbadapter = postgresql. You only need to set it in [master]. Being in [main] will apply to [agent] and [master] and even [apply]. It is possible to use storeconfigs with purely standalone puppet, but the standard deployment is just on the master. Is the clientconfigs.sqlite3 file related to storeconfigs? If so, is it simply being created and ignored by the agent? Apologies if I'm asking silly questions, I'd appreciate a pointer to an RTFM, it's possible I have missed something. -Taj. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Nigel Kersten Product, Puppet Labs @nigelkersten -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Weird paramterized issue
Im using a parameterized class in my site.pp:
class development($user) {
class{basenode: user = $user}
class{nodejs: user = $user}
include coffeescript
include ruby
}
This class defines nodejs class that epects a user as input:
class nodejs($user) {
class {nodejs::npm: user = $user}
$node_ver = v0.4.7
$node_tar = node-$node_ver.tar.gz
# ...
}
The first time I run this all works fine, still on the second run Im
getting:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Must pass user to Class[Nodejs] at
/etc/puppet/modules/nodejs/manifests/init.pp:1 on node
When I touch the site.pp file or restart puppet master all things work
again, any idea what Im doing wrong?
Thanks
Ronen
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
