Puppet » Puppet Dashboard

Argh. I don’t see this behaviour at all. I’m going to have to take a deeper look.

As an aside, would it be useful to release a plugin for the puppet_dashboard.rb report processor to make installation easier for those still running Puppet 0.25.x?

Rein Henrichs wrote:

As an aside, would it be useful to release a plugin for the puppet_dashboard.rb report processor to make installation easier for those still running Puppet 0.25.x?

personall, I have no opinion on this. I wasn’t using puppet-dashboard yet. I just saw the new release and thought I would give it a whirl and make my life a tad bit easier.

I think a module makes sense for ease of installation, since I think this pluginsync conflict is essentially endemic – purging is enabled when pluginsync is running, so it will always purge this kind of thing.

$libdir should actually support more than one path, like most of these apps do (e.g., $PATH), but it doesn’t for some reason, so the only reasonable solution is to put it into a module or a separate Ruby search path which you add separately, unfortunately.

Hmm. I think you are correct.

That is, yes – if pluginsync is enabled on the server, then pluginsync owns the destination $libdir, and it will purge anything it doesn’t get.

Additionally, if it’s in a place where pluginsync will find it, then all clients will get it.

The only other option I can think of in the short term is to install it in Ruby’s load path, rather than Puppet’s. In the long term, the right option, I think, is to support the libdir being multiple directories, so you could just add the Dashboard’s libdir to Puppet’s, or something similar.

FWIW, my current hack around this problem (on 0.25.5) is as follows:

[main]
    vardir = /var/lib/puppet
[puppetd]
    pluginsync = true
    libdir = $vardir/lib
[puppetmasterd]
    libdir = $vardir/masterlib
    reports = puppet_dashboard

And I install $vardir/masterlib/puppet/reports/puppet_dashboard.rb via some method besides pluginsync (manual, local RPM, File resource).

two comments on the README notes:

• the fix is only suggested for puppet 0.25.x, it is also required for 2.6.x

• the fix says only to use if ‘puppetd —configprint pluginsync’ is true. I would recommend it for all cases. With the current recommendation, if the pluginsync is enabled, then the file could be destroyed.

This was merged into master in commit:308dcbbfc892ccbaf13b3be4d997c6cdcb6b44af as part of Iteration-2010-11-10, but I’m assigning it to Dan for clarification about his concerns.

an update for this ticket (although I still need to check the patch)

As far as I am concerned, this is fixed in 2.6.x with the http report handler.