> > I've considered this for about ten seconds, but how about supporting some > deployment tools in Puppet? So you could write a recipe that deploys > middleware, application and other infrastructure for example.
Personally, I'd rather figure out what doesn't fit into the model well than force a lot of external dependencies on other tools someone would need to grok. The idea that Puppet automation and 'deployment' are different shouldn't be the case, IMHO. That all being said, there's nothing stopping the creation of a Puppet type to run a deployment tool, I think that if you did that, you're doing the analog of an exec task, and that's not so interesting. I do agree though -- Puppet needs to have examples of how to construct manifests for middleware, applications, etc... though I don't think that's too hard to do today provided things lurk on a single server, and addressing the multi-server case is something we'll eventually want to conquer. I think there's a huge advantage of having all of your deployment + OS + config modelled in the same system. (Then again, I also believe in creating RPMs where possible so you can have package dependencies, but that's another story ... I know that doesn't fit into everyone's workflow so we have to make it easier to deploy things both ways. I think the VC type will go a pretty good way towards that.) --Michael -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
