[chef] Re: Re: Chef best practice for multiple developers

[Ritesh Angural < >]

Great question & thanks for the informed reply Brad.

I've been pondering about this myself. My team is in the initial stages of our Chef implenetation. We're currently a team of 15 developers.We have staging & production environments for all our applications that directly map to develop & master branches in their respective git repositories. We also use Jenkins for integration & deployment across our services so a push to develop or master triggers a deployment to our staging or production servers.

My question is how do we do a similar setup for Chef? Does it make sense to have two different chef servers per environment? My initial guess would be no because chef itself is used to manage the different environments.

But, on the other hand it would be ideal to have git branches as the single point of truth such that everything on master branch in the chef-repo is the exact replica of what's on the chef-server.

How are you guys doing it currently?

Ritesh  

On Fri, Dec 27, 2013 at 10:57 PM, Ameya Varade < " target="_blank"> > wrote:

I would say go with git. You can also have Gerrit as a gatekeeper for git. This will provide review workflow. Or simplest way is using github for managing repos. 

On Friday, December 27, 2013, Keckler, Ray wrote:

Okay so I installed a Chef server, A chef workstation and a chef node.

 

I am able to create  cookbook with a recipe and upload the results from the workstation to the server.  The server can then update the node.

 

Everything is good.

 

Only one question

 

How do multiple developers make, update and recipes? 

I know about cvs, git and all that but what it the best practice with Chef?

 

 

 

Ray Keckler

Unix Administator | Acclaris, Inc. | c 813.9515160
Transforming consumer-driven healthcare and reimbursement offerings.

 

PRIVACY/CONFIDENTIALITY NOTICE: This e-mail communication may contain private, confidential, or legally privileged information intended for the sole use of the designated and/or duly authorized recipient(s). If you are not the intended recipient or have received this communication in error, please notify the sender immediately by email to mailto: "> or by telephone at 1-813-873-2020, and delete all copies of this e-mail, including all attachments, without reading them or saving them to your computer or any attached storage device. If you are the intended recipient, you will need to secure the contents conforming to all applicable state and/or federal requirements related to the privacy and confidentiality of such information, including the HIPAA Privacy guidelines.