On Monday, February 18, 2013 2:13:26 AM UTC-6, Gavin Williams wrote: > > No-one doing anything similar? > > Puppet is all about managing nodes to a known-in-advance state. You can encapsulate stateful logic inside 'providers' for custom or built-in resource types. You also might be able to model steps or groups of steps as a separate classes, provided that no node state set by one such class subsequently needs to be modified by another.
Alternatively, you might need or want to use multiple Puppet runs to step through this process. Indeed, that may be necessary if you need the same resource (as Puppet sees it) to be managed to two or more different states during the course of the process. I don't have any knowledge of the specific software stack you are configuring, so I'm afraid I can't offer detailed suggestions. One way or another, Puppet can probably be made to perform this process for you, but that doesn't necessarily mean it's the best tool for the job. One alternative might be to script multiple puppet runs in series, each selecting different classes to apply via tags. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
