[Pkg-puppet-devel] Fwd: packaging the ext bits

[micah anderson]

Hi,

Excerpts from Nigel Kersten's message of Thu Nov 26 15:58:07 -0500 2009:
> On Thu, Nov 26, 2009 at 11:49 AM, micah anderson <micah at riseup.net> wrote:
>
> I've been really unsure what to do about these. Are they all being actively
> maintained upstream?

Good question. There are a couple, that I know about, that are being
maintained upstream, but then a couple I know nothing about. See my
additions below.

> 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?

Good question, I think this should be confirmed with upstream. I know it
works with 0.24.8, but I'm not sure about 0.25.1. I have had quite a bit
of problems migrating to 0.25.1 WRT to the stored configs, resulting in
me needing to kill a lot of nodes in the database, I've been wondering
if this dbfix script would have solved that or not. 

> puppet-test is good, and extlookup is good. We should absolutely include
> those, same for the vim/emacs stuff.

Agreed.

> 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?

These I dont know about. I think we should ask about them.

There are a couple others you did not touch on in your (*ahem*
top-posted) reply, which I do know somethings about and think we should
include:


> > ext/bin/sleeper
> > ---------------
> > comment from the top reads: # sleep indefinitely as a debug. I dont know
> > what this is and unless someone figures it out, I would suggest we dont
> > install it

We should ask about this one on the list. 

> > ext/dbfix.sql
> > -------------
> > this supposedly will clean up and fix Mysql stored config databases. i'd
> > suggest adding this to the puppetmaster package. perhaps as an example
> > file?

Agreed, we should check on the schema issue.

> > ext/extlookup.rb
> > ----------------
> > this is a useful external data sources function, I'd like to have this
> > installed, would only be useful on the puppetmaster, I'd propose
> > installing it in /var/lib/puppet/lib/puppet/parser/functions/

Agreed, we should install this

> > ext/ldap/puppet.schema
> > ----------------------
> > presumably this is a LDAP schema that some might find useful. perhaps
> > install it in the puppetmaster package as an example?

I am guessing that this would be useful for LDAP people, should we check
its freshness on the list before we include it?

> > 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, but perhaps
> > in the puppet package as an example?

Perhaps this is good for cfengine people, but I cannot tell how fresh it
is, suggest asking on the list.

> > 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 configruation run
> > request. my guess here is that this would go in puppet.examples
> >
> > 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. my
> > guess with this one is that it belongs in puppetmaster.examples

These two, I agree with you, I have no clue and we should ask.

> > 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

This is very useful, and I've been using it a lot for my migration to
0.25.1, I think we should include it.

> > ext/puppet-test
> > ---------------
> > comment reads:
> > # Test individual client performance.  Can compile configurations, describe
> > # files, or retrieve files.
> > This appears to be a puppet.examples install.

I dont really have an opinion on this one, but Nigel you think its good
so I'm happy to agree.

> > ext/rack
> > --------
> > this contains the pieces needed to run puppetmaster as a rack-based
> > application. for example with passenger/mongrel etc. I propose to
> > install this as a puppetmaster.examples set of files

This one is necessary for anyone who is using passenger, so I think we
should include it.

micah
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20091126/2471969f/attachment.pgp>