On 07/10/2012 08:52 PM, Christopher Wood wrote: > I don't understand your issue with mcollective. You have an orchestration > issue but don't want to use the puppet-ecosystem orchestration tool? This is > the part that confuses me, especially since this won't be your last > orchestration requirement.
I agree with the OP that there is quite some overhead involved and there should be a good reason for implementing the requried infrastructure. What's not clear to me is: Should all this happen during the same agent run? I disbelieve puppet can handle this. Puppet really only cares about this: Is service A running? If not, start it. If starting is implemented synchronously, i.e. the start operation does not finish before the service is ready, puppet will wait for it to get ready. Nothing works in parallel in this scenario. On the other hand, if the start operation finishes immediately, puppet will consider the start to be complete and apply all depending resources. So if you wish your start procedures to work asynchronously, you will probably have to design your depending services accordingly, i.e. when you start services B and C, their initscritps (or whatever) need to linger in the background and wait for service A to be completely initialized before actually performing their true startup operations. HTH, Felix -- 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.
