On Wed, May 12, 2010 at 10:07 AM, Dan Bode <[email protected]> wrote:

>
>
> On Wed, May 12, 2010 at 9:55 AM, Nigel Kersten <[email protected]> wrote:
>
>>
>>
>> On Wed, May 12, 2010 at 9:35 AM, Dan Bode <[email protected]> wrote:
>>
>>>
>>>
>>> On Wed, May 12, 2010 at 9:25 AM, Alan Barrett <[email protected]> wrote:
>>>
>>>> On Thu, 13 May 2010, Ohad Levy wrote:
>>>> > > And the absolute killer: as far as I know, external node classifiers
>>>> > > are global, not per environment.  It doesn't even get to know which
>>>> > > environment the node requested, so it is *impossible* for it to give
>>>> > > back the correct information to Puppet.
>>>> > >
>>>> > thats not correct (at least in the case of http://theforeman.org).
>>>>
>>>> Really?  Did feature #2834 get implemented while I wasn't paying
>>>> attention?
>>>>
>>>> there is a workaround for it (although your feature is valid and should
>>> be implemented) . The external classifier can access client facts from the
>>> $vardir/yaml/facts. Ohad said it's possible, not that its pretty ;)
>>>
>>
>> Assuming the client has puppeted at least once against that server. This
>> won't work for bootstrapping a client though will it?
>>
>
> it does, the facts yaml file is created before the external node classifier
> is called ;)
>

Whoa. This should be called out in the external node docs, as I simply
assumed this happened after the node classifier is called.




>
>
>>
>> I'd love it if facts were available to the external node classifier. I'm
>> thinking of a flow like:
>>
>> * new client runs puppet, has no facts
>> * external node classifier supplies a bootstrap environment with bootstrap
>> facts
>> * client submits evaluated facts to external node classifier again, it can
>> now make decisions with full data about the client.
>>
>>
>>
>>
>>>
>>>
>>>
>>>> --apb (Alan Barrett)
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Puppet Users" group.
>>>> To post to this group, send email to [email protected].
>>>> To unsubscribe from this group, send email to
>>>> [email protected]<puppet-users%[email protected]>
>>>> .
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/puppet-users?hl=en.
>>>>
>>>>
>>>  --
>>> You received this message because you are subscribed to the Google Groups
>>> "Puppet Users" group.
>>> To post to this group, send email to [email protected].
>>> To unsubscribe from this group, send email to
>>> [email protected]<puppet-users%[email protected]>
>>> .
>>> For more options, visit this group at
>>> http://groups.google.com/group/puppet-users?hl=en.
>>>
>>
>>
>>
>> --
>> nigel
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected]<puppet-users%[email protected]>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<puppet-users%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>



-- 
nigel

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

Reply via email to