[chef] Re: Re: Re: Re: Re: AWS OpsWorks custom


Chronological Thread 
  • From: Morgan Blackthorne < >
  • To: " " < >
  • Subject: [chef] Re: Re: Re: Re: Re: AWS OpsWorks custom
  • Date: Fri, 24 May 2013 13:58:24 -0700

*nod* In theory, OpsWorks is great. In practice... losing the ability to reliably use the vast amount of community cookbooks is a pretty strong negative.

--
~*~ StormeRider ~*~

"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS


On Fri, May 24, 2013 at 1:52 PM, Liam Kirsher < " target="_blank"> > wrote:
There's no specific reason -- I'm just trying to find the quickest way to setup deployment infrastructure.  OpsWorks looked like it would be easy to set up, and integrated with all the other AWS services.
However, now that I'm aware of the chef version issue... not so much.
So, I'm setting up a Hosted Chef account now.
I'm sure I'll have more questions, though. Thanks for you help!

On May 20th AWS mentioned they were upgrading chef to version 11, but there was no mention of when that would be accomplished.


On 05/24/2013 01:33 PM, Morgan Blackthorne wrote:
I don't know your requirements, but I do have to ask; is there a specific reason you're looking at using OpsWorks instead of running Hosted Chef or an Open Source Chef server? Until AWS upgrades OpsWorks to Chef 11, I think it's a bit crippled, personally.

--
~*~ StormeRider ~*~

"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS


On Fri, May 24, 2013 at 1:11 PM, Liam Kirsher < " target="_blank"> > wrote:
Noah,

Thanks for mentioning that!
Is there any way to know which cookbooks work with OpsWorks and which
don't?  These are the ones I think I need:
> cookbook 'nginx'
> cookbook 'rabbitmq'
> cookbook 'mongodb'
> cookbook 'mercurial'
> cookbook 'newrelic'
> cookbook 'newrelic_monitoring'
> cookbook 'django'
> cookbook 'application'
> cookbook 'application_nginx'
> cookbook 'application_python'
> cookbook 'uwsgi'

(Along with other cookbooks they require, I guess.)

Thanks again.


On 05/23/2013 06:25 PM, Noah Kantrowitz wrote:
> On May 23, 2013, at 5:42 PM, < " target="_blank"> > wrote:
>
>> I'm using AWS OpsWorks for a project.  I think most of my cookbooks will not
>> require modification, and I can just use the ones from
>> http://github.com/opscode-cookbooks/
>> I expect there will be some of those I will need to modify and perhaps will
>> need to create some new ones.
>> (For example, I would like to use the django recipe, but want to substitute
>> uwsgi for gunicorn.)
> I'm afraid OpsWorks is on such an old version of Chef that you may find that few community cookbooks work on it as is. There is no good solution for this that I'm aware of, except for Amazon moving to a somewhat more recent version of Chef.
>
> --Noah
>

--
Liam Kirsher
PGP: http://liam.numenet.com/pgp/



-- 
Liam Kirsher
PGP: http://liam.numenet.com/pgp/




Archive powered by MHonArc 2.6.16.

§