On 02/15/2013 01:11 AM, Brian Lalor wrote: >> Puppet isn't particularly good at code deployment. Ideally, you'd >> package your code, set a package resource to ensure => latest, then >> update your package repo with the new code. Then, all the resources >> that subscribe to that package (services, etc.) would be refreshed >> when the package gets updated in your repo. > > Why do you say "Puppet isn't particularly good at code deployment"? > What you described seems perfectly reasonable.
I'm inclined to second Joe's notion. Application deployment is usually a point-in-time thing. If you have the luxury to have your nodes deploy at times that are not clearly defined, you can resort to a puppet approach. If you *do* need orchestration, you probably apply an orchestration tool to the mix, and in this scenario, puppet is likely redundant. Cheers, Felix -- 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.
