[chef] Re: Installing Chef-client on existing servers...

[Ranjib Dey < >]

sorry for the blank mail.

Yes you can grab the omnibus installer corresponding to your platform and use it locally. since omnibus bundle all its dependencies  (above glibc) , you can directly curl/wget it from a local http server also , instead of a full blown rpm/dpkg repo.

On Mon, Aug 20, 2012 at 9:50 PM, Ranjib Dey < " target="_blank"> > wrote:

On Mon, Aug 20, 2012 at 9:17 PM, Gavin Williams < " target="_blank"> > wrote:

Hi there,

I’m starting to evaluate how we’d go about rolling out chef-client to all of our existing servers with the minimum amount of hassle…

 

I started with ‘knife bootstrap x.x.co.uk -d chef-full’, however instantly failed with:

x.x.co.uk --15:09:28--  http://opscode.com/chef/install.sh

x.x.co.uk Resolving opscode.com...

x.x.co.uk failed: Temporary failure in name resolution.

 

My understanding of the process soo far is that the bootstrap process is attempting to download the install.sh script from opscode.com… However the majority of servers don’t have open internet access or DNS setup…

So looks like I’ve hit an instant brick wall… L

 

From my understanding of the process, the above install script computes a rpm filename (chef-full-${version}.${machine}.rpm) and URL (http://s3.amazonaws.com/opscode-full-stack/$platform-$platform_version-$machine/$filename) then downloads the file and rpm installs it…

Could I simply create a local yum repo with this RPM file present, and then create a custom bootstrap script which ssh’s into the relevant server, adds a host file entry for the yum repo server, creates the required yum repos.d file, and then installs the above rpm using yum?

Is that possible using bootstrap?

Any big gotcha’s with doing it that way? Other than having to maintain the versions in our local yum repo?

 

Thank-you in advance for any responses.

 

Regards

Gavin