[chef] Re: Re: Re: How to get Chef Server to add itself as a node?

[Nico Kadel-Garcia < >]

You left out "make sure DNS and/or /etc/hosts make a working 'hostname --fqdn' setup before running chef-server or chef-client".

A lot of people leave this out of their setup notes, but it saves a lot of trouble.

Nico Kadel-Garcia

Email: n ">

Sent from iPhone

On Jun 11, 2015, at 8:01, "Greg Barker" < "> > wrote:

Last time I used the aws cli to spin up an EC2 instance that will become my chef server.

Then I ran a simple little fabric script that does the following:

* Copies encrypted_data_bag_secret, bitbucket deploy key, and known_hosts file to the instance

* yum install git

* Clone down my chef repo from bitbucket

* Runs berks package on my cookbooks, copies it to the instance, and untar it (I think `berks package` is run locally, maybe it should be run on the server?)

* Creates a solo.rb file

* Run chef-solo with run list role[mycorp_chef_server], from there it's mainly just the chef-server cookbook

I haven't looked at this script in awhile, maybe there's a better way to go about this?

On Wed, Jun 10, 2015 at 1:39 PM, Ranjib Dey < " target="_blank"> > wrote:

how you provision chef server?

On Wed, Jun 10, 2015 at 12:36 PM, Greg Barker < " target="_blank"> > wrote:

How do I get my Chef Server to add itself as a node during provisioning?