我应该使用 Chef 或其他工具来管理服务器
我在负载均衡器后面有 4 个服务器、一个临时服务器、一个数据库服务器和一个用于托管多个网站的 Web 应用程序的实用程序服务器。
我应该跳转到 Chef 来管理这些服务器还是应该手动维护它们？服务器是用spill构建的，但当时只有两台。现在有四个维护变得更加成为一个问题。
我想听听厨师和其他类似厨师的工具的经验以及优缺点。
谢谢！
I have 4 servers behind a load balancer and a staging server, a db server, and a utility server for a web application that hosts a number of web sites.
Should I make the jump to Chef to manage these servers or should I just maintain them manually? The servers were built using sprinkle but at that time there were only two. Now that there are four maintenance is becoming more of an issue.
I'd like to hear experiences and the pros and cons of chef and other chef-like tools.
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我们迁移到 Chef，现在我们的应用程序只需 1 分钟即可重新部署。所以它肯定会得到回报。
然而，我们花了很长时间（几个月）才达到我们对厨师部署策略感到满意的程度。事后看来，我们会有几个备用盒子来尝试“从头开始”部署。我当然不会建议在没有精确的设置镜像和大量测试的情况下在生产环境中尝试 Chef，我也不建议在尚未从头开始“cheffed”的设置上使用 Chef。
话虽如此，Chef 比我们考虑过的其他选项要好得多，现在我们已经走出了另一边，在多个服务器上部署该应用程序的新版本变得轻而易举。将来我将在我拥有的任何暂存或生产环境中使用它。
总而言之，是的，但前提是您的客户/雇主意识到他们可能需要一段时间才能看到收益，而收益将是相当可观的。
We moved to Chef, and we now have a 1 minute redeployment for our app. So it certainly pays off.
However it took a long time (a few months) to get to the point where we were happy with the chef deployment strategy. With hindsight we would have had several spare boxes around to try out a 'from scratch' deployment. I certainly wouldn't advise trying chef in a production environment without an exact mirror of the setup and lots and lots of tests, nor would I advise using chef on a setup that hasn't been 'cheffed' from scratch.
Having said that, Chef is far better than the other options we looked at and now that we are out the other side it's a breeze deploying a new version of the app on multiple servers. In future I'll be using it for any staging or production environment I have.
In summary, yes, but only if your client/employer is aware that it may take some time before they see the benefits, which will be considerable.
Chef 的学习曲线很陡，因此需要一段时间（至少几周）才能熟悉如何使用它。
但是一旦您掌握了基础知识，它就是一个非常方便的系统，并且可以简化任意数量的任务 - 即使对于最小的基础设施也是如此。
开始时的一些注意事项。
您将设置和拆除云服务器数十次，只是为了掌握它的窍门。实验。
标准的 opscode 食谱 (github.com/opscode/cookbooks) 非常有用。但是您将需要针对您的特定情况扩展/定制其中的许多内容。您需要在网上搜索 opscode/cookbooks 存储库中缺少的说明书。
阅读 opscode 食谱，并阅读 37signals 食谱。
应用程序和数据库说明书适用于使用 MySQL 和 Memcached 的标准 Rails 应用程序。就这对您的描述而言，您非常幸运。Chef has a steep learning curve, so it will take a while - at least a few weeks - to become familiar with how to use it.
But once you pick up the basics, it is a very handy system, and can simplify any number of tasks - even for the smallest of infrastructures.
A few notes for when you start.
You will be setting up and tearing down cloud servers dozens of times, just to get the hang of it. Experiment.
The standard opscode cookbooks (github.com/opscode/cookbooks) are very useful. But you will need to extend/customize many of them for your particular case. And you will need to search the 'net for cookbooks that are missing from the opscode/cookbooks repository.
Read the opscode cookbooks, and read the 37signals cookbooks too.
The
applicationanddatabasecookbooks are geared towards standard Rails apps with MySQL and Memcached. To the extent that this describes you, you are way in luck.