[chef] Re: Re: RE: Re: Rollout the Chef client

[Kenneth Barry < >]

To summarize:

Getting the client is Easy on everything but Windows. Windows takes a little bit more effort. We don't use images, but do fresh installs via PXE, but have chef install happen as part of a GPO (Originally we had it as part of a first-boot script).

Generally I would suggest:

There are Cookbooks (The work is done for you) for Lots and lots of things already. Before you start writting chef recipes/cookbooks, see if there is a cookbook already.

Start small. Your doing things manually/some-other-way currently, take over the jobs one at a time. Keep converting processes (installs, configurations, etc.) into chef, with an emphasis on everything being Idempotent (Recipes can be run over and over and your machine will end up where it needs to be.)

On Mon, Dec 1, 2014 at 7:05 AM, Galen Emery < " target="_blank"> > wrote:

Chef can be used to update itself.

When rolling chef into existing infrastructure, the simplest way is to use knife bootstrap. This is easily script able.

For Unix systems, we make an ssh connection. For Windows, we need winrm open and we use winrm.

On Windows, if everything is talking to AD, you could use a group policy  to download and install the chef-client to each node. It's cleaner than knife bootstrap imo.

I'm sure others have more elaborate suggestions, but since this is a one time task, I try to not spend too much time automating the whole thing.

Lastly, the method you use to get chef onto your existing infrastructure may not be the same to get it onto new infrastructure. I bake chef-client into my images for future infrastructure.

Hope that helps!

-Mobile Galen

On Dec 1, 2014 1:31 AM, < " target="_blank"> > wrote:

 

We are planning to implement Chef in our estate. We have around 300+ hosts & VMs which include different versions of OS like Solaris/Linux/Windows/AIX machines

 

I just want to avoid a lot of manual work in rolling out Chef Client. Could you please suggest a good approach (creating script or any tool) for this?

 

What's required for the install on Solaris/Windows/AIX?

 

The mechanism we use - we might want to use it again in future to upgrade the clients- unless chef can do that itself, which I doubt.

 

Thanks

Devesh

 

 

From: Tyler [mailto: " target="_blank"> ]
Sent: 01 December 2014 11:33
To: " target="_blank">
Subject: [chef] Re: Rollout the Chef client

 

Thats a pretty open ended question.  https://www.getchef.com/download-chef-client/ has downloads for installing Chef.  If that doesn’t provide resources, can you provide more information about what prevents you from installing it through normal channels?

 

-T

 

On Nov 30, 2014, at 8:54 PM, " target="_blank"> wrote:

 

Hi All,

 

We are implementing Chef. I want to rollout Chef Client in all the exiting Linux, Solaris and Windows VMs.

 

Could you please suggest a good approach for this?

 

Thanks

Devesh

 

---

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. 
______________________________________________________________________________________

www.accenture.com

 

--

Kenneth Barry 

TuneIn | Build and Release Engineer

M: 409-673-0544

www.tunein.com