Re: [Puppet Users] Definitions in External Nodes

Nigel Kersten
Tue, 31 Aug 2010 00:50:47 -0000

On Mon, Aug 30, 2010 at 5:35 PM, Alan Sparks <asparks@doublesparks.net>
wrote:
>  On 8/30/2010 9:44 AM, Nigel Kersten wrote:
>> This is much clearer now.
>>
>> Can you not solve this problem with extlookup now rather than having
>> to write custom functions?  Either key the relevant data off a base
>> variable, or set the key to lookup info for in the external node
>> provider?
>>
>> I like this approach because it keeps the data and the model nicely
>> separated, rather than whacking data into the external node provider.
>>
>
> If the extlookup() function supported other than just CSV files now, it
> would be more attractive.  My instance, most of this information has to
> be derived in the external node classifier, this would entail some sort
> of periodic extraction to generate the extra data source.  Besides,
> isn''t the node classifier intended to provide the driving data
(e.g.,
> parameters) for the models?  As well as calling out the nodes classes?

I''m not disagreeing with you. It could be better, just pointing out an
option.

I have custom functions for pulling data out of yaml files, and
strongly prefer to keep that data separate to the actual code in my
node classifier, so it doesn''t really matter to me whether the data is
directly interrogated by the node classifier, or pulled out by
functions inside manifests based upon a key that the node classifier
sets.



> -Alan
>
>
> --
> You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>
>



--
nigel