I was asking about this months ago and was pointed to http://dev2ops.org/storage/downloads/FullyAutomatedProvisioning_Whitepaper.pdfas an example and explanation of why Puppet was not "good" for application deployment, better at being part of a stack of apps to achieve it.
Not that I understand it much :-P. But in general, I really didnt see why application deployment would be different for system deployment... except in operational terms. Things like "ok, new version of jar files on a load balanced enviroment, have to do one leg first, then the other, to ensure no outage...", that are very much procedural while Puppet manifest are more useful on a description of required software level. Cause you could do some weird thing like using a different class or parameter or something to update one leg first and then converging to the correct version, but at the default 30 minutes interval it would take you 1 hour to deploy, for example. ------------------------------ Jesús Couto F. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
