On Friday, May 11, 2012 10:00:36 AM UTC-7, Philip Brown wrote: > > I've just started experimenting with using some modules on our puppet > installation, and observing behaviour. > From these observations, it suddenly struck me, that the current module > implementation, violates what has previously been described as good puppet > design. > > It has previously been said, by multiple people in multiple places, > variants of, > "'Dont use puppet to distribute a lot of files; it's inefficient! use > rsync, or (that other file transport thingie)" > or, "Use packages!" > > Oddly, the new module architecture, and plugins, in general, seem to > violate both principles. > > These statements were generally made when people were trying to deploy web applications with hundreds of files quite often as part of their release process. For those purposes, using native packaging is a viable alternative. Puppet has also received significant performance improvements with recursive file serving that makes the process more tolerable now.
Plugins are a different animal. They are distributed to an agent and don't change again unless the custom fact, function or whatever is removed or modified on the Puppet master. Personally, I have different performance concerns for that type of process than when I want to deploy my web application to hundreds of clients several times a week/day. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-dev/-/lkDsd7SMwT8J. 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-dev?hl=en.
