S
S
SMiX2010-09-08 03:48:40
ruby
SMiX, 2010-09-08 03:48:40

Update means chef?

Previously, I used capistrano to roll out new releases of the application, but now we have 10 production servers, and due to the specifics of the service, new ones need to be added regularly.
In order to save myself time for the future, I decided to spend a couple of days automating the process of connecting a node to the system. As soon as I started writing a script for capistrano, a note appeared on the hub about chef. This is how it always happens!
I read the note, studied the documentation, fiddled with the cookbooks, and everything worked out.
Now I put new servers into operation with one command. But there was one unresolved issue:
The application is being actively developed and needs to be updated quite often. This point also needs to be automated. You can make it so that knife bootstrapadded information about new servers to capistrano configs, but I think that this is an irrational way, and everything can be solved using chef. How is this possible? A laconic
crosspost on stackoverflow.com. PS. After reading the documentation and posts on habré, I got the impression that the chef is needed exclusively to work with new servers using the knife bootstrap command . Is it so? Or can servers really be managed , as the title of this article suggests?

Answer the question

In order to leave comments, you need to log in

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question