On Apr 22, 2011, at 11:44 AM, Daniel Pittman wrote: > On Fri, Apr 22, 2011 at 10:18, Arm Adam <[email protected]> wrote: > >> Does puppet have any concept of a job engine with a request ID so that >> I can submit a request for a kick to happen, be given a request ID, >> and then be able to check back in for results for that specific >> request ID? Or is the only way of knowing when it is done to run kick >> in --foreground mode? > > No. Specifically, Puppet doesn't even come close to having a model of > that for the network. What we do have is MCollective, which is much > closer. I don't recall if it does asynchronous operations yet, but it > certainly allows the sort of remote control and verification on puppet > runs that you are after.
As Daniel says, mcollective is the only real way to do this kind of work right now, but it is still essentially syncronous in terms of control - you can't set up jobs and manage them discreetly, as far as I know. However, I've been thinking a lot about this recently, and I expect we'll be looking at whether it's reasonable to add something like it to the system at some point, so I'd love to hear about anything you come up with. -- The Internet, of course, is more than just a place to find pictures of people having sex with dogs. -- Time Magazine, 3 July 1995 --------------------------------------------------------------------- Luke Kanies -|- http://puppetlabs.com -|- http://about.me/lak -- 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.
