On 07/27/2012 07:08 PM, Nick Fagerlund wrote:
On Friday, July 27, 2012 9:41:28 AM UTC-7, Stephen J. wrote:
For lots of nodes, MCollective is definitely the way to go. For
smaller environments where you need one-off server initiated puppet
runs, there's also 'puppet kick'
http://docs.puppetlabs.com/man/kick.html
<http://docs.puppetlabs.com/man/kick.html>
Note that getting puppet kick working is a multi-step process:
- Gotta change all agents' puppet.conf to have listen = true in either
[main] or [agent].
- Gotta open port 8139 to incoming connections on every agent node's
firewall.
- Gotta add the following stanza somewhere near the top of each agent
node's auth.conf file:
path /run
auth yes
allow puppet.example.com
(trading puppet.example.com for your puppet master's certname.)
Given that, you might find MCollective not that much more work.
You can push configuration through puppet itself, so it's not a big deal.
Although main issue is if you are using or planning to use mcollective
or not. If not, then kick is the only option to "push", and if yes then
mcollective with puppetd plugin.
I use the latter and it works superbly! For example I disable all the
puppet agents and enable them only when I change the manifests. One can
use shell script and help itself with the sleep(1) or disperse load
through mcollective. That way load on puppetmaster is eliminated.
--
Jakov Sosic
www.srce.unizg.hr
--
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.
