[chef] Re: Re: Re: set run list on Server or node.

[Mike < >]

The distinction is that when a new node starts up, Chef Server has no idea of what the node is, nor its run_list.

As Dan stated, with bootstrap, a json file is placed on the node, and chef-client references that file, runs Chef, and at the end of the (completed) run, sends the details back to Chef Server (including the run_list) for future use.

Using knife to set the run_list on existing nodes will affect their future runs, as when chef-client starts, it asks Chef Server for its current run_list.

-M

On Thu, Sep 5, 2013 at 12:54 AM, Howard Zhang < " target="_blank"> > wrote:

What I know is that the two command, "knife bootstrap -r xxx" and "knife node run_list set" is different. The first one is the bootstraped node tell Chef server his run list, while the other is that knife tell Chef Server to assign run list to certain node.

Howard

On Wed, Sep 4, 2013 at 11:38 PM, Daniel DeLeo < " target="_blank"> > wrote:

On Tuesday, September 3, 2013 at 8:37 PM, Howard Zhang wrote:

Hi,

I wonder when I use knife to set a Node's run list, knife build connection with server or node to set its run list? Is "bootstrap -r" make use of the same mechanism with "knife node run_list"?

No, when you bootstrap, it creates a JSON file on the remote box and passes `-j /etc/chef/first-boot.json` option to chef-client.

 

Thanks.

Cheers,

Howard Zhang

-- 

Daniel DeLeo