On Thursday, April 12, 2012 at 12:44, wrote:
Hi,I wanted to get folks opinions on what is better to use for localinfrastructure development chef-solo or chef-client?I'm thinking it is nice to be able to have a fully isolated environment usingchef-solo locally with say a Vagrant box or any other vm offering of yourchoice. The reason I say this is if you had all your developers using the sameproduction chef-server and same environment that there is a chance that youcould all stomp on each others toes. I know you can freeze the version but nowI have to keep maintaining my version list locally which I feel could be amaintenance nightmare if you have a lot of cookbooks. My thought is you woulduse chef-solo for local development and then after you commit your changes itgoes to a continuous integration environment where chef-client is used. In thecontinuous integration environment it could use environment=development andthat environment could specify what version to use. After it has successfullybeen tested in the continuous integration environment the productionenvironment file then gets a bump to use the new version that was just tested.Anyone see any holes in this process or have any suggestions for a betterapproach? If you think chef-client would be a better choice for local dev canyou offer up some ideas on how it would work with multiple users?Looking forward to your responses.I also have this question posted here:https://groups.google.com/d/topic/chef-testing/3qZfJqOsycU/discussionThanks,Jay
Archive powered by MHonArc 2.6.16.