[Puppet Users] Re: Pluginsync in 0.25

Luke Kanies
2009-05-12T20:48:07Z

On May 12, 2009, at 5:35 AM, DerekW wrote:

>
> I''ve been testing 0.25beta1.  I understand that the default
pluginsync
> mount is now a special PluginMount, presumably to do with the fact
> that plugins are now modular.

There was actually a special PluginMount class before; it was just in
the same file as the main Mount class (as was all of the fileserving
code, actually).

>
> However, I haven''t quite gotten around to refactoring my Manifest,
and
> moreover a lot of our custom types and functions are actually shared
> amongst modules anyway.
>
> Is the new model to assign my custom types to an arbitrary module (say
> the one where it''s used most) and rely on that?

The behaviour shouldn''t have changed at all; only the internals.  Any
changes in function are bugs (so we appreciate the testing).

>
> I can''t get this to work with non-modular plugins (see ticket
#2244).
> At the moment I just created a fileserver export called
"oldplugins"
> and set my client
> pluginsource = puppet:///oldplugins/
>
> That doesn''t appear to be loading my types so the run fails but
I''ve
> raised ticket #2245for that.

I''ve got both of those in my queue and I hope to get to them this week.

>
> I''m also seeing my /var/lib/puppet/plugins dir completely cleaned
out
> on the Puppetmaster (!) and I''m trying to track that down too.  I
do
> wonder if puppetmasted is trying to create a combined directory from
> each of my modules for fileserving purposes?


If your pluginsource and plugindest are the same directory, I would
consider behaviour to be somewhat undefined.  I mean, it *should*
work, but...

--
Always behave like a duck - keep calm and unruffled on the surface but
paddle like the devil underneath. -- Jacob Braude
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com