On Fri, Sep 14, 2012 at 2:40 PM, Eric Sorenson <[email protected]> wrote: > > There are a lot of issues with `puppet kick`, because it requires an open TCP > port listening on every agent, special auth.conf setup, and some form of node > discovery/inventory. While I can definitely understand that people find kick > useful, we really think that mcollective is the right way forward because it > addresses all 3 of these issues and gives you a ton of extra functionality > that kick simply can't do. > > Note that in 3.0 we are just going to start emitting a warning message; the > code is still there and will continue to work through the 3.x series. I > really think that by the time the "hard" deprecation comes in 4.0, > mcollective will be super easy to get running even for small sites and give a > way better user experience than kick ever did.
I would also add that, in a small site, `ssh node.example.com puppet --test` is generally also a reasonable way to run Puppet immediately and get feedback on progress without having to wait. At large scale that gets hard to manage, but at small scale it is a pretty respectable way to get remote execution in place. -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
