>
> "For a given node, the pluginsync process will sync plugins, including
> custom facts, from the modules in the modulepath of the environment to
> which that node belongs."
>
So if my modulepath is /etc/puppet/modules - pluginsync will grab
everything from 'lib' folders under that (IE /etc/puppet/modules/.../lib )
regardless of whether it is referenced for a given client? Seems a tad
confusing as other elements from this path (other modules) aren't sent to a
given client without appearing in the node classifier for that client.
On Wednesday, September 24, 2014 6:34:13 AM UTC-7, jcbollinger wrote:
>
>
>
> On Tuesday, September 23, 2014 7:30:40 AM UTC-5, JonY wrote:
>>
>> I'm attempting to make the jump to directory-based environments and am
>> curious about what to do with custom facts.
>>
>> In my current config I've tried putting custom facts into a separate
>> module as /etc/puppet/modules/facts/{manifest,lib} and
>> /etc/puppet/modules/facts/lib/facter/<modules go here>. I haven't had any
>> success in getting these to propagate to clients though.
>>
>> I've added 'pluginsync=true' to puppet.conf on server/clients.
>>
>> Reading the various docs doesn't make it sound like I need a manifest for
>> custom facts. Truth? How about a class file?
>>
>
>
> Correct, you do not need a manifest for custom facts. Manifests are
> instructions for constructing parts of nodes' catalogs. They can use the
> values of custom facts, but they are not involved in installing custom fact
> implementations on clients. That's what pluginsync is for.
>
> I don't know what you mean by a "class file", as distinguished from a
> manifest.
>
>
>>
>> Questions:
>>
>> 1. What step(s) did I miss in getting my facts to be distributed?
>> 2. When I split up my network into 'production', 'test', etc folders for
>> use in environments - what happens to custom facts then?
>>
>
>
> Custom facts should be in modules. Typically they are in the same module
> as the classes that use them, but in principle, it should not be a problem
> for them to appear in their own, separate module. For a given node, the
> pluginsync process will sync plugins, including custom facts, from the
> modules in the modulepath of the environment to which that node belongs.
> Therefore, if your facts are not getting distributed then a modulepath
> issue is one of the things to consider.
>
> Also, running plain 'facter' on a client will compute and present only the
> standard facts. If you want also custom facts from Puppet then use 'facter
> -p'.
>
>
> John
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/163bf27d-edce-4fc8-97bb-660df2e4a4dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
