Hi Everyone, First, thanks for all the great feedback!
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. Felix, yes my aim was to have everything complete in one Puppet run. My next-best option would be that Puppet would run again as soon as the slow-starting-service is ready - as opposed to waiting until the next scheduled run. Trevor, I'll take a look at Capistrano (that was mentioned at the recent Dublin Puppet Camp) but I have the same reservations as I would have with MCollective. Func isn't possible for us, due to arcane/licensing issues. Brian, thanks for your comments too. I will definitely model the service dependencies. 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. Cheers everyone! Dave On Tuesday, 10 July 2012 19:39:58 UTC+1, Dave Anderson wrote: > > Hi > > I have a resource that is slow to come into service and I have other > resources that are dependent on the service in order to be configured. I've > been searching for the "puppet way" to do this, but all the options I've > found don't seem optimal, so I'm assuming there is a better way that I'm > missing. > > I have several instances, so I want puppet to kick them off in parallel. > And I want the reliant services to be configured as soon as possible when > the slow services are ready > > So I don't really want to use long timeout/multiple retry because I > believe that won't be executed in parallel - and anyway, it's not a retry I > want, it's a wait > > I don't want to have Mcollective/AMQP just for this one problem, it feels > like a sledgehammer to crack a nut > > I don't want some external process to repeatedly kick puppet repeatedly > until the dependency is resolved and the reliant service can be configured > > I'm imagining something like a semaphore, puppet sleeps and wakes up when > the semaphore is flipped (the slow resource is available) > > Sorry if this is a dumb question, first post etc ... > > Thanks > > Dave > -- > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. > If you have received this email in error please notify the system manager. > This message contains confidential information and is intended only for > the > individual named. If you are not the named addressee you should not > disseminate, distribute or copy this e-mail. > > -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. -- 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/-/pSQNRuLUHgAJ. 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.
