Hi all, There is a handful of useful goodies in the upstream ext/ directory. Over here in Debian-land, we are currently installing some of those bits, in certain ways, but not all of them. The ones we aren't installing are because we aren't completely clear on what the deal is with them. Right now we are installing:
1. puppetlast is getting installed in /usr/bin when you install the puppetmaster package 2. emacs/vim modes are being installed in the puppetmaster package (although we are looking at breaking these out into more general debian emacsen/vim mode packages) 3. the logcheck rules for both packages However, there are various other things in ext/ which seem useful and we'd like to also ship in the Debian packages, but we need some clarity on them. Perhaps a README in the ext directory which provided more clear overview of what they are, and some usage examples? Are these being actively maintained and current, or are some of these orphaned? ext/bin/sleeper --------------- comment from the top reads: # sleep indefinitely as a debug. I don't have any idea what this is, what it would be useful for, in what scenarios, etc. ext/dbfix.sql ------------- I've heard through the grapevine that this supposedly will clean up and fix MYSQL stored config databases. was this updated for the new schema changes? What exactly does it do, and in what scenarios would someone need/want to run this? If it is updated and generally useful, we might put it in our /usr/share/doc/puppetmaster/examples directory ext/extlookup.rb ---------------- I've seen this discussed in a few places, and it looks to be a very useful external data sources function, I would like to start using it personally, and I'd love it if the packages installed it in the appropriate location so that it could be used. It seems like the right location would be on the puppetmaster in /var/lib/puppet/lib/puppet/parser/functions -- however, an *even better* solution would be if this was incorporated into puppet itself as part of the normal installation. Any chance I can talk people into that? ext/ldap/puppet.schema ---------------------- presumably this is a LDAP schema that some might find useful, although I'm not sure the details on this. perhaps it would be useful the puppetmaster package in the examples directory? ext/module_puppet ----------------- comment from the top of the file says: # Run a +puppet+ script as a cfengine module. I'm not sure where this would be useful, is this a cfengine thing that allows you to run puppet stuff? would this be something useful to include in a puppet/puppetmaster package in an example directory? ext/puppetlisten/puppetlisten.rb --------------------------------- comment from the top of the file reads: # this is a daemon which accepts non standard (within puppet normal intervals) puppet configuration run request. I'm unsure why one would use the puppetlist/puppetrun scripts? Wouldn't you just run puppetd in daemon mode and use the 'real' pupperun? ext/puppetlisten/puppetrun.rb ----------------------------- comment from the top reads: # this scripts calls a client and ask him to trigger a puppetd run uses # SSL for communication based on the puppet infrastructure the client # allows access based on the namespaceauth. same question as the previous one above in the puppetlisten.rb section ext/puppetstoredconfigclean.rb ------------------------------ this script is useful to clean out, from the database, the stored configuration information for a particular node. you want to do this when a node has been decommissioned, if you dont then it will continue to show up on your munin/nagios/ssh or whatever stored configuration generated nodes, i use it and would like to have it available on puppetmaster installs. ext/puppet-test --------------- comment reads: # Test individual client performance. Can compile configurations, describe files, or retrieve files. This appears to be a useful benchmark script that probably would make sense to be installed when you install the puppet package (or puppetmaster?) as an example file. ext/rack -------- this seems to contains the pieces needed to run puppetmaster as a rack-based application. for example with passenger/mongrel etc. If i'm right, I would propose to install this as a puppetmaster.examples set of files thanks for any insights into these, hopefully sorting them out will lead to a better set of packages that are more functionally useful in general. micah -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
