blocks|key|133564|text|我不知道旧的OpsWorks食谱，但可以查看https://github.com/poise/application_examples/中使用普通厨师(也可以在OpsWorks上工作)进行Rails+(以及更多)部署的一些示例。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|133565|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/poise/application_examples/^0|M|1A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I don't know about the old OpsWorks cookbooks but check out <a href="https://github.com/poise/application_examples/" rel="nofollow">https://github.com/poise/application_examples/</a> for some examples of doing doing Rails (and more) deploys using plain Chef (will work on OpsWorks too).

blocks|key|126846|text|opsworks_ruby+cookbook+on+the+Supermarket基本上就是您需要的一切。它甚至将应用程序放入相同的目录(即/srv/www/app_name/)，设置database.yml，等等。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|126847|这个菜谱与其他非OpsWorks菜谱的主要区别在于，它将为您删除OpsWorks配置中的所有内容。你不必自定义食谱，只需确保你的应用程序和层的名称正确-它将从那里构建一切-包括你的database.yml的RDS配置！|126848|主要的区别是，OpsWorks中的层将不是"Ruby感知的“，所以您将不会有Rails或Ruby之类的内容的字段，而是需要在其他地方管理这些内容。加载ENV+vars的方式也略有不同。|126849|此外，请务必阅读亚马逊网络服务为OpsWorks实现的Chef+12。从技术上讲，他们有两本厨师食谱在运行，他们内部的一本和你的一本。它们包括管理代理是最新的，加载用户(对于ssh)，布线监控，等等。你将不得不管理其余的。|126850|我们要么用超市里的个人食谱取代了他们巨大食谱中的内容，要么只是重写了它。例如，老的厨师11+opsworks_initial_setup有一些关于调整网络和linux设置的东西-我们重新创建了它。|126851|它还根据需要使用deploy+users，例如：|126852|$+ps+-eo+user,command+USER+++++COMMAND+//+snip+root+++++nginx:+master+process+/usr/sbin/nginx+-c+/etc/nginx/nginx.conf+aws++++++opsworks-agent:+master+10820+aws++++++opsworks-agent:+keep_alive+of+master+10820+aws++++++opsworks-agent:+statistics+of+master+10820+aws++++++opsworks-agent:+process_command+of+master+10820+deploy+++unicorn_rails+master+--env+production+--daemonize+-c+/srv/www/app/shared/config/unicorn.conf+deploy+++unicorn_rails+worker[0]+--env+production+--daemonize+-c+/srv/www/app/shared/config/unicorn.conf+deploy+++unicorn_rails+worker[1]+--env+production+--daemonize+-c+/srv/www/app/shared/config/unicorn.conf+deploy+++unicorn_rails+worker[2]+--env+production+--daemonize+-c+/srv/www/app/shared/config/unicorn.conf+deploy+++unicorn_rails+worker[3]+--env+production+--daemonize+-c+/srv/www/app/shared/config/unicorn.conf+nginx++++nginx:+worker+process+nginx++++nginx:+worker+process|126853|这只是进程输出的一个小示例，但是root会根据需要引导程序，并且每个进程都利用自己的用户来限制权限和访问。|126854|entityMap|0|LINK|mutability|MUTABLE|url|https://supermarket.chef.io/cookbooks/opsworks_ruby^0|1Y|I|0|15|0|0|0|0|0|0|0|0|P1|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@$9|14|A|15|1|16]]|E|$]]|$1|F|3|G|5|6|7|17|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|18|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|19|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1A|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1B|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1C|8|@$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|R|3|S|5|6|7|1F|8|@]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|U|$V|$5|W|X|Y|E|$Z|10]]]]

The <a href="https://supermarket.chef.io/cookbooks/opsworks_ruby" rel="nofollow">opsworks_ruby cookbook on the Supermarket</a> is basically everything you need. It even puts the apps into the same directories (i.e. <code>/srv/www/app_name/</code>), sets up your database.yml, etc, etc.

The main difference between this recipe and other non-OpsWorks recipes is that this will pull everything out of the OpsWorks configuration for you. You don't have to customize the recipes, just make sure your app and layers are named correctly - it'll build everything from there - including your RDS configuration for the database.yml!

The main difference is that the layers in OpsWorks won't be "Ruby aware" so you won't have fields for Rails-ish or Ruby-ish things and instead will need to manage those elsewhere. The way ENV vars is loaded is a little different too.

Also be sure to read up on AWS' implementation of Chef 12 for OpsWorks. They technically have two chef cookbooks running, their internal one and yours. Theirs include managing the agent is up-to-date, loading up users (for ssh), wiring up monitoring, etc. You'll have to manage the rest.

We've either replaced stuff from their huge cookbook with individual cookbooks from the Supermarket or just rewrote it. For instance, the old Chef 11 opsworks_initial_setup had a couple things around tweaking network and linux settings - we recreated that.

It also does use deploy users as applicable, for instance:

<code>$ ps -eo user,command
USER COMMAND
// snip
root nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf
aws opsworks-agent: master 10820
aws opsworks-agent: keep_alive of master 10820
aws opsworks-agent: statistics of master 10820
aws opsworks-agent: process_command of master 10820
deploy unicorn_rails master --env production --daemonize -c /srv/www/app/shared/config/unicorn.conf
deploy unicorn_rails worker[0] --env production --daemonize -c /srv/www/app/shared/config/unicorn.conf
deploy unicorn_rails worker[1] --env production --daemonize -c /srv/www/app/shared/config/unicorn.conf
deploy unicorn_rails worker[2] --env production --daemonize -c /srv/www/app/shared/config/unicorn.conf
deploy unicorn_rails worker[3] --env production --daemonize -c /srv/www/app/shared/config/unicorn.conf
nginx nginx: worker process
nginx nginx: worker process
</code>

Just a small example of the process output but root boots things as needed and each process utilizes their own users to limit rights and access.

blocks|key|27721|text|我认为最常见的方式是使用超市中的“应用程序”食谱：https://supermarket.chef.io/cookbooks/application/versions/4.1.6+(它也基于Poise)。注意：使用的是版本4的，他们删除了v5中几乎所有的好特性。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|27722|它将创建目录结构，支持不同的部署策略，并提供一些可以挂钩的事件。请注意:在我看来，Opsworks文档在“使用opsworks和chef12进行部署”这一主题上还算不错:来自gui的信息(如repo-url等)并不在node对象上，而是在应用程序的数据库标签中。对于调试，查看/var/chef/runs/<run-id>/目录以查看其中的可用内容非常有帮助。展示这个想法的一小段代码：|CODE|27723|app+=+search("aws_opsworks_app").first
application+"#{app['shortname']}"+do
++owner+'root'
++group+'root'
++repository+app['app_source']['url']
++revision+++'master'
++path+"/srv/#{app['shortname']}"
end|code-block|syntax|javascript|27724|这将在/srv上创建releases/current目录结构并签出代码。注意:您可能认为您在GUI中指定的ssh-key会以某种方式自动放在适当的位置。不是的，你得自己处理。查看chef11+opsworks食谱：https://github.com/aws/opsworks-cookbooks/blob/release-chef-11.10/scm_helper/libraries/git.rb|27725|entityMap|0|LINK|mutability|MUTABLE|url|https://supermarket.chef.io/cookbooks/application/versions/4.1.6|1|https://github.com/aws/opsworks-cookbooks/blob/release-chef-11.10/scm_helper/libraries/git.rb^0|2X|8|P|1S|0|0|30|4|3U|O|0|0|3|4|2Z|2L|1|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@$9|12|A|13|1|14]]|E|$]]|$1|F|3|G|5|6|7|15|8|@$9|16|A|17|B|H]|$9|18|A|19|B|H]]|D|@]|E|$]]|$1|I|3|J|5|K|7|1A|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|1B|8|@$9|1C|A|1D|B|H]]|D|@$9|1E|A|1F|1|1G]]|E|$]]|$1|P|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W]]|X|$5|S|T|U|E|$V|Y]]]]

I think the most common way is to use the "application" cookbook from the supermarket: <a href="https://supermarket.chef.io/cookbooks/application/versions/4.1.6" rel="nofollow noreferrer">https://supermarket.chef.io/cookbooks/application/versions/4.1.6</a> (which is also based on Poise). Attention: use version ~4, they removed almost all of the good features in v5.

It will create the directory structure, supports different deploy-strategies and offers some events to hook.
Be aware: In my opinion, the Opsworks documentation is semi-good when it comes to the "deploy with opsworks and chef12" topic: The information from the gui (like repo-url etc), is not on the <code>node</code> object but in a databag from the application. For debugging it can be very helpful to have a look into the <code>/var/chef/runs/&lt;run-id&gt;/</code> directory to see what is available from where. 
Small snippet that shows the idea: 

<pre><code>app = search("aws_opsworks_app").first
application "#{app['shortname']}" do
 owner 'root'
 group 'root'
 repository app['app_source']['url']
 revision 'master'
 path "/srv/#{app['shortname']}"
end
</code></pre>

This will create the releases/current directory structure on <code>/srv</code> and checkout the code. Note: you could think that ssh-key you specify in the GUI is somehow automatically put in the proper place. Its not, you'll have to take care of that on your own. Check the chef11 opsworks cookbook: <a href="https://github.com/aws/opsworks-cookbooks/blob/release-chef-11.10/scm_helper/libraries/git.rb" rel="nofollow noreferrer">https://github.com/aws/opsworks-cookbooks/blob/release-chef-11.10/scm_helper/libraries/git.rb</a>

Has anyone attempted to convert Opsworks Chef v11 recipes to Chef v12?

Im running multiple stacks on Chef 11 and decided to start converting some of them to Chef 12. Since AWS dropped their opsworks app layers, such as <code>rails</code> layer recipes, we (opsworks users) are now responsible for creating <code>deploy</code> user, git checkout repos into <code>deploy_to</code>, etc. 

Its all good with flexibility and no more namespace conflicts, but we are missing all that good stuff opsworks was giving us for free.

Wonder if someone converted recipes for Chef 12 and open-sourced? Otherwise, is community interested in these recipes at all? Im pretty sure Im not alone here.

Thank you in advance!

Opsworks Chef 12 recipes

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

有没有人尝试过将Opsworks厨师的v11食谱转换为v12厨师？我在厨师11上运行了多个堆栈，并决定开始将其中一些转换为厨师12。自从亚马逊网络服务删除了他们的opsworks应用层，例如rails层食谱，我们(opsworks用户)现在负责创建deploy用户，git结帐repos到deploy_to等。这一切都很...

问Opsworks Chef 12食谱
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Opsworks Chef 12食谱EN