> How can MCollective replace "puppet kick"?
http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/AgentPuppetd
MCollective is a service that runs on every node. It constantly polls a message queue server for real-time messages and sometimes responds to them by performing actions.You use a command-line client app to send messages, and you can set filters on each message so only certain nodes or groups of nodes will respond to them. Every node that matches a message will react simultaneously when the message goes out.Each node has a set of actions it can run, provided by plugins. The "puppetd" plugin lets you control puppet agent, but it's better than puppet kick: It can trigger runs even if puppet agent usually runs via cron instead of as a service, it can enable and disable puppet runs, and it can fetch last run summaries. MCollective also lets you be smarter about triggering runs because it doesn't limit you to hostnames; you can filter by puppet class, facts, etc.Does that help?
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/VK67c2UfgG4J.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
The mcollective agent is written in Ruby, but it's really tiny. You can use the mco controller plugin to view resource utilization over time, and it's generally infinitesimal.
http://projects.puppetlabs.com/projects/mcollective gives a bit more information on mcollective itself. You don't actually push configs to nodes with it; you have a client which "tells" all machines that matches a fact to trigger a puppet run. The puppetd agent plugin is required for this to work.