[chef] Re: Re: Re: Re: Peoples' thoughts on Amazon AWS OpsWorks?


Chronological Thread 
  • From: John Martinez < >
  • To: " " < >
  • Subject: [chef] Re: Re: Re: Re: Peoples' thoughts on Amazon AWS OpsWorks?
  • Date: Wed, 20 Feb 2013 09:06:08 -0800

We have a similar workflow, but using Hosted Chef. OpsWorks looks very interesting, but I'm not sure if it's a replacement for Jenkins+CFN+Chef the way we've set things up. I'll be playing more with it when it's available, that's for sure!

-john

On Feb 20, 2013, at 8:51 AM, Peter Norton < "> > wrote:

OpsWorks is so similar to what we ended up building for ourselves using cloudformation and chef-solo that I wish we'd waited.  We already have a practice of downloading a small tarball that chef-solo will use to download the appropriate bundle and run the roles we've defined there, including registering with a chef server.  This is really promising.


On Wed, Feb 20, 2013 at 11:39 AM, Christopher Brown < " target="_blank"> > wrote:
Just to allay people's fears and maybe stem the tide of speculation, we've worked with Amazon off-and-on a few times and have some involvement with OpsWorks.
There will probably be more visible press soon, as we get closer to #ChefConf 2013 (http://chefconf.opscode.com/).  I'll make sure the press and marketing team shed some light on this.

Cheers,
Chris


They had a twitter post about it.

No press release that I've seen yet :(




"Since AWS OpsWorks uses Chef recipes, you can leverage hundreds of community-built configurations such as PostgreSQL, Nginx, and Solr."

https://aws.amazon.com/opsworks/

This is apparently based on Scalarium, from AWS' Peritor acquisition.  Interesting discussion at ycombinator: http://news.ycombinator.com/item?id=5243196

Haven't really dug into it yet.  Surprised nothing from OpsCode about it.

--
Denis Haskin





Archive powered by MHonArc 2.6.16.

§