- From: Daniel DeLeo <
>
- To:
- Subject: [chef] Re: Re: Re: Re: Add Client to Chef Server Immediately?
- Date: Tue, 12 Aug 2014 15:54:56 -0700
On Tuesday, August 12, 2014 at 3:38 PM, Douglas Garstang wrote:
>
Daniel,
>
>
Caveats aside, where would the node.save go? Would it go in the recipe
>
somewhere very early in the run list? I think the hack I saw had this run
>
on the client side with chef-client.
>
>
Doug.
Yeah, you can put it in a recipe, probably at the top-level (i.e., not in a
ruby_block resource) so it’ll run during the compile phase. If you’re using a
Chef Server with the older Solr (most likely if you’re not on Hosted
Enterprise Chef) then the next commit should happen within 60 seconds
(assuming you haven’t changed the default tuning). So you have to either
sleep 60 or poll search until the node can find itself. If you opt for
polling, make sure you have sufficient wait time in between checks or else
you can kill the server performance in some situations (e.g., you bring up a
new test environment with a bunch of brand new nodes and they’re all
hammering the server).
--
Daniel DeLeo
Archive powered by MHonArc 2.6.16.