[chef] RE: RE: Re: RE: ohai, number ldap accounts

[< >]

I'm glad to hear that as well. I would also like to know how to do the same 
thing...with bootstrap.

Ian D. Rossi
CD - Server Infrastructure
Phone 23834

________________________________________
From: Van Fossan,Randy 

 
Sent: Wednesday, March 28, 2012 12:52 PM
To: 

 
Cc: Zulauf, Graham; Kiner, Kari; 

 
Subject: [chef] RE: Re: RE: ohai, number ldap accounts

That is good news.   I need to incorporate that in the chef-client cookbook 
so that when the node is bootstrapped, it doesn't pull the data in after the 
first run.   Anyone, Know how I can incorporate the plugin disable when doing 
a bootstrap?   I do not want to delete the plugin as there may be reason to 
use it in the future or on a particular node.

I am not sure where to incorporate this...
Ohai::Config[:disabled_plugins] = [ "passwd" ]

Thanks all
  Randy

-----Original Message-----
From: Daniel DeLeo 
[mailto:
 
 On Behalf Of Daniel DeLeo
Sent: Wednesday, March 28, 2012 11:58 AM
To: 

 
Cc: 

 ;
 

 ;
 

 
Subject: [chef] Re: RE: ohai, number ldap accounts



On Wednesday, March 28, 2012 at 8:25 AM, 

 
 wrote:

> Hi Randy,
>
> We are experiencing this very same issue and were recently looking for a 
> solution. We use centrify to pull in AD accounts for authorization. The 
> nodes are pulling in tons of data for all of these user groups and accounts.
>
> If we're not doing anything with specific user accounts in 
> recipes/templates, should we be safe to just disable the Ohai plugin that 
> pulls in the user accounts from AD?
Chef doesn't use ohai data to lookup user/group data for 
file/template/directory or execute/script or user/group resources. It uses 
Ruby's `Etc` module, which in turn uses the `getpwent` family of functions.

So it's totally safe to remove the plugin if you don't need the data for 
other reasons.

--
Dan DeLeo