厨师和木偶推荐 [英] Chef and Puppet recommendations

问题描述

我想问一下何时，在什么情况下使用木偶以及何时使用厨师。我还发现了 rump ，这是一个p独奏类型的事情，您可以将单个服务器迭代到其上配置，然后将其推送到一系列服务器，使您可以直接查看更改。

I'd like to ask about when and in what circumstances you'd use puppet and when you'd use chef. I've also found rump which is a puppet-solo type of thing where you iterate a single server to its configuration and then push that to a series of servers, allowing you to see changes directly.

我的问题：我应该使用上述哪种方式以及以哪种方式使用？有人可以帮我吗？

我的目标是在不断集成，在rake和git的mono / .Net环境中持续部署的环境中。我想轻松地打包，版本化和部署Web应用程序，并希望将收据用于多个Web服务器的负载均衡器。能够快速删除这些文件，并且在两次升级之间没有任何停机时间。

My aim is in the context of continuous integration, continuous deployment in a mono/.Net environment with rake and git. I would like to package, version and deploy web applications easily and would like to use recepies for a load balancer for multiple web servers. Being able to take these down quickly and not have any downtime in between upgrades.

推荐答案

我会使用Puppet，但我当我写一本关于它的书并在那里工作时，有点偏见。 :)除了Rump，您还可以在其应用模式下使用Puppet-与Chef-solo相同。尽管Rump围绕过程提供了一些优点，但是值得尝试。

I'd use Puppet but I'm kinda biased as I wrote a book about it and work there. :) In addition to Rump you can also use Puppet in its apply mode - which is the same as chef-solo. Although Rump wraps some goodness around the process that's worth trying out.

我会在这里使用Rump作为环绕来给Puppet拍照-你们都可以使用Puppet DSL或Ruby DSL（Chef仅具有Ruby DSL）。使用Puppet创建环境并将git / CI工作流程与您的部署集成起来非常容易。与Rake任务或类似任务集成也很容易。

I'd give Puppet a shot here using Rump as a wrap around - you can both use the Puppet DSL OR Ruby DSL (Chef only has a Ruby DSL). It's very easy to create "environments" using Puppet and to integrate a git/CI workflow with your deployments. It's also easy to integrate with Rake tasks or the like.

这篇关于厨师和木偶推荐的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！