[chef] Re: RE: Moving from gem chef to omnibus

["Wolfe, Eric G" < >]

You can just copy over the couchdb file to the new server.  There is no 
reason to rekey all your clients just because you migrated your chef server.

Kevin Keane Subscription 
<
 >
 wrote:



I found a fairly (but not completely) painless migration path to a different 
server is this:



- Set up the new server

- On the chef workstation, modify your client.rb to reflect the new server. 
You'll also need to delete (or rename) your client.pem file and add the 
validation.pem from the new server.

- upload all your cookbooks, databags, roles etc. to the new server. Note: if 
you used knife to edit a databag or node attributes, you will run into 
trouble here.

- On each client, delete /etc/chef/client.pem, add /etc/chef/validation.pem, 
and modify the /etc/chef/client.rb to point to the new server. If running 
Chef as a daemon, you should probably also restart the daemon. You can use 
the knife bootstrap mechanism to execute this script, or simply use ssh.


You may also run into issues if you use environments, and quite possibly in 
other situations I didn't see in my testing.

-----Original message-----
From: Jens Skott 
<
 >
Sent: Wed 01-16-2013 11:04 pm
Subject: [chef] Moving from gem chef to omnibus
To: 

 ;
Im not sure if this has been brought up before, but since omnibus
seems to be the prefered way to install chef in the future, both
client and server I was thinking about moving from gem installation to
omnibus. My questions are now. Whats the easiest way to do the move? I
need all my old conf and data from my current chef server including
certificates for the clients and so fourth in the new installation
aswell.
Is there a good way to do it. Was reading the wiki and it only told my
how to install it. But not how to migrate data and how to move from
gem to omnibus.



Jens Skott
Tel: +46-8-5142 4396
Schibsted Centralen IT