+puppet-users, puppet-dev to catch the developer-y folks too.
How, if at all, do any of you do capacity planning with Puppet? I've worked out a snippet of ruby code that will take the cached fact data from the servers, and use that to issue a bunch of catalog retrieval requests. I ended up modifying my auth.conf (such an awesomely flexible setup) to allow a given certificate to request anyone's catalogs, which made this all a lot easier. I'm now looking at jmeter to issue the https with client certificate GET requests, and before I dive too deeply into scripting jmeter, I thought I'd see what anyone else is doing in this space. It would be awesome if we could put something into the source distribution to do this in a standard manner so we can all compare performance on different platforms and ruby stacks. This is all a lot easier with the RESTful API than it was with XMLRPC by the way. There was the puppet-test script in ext/, but as per http://projects.reductivelabs.com/issues/3183 it doesn't appear to have been updated for 0.25.x clients. Anyone else interested in collaborating on something to provide uniform server benchmarking with pretty graphs for management? -- 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.
