In regard to: [Puppet Users] Re: The Puppet Way to handle slow resources?...:
Chris, I'll take a look at exported resources. I don't have a problem with MCollective per se, I just don't want to add a bunch of other software if there's a "native puppet" way to solve the problem. From what I've seen, Puppet itself isn't supposed to solve this problem, MCollective is.
Agreed.
My "plan A" right now is that when the slow-running service is up and running it will tell Puppet to run. I haven't really thought about how this would work for multiple instances of the slow-service, I'm pretty sure that's not a hard problem to solve though.
I've only partially followed this thread so I don't know if someone else has already suggested this, but if the real issue is that the interaction between software, init script, and puppet isn't working correctly, then why not have puppet manage and use a "wrapper" init script? You keep the init script that came with the software, but instead of having puppet use that for start/stop/status, you write your own "local-service" or "mycompany-service" init script and have that script call the original script and augment the logic in start/stop/status/whatever to do whatever is needed to work correctly with puppet. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 -- 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.
