<br><div><br><div class="gmail_quote">On Thu, Nov 26, 2009 at 11:49 AM, micah anderson <span dir="ltr"><<a href="mailto:micah@riseup.net">micah@riseup.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi folks,<br>
<br>
There is a handful of useful goodies in the upstream ext/ directory. We<br>
are currently installing some of those bits, but not all of them.</blockquote><div><br></div><div>I've been really unsure what to do about these. Are they all being actively maintained upstream?</div><div><br></div><div>
I'm a bit worried about using the sql scripts, as I'm not sure whether they've been updated for the newer schema changes? </div><div><br></div><div>puppet-test is good, and extlookup is good. We should absolutely include those, same for the vim/emacs stuff.</div>
<div><br></div><div>I'm unsure why we'd use the puppetlist/puppetrun scripts? Wouldn't you just run puppetd in daemon mode and use the 'real' pupperun?</div><div><br></div><div>We should spark off a discussion about this on the upstream list, I have a feeling some of these have just been orphaned...</div>
<div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Right<br>
now we are installing:<br>
<br>
1. puppetlast in puppetmaster.install<br>
2. emacs/vim modes in debian/rules<br>
3. logcheck in debian/rules<br>
<br>
We have talked in the past about breaking out the emacs/vim pieces and<br>
submitting them to the packages that collect and distribute those. I<br>
think we should do that.<br>
<br>
However, there are various other things in there that are useful, and<br>
I'd like to outline them below and propose to install them in different<br>
ways. I'm planning on doing the ones that I propose below, however, I'm<br>
interested in feedback, suggestions or disagreements before proceeding:<br>
<br>
ext/bin/sleeper<br>
---------------<br>
comment from the top reads: # sleep indefinitely as a debug. I dont know<br>
what this is and unless someone figures it out, I would suggest we dont<br>
install it<br>
<br>
ext/dbfix.sql<br>
-------------<br>
this supposedly will clean up and fix Mysql stored config databases. i'd<br>
suggest adding this to the puppetmaster package. perhaps as an example<br>
file?<br>
<br>
ext/extlookup.rb<br>
----------------<br>
this is a useful external data sources function, I'd like to have this<br>
installed, would only be useful on the puppetmaster, I'd propose<br>
installing it in /var/lib/puppet/lib/puppet/parser/functions/<br>
<br>
ext/ldap/puppet.schema<br>
----------------------<br>
presumably this is a LDAP schema that some might find useful. perhaps<br>
install it in the puppetmaster package as an example?<br>
<br>
ext/module_puppet<br>
-----------------<br>
comment from the top of the file says: # Run a +puppet+ script as a<br>
cfengine module. I'm not sure where this would be useful, but perhaps<br>
in the puppet package as an example?<br>
<br>
ext/puppetlisten/puppetlisten.rb<br>
---------------------------------<br>
comment from the top of the file reads: # this is a daemon which accepts<br>
non standard (within puppet normal intervals) puppet configruation run<br>
request. my guess here is that this would go in puppet.examples<br>
<br>
ext/puppetlisten/puppetrun.rb<br>
-----------------------------<br>
comment from the top reads: # this scripts calls a client and ask him to<br>
trigger a puppetd run uses # SSL for communication based on the puppet<br>
infrastructure the client # allows access based on the namespaceauth. my<br>
guess with this one is that it belongs in puppetmaster.examples<br>
<br>
ext/puppetstoredconfigclean.rb<br>
------------------------------<br>
this script is useful to clean out, from the database, the stored<br>
configuration information for a particular node. you want to do this<br>
when a node has been decommissioned, if you dont then it will continue<br>
to show up on your munin/nagios/ssh or whatever stored configuration<br>
generated nodes<br>
<br>
ext/puppet-test<br>
---------------<br>
comment reads:<br>
# Test individual client performance. Can compile configurations, describe<br>
# files, or retrieve files.<br>
This appears to be a puppet.examples install.<br>
<br>
ext/rack<br>
--------<br>
this contains the pieces needed to run puppetmaster as a rack-based<br>
application. for example with passenger/mongrel etc. I propose to<br>
install this as a puppetmaster.examples set of files<br>
<br>
<br>
<br>
ps - I just uploaded a backport of the 0.25.1-2 package to <a href="http://backports.org" target="_blank">backports.org</a>, now<br>
that it has migrated to testing.<br>
--- End forwarded message ---<br>
<br>
_______________________________________________<br>
Pkg-puppet-devel mailing list<br>
<a href="mailto:Pkg-puppet-devel@lists.alioth.debian.org">Pkg-puppet-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/mailman/listinfo/pkg-puppet-devel" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/pkg-puppet-devel</a><br>
</blockquote></div><br></div>