On Thu, Feb 18, 2010 at 9:12 AM, Trevor Vaughan <tvaug...@onyxpoint.com> wrote: > This is true and, unfortunately, I couldn't get to the presentation either.
I got to read a copy over the shoulder of someone here with a login. I thought it was pretty skimpy really, and didn't really adequately cover the advantages of either system. > > It's pretty well known that, given any two similar systems, the one > written in a lower level language will probably always win in terms of > speed and resource usage and lose in terms of community extensibility. > > It all comes down to what you're actually looking for in the tool. > > Trevor > > On Thu, Feb 18, 2010 at 12:06 PM, Nigel Kersten <nig...@google.com> wrote: >> On Thu, Feb 18, 2010 at 8:59 AM, R P Herrold <herr...@owlriver.com> wrote: >>> On Thu, 18 Feb 2010, Nigel Kersten wrote: >>> >>>> How, if at all, do any of you do capacity planning with Puppet? >>> >>> somewhat orthogonal to the question, but after reading this piece: >>> http://www.usenix.org/publications/login/2010-02/pdfs/bjorgeengen.pdf >>> at >>> http://www.usenix.org/publications/login/2010-02/index.html >>> >>> ... doing capacity planning for puppet presently may represent a 'premature >>> optimization' >> >> How is knowing how many clients your current infrastructure supports a >> premature optimization? >> >> Although that pdf is in 'teal', it doesn't actually appear to be >> available without a usenix login, which I don't have. >> >>> >>> The seeming speed and scaling differences between CFengine and puppet are >>> dramatic, and one has to ask if puppet is the right tool to bet on, in its >>> present form >> >> The default configurations of the two are radically different. >> >> There's nothing stopping you mimicking a CFengine style setup with >> puppet. Set up an rsync server, have your clients fetch the manifests >> and compile them locally. >> >> We've considered it several times for performance reasons, but I'd >> like to avoid exposing the raw manifests to my clients, even if you >> fake out environments by setting different rsync sources. >> >> >>> >>> -- Russ herrold >>> >>> -- >>> 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. >>> >>> >> >> >> >> -- >> nigel >> >> -- >> 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. >> >> > > > > -- > Trevor Vaughan > Vice President, Onyx Point, Inc > (410) 541-6699 > tvaug...@onyxpoint.com > > -- This account not approved for unencrypted proprietary information -- > > -- > 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. > > -- nigel -- 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.
