On Dec 1, 2009, at 4:11 PM, James Turnbull wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Micah Anderson wrote: >> 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. > > Not sure why this is in there - Luke might know.
This used to be used for testing but can be removed now. >> 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 >> > > I think Brice wrote this one. I don't know if it was updated for > 0.25.x or if it needed to be. No idea here. >> 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? > > Think it would be useful 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? > > Not sure this would be overly useful for most people but with some > more documentation might be useful - not sure it still works though > either. AFAIK, no one has ever used this. I'd remove it and only add it back if someone actually complains about it. >> 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? > > There was a reason for this - Luke will know. > >> 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 > > Ditto. These are both actually Volcane's, right? >> 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. > > Agree and think that'd be useful. > >> 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. > > Yeah - needs some more documentation. I'm sure it does. Once we switch to one executable, this functionality will either be obsoleted or merged in, but for now it's useful to have somewhere. >> 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 > > I'd like to make this a bit more embedded into Puppet but I'm trying > to puzzle out how currently. Perhaps allow a command line flag to > create config.ru depending on versions. I've heard tell that people are a bit flummoxed by how hard it is to get our Passenger stuff work, so yeah, some kind of better integration would be good. -- The Chico, California, City Council enacted a ban on nuclear weapons, setting a $500 fine for anyone detonating one within city limits. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com -- 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.
