[chef] Re: Re: managing chef server/webui/couchdb with chef?

[Jim Hopp < >]

Right, we do use chef-solo for the initial install of chef server. I'm wondering how people manage on-going updates to the chef server components. But I guess we won't be changing the chef server components very often; most of the changes to the machine will be the standard machine config stuff. Thanks for the affirmation that we can just use chef-client for that.

-Jim

On 10/10/2010 12:35 PM, "> wrote:

" type="cite">

Knife has a bootstrap option to setup a box as a chef client which you can use chef solo to then run the bootstrap cookbook for server components.

There's no magic with chef server and client living on the same machine except that the validation key is already on the machine so it saves you a step

On Oct 10, 2010 11:49 AM, "Jim Hopp" < "> > wrote:
> Hi folks-
>
> We're curious about how people are managing the chef server components
> (Chef Server API/webui, CouchDB, Solr Indexer, rabbitMQ, etc) and the
> machine all this is running on.
>
> First, the machine: it seems feasible to assign a role to the node
> running the server, and to use that role to manage the prosaic stuff:
> packages, iptables, ntp, accounts, etc; all the stuff we're managing on
> the all the other nodes. Are there any gotcha's to just running
> chef-client on the chef server node?
>
> Second, the chef server components: this seems much more complicated. Do
> people try to manage updates to the chef server components with chef
> itself, or do you simply use chef-solo to do the initial install and
> then manage updates by hand?
>
> -Jim