General discussion about Chef

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


Chronological Thread 
  • From: Stéphane Jourdan < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Re: Peoples' thoughts on Amazon AWS OpsWorks?
  • Date: Thu, 21 Feb 2013 16:00:54 +0100
Hi, 

I confirm it's running a 0.9.15.3 fork of chef from Peritor, last updated 2 years ago.
Deployed cookbooks from Opscode looks quite dated too (think of a 0.9 Apache cookbook for example).

I'm still experimenting but am somewhat disappointed for my usage.

For those who wonder, you get 
  • an equivalent of a standard chef-repo, 
  • versionned by date and symlinked to "current" for usage.
  • a Gemfile for the hellish deps for such old software reqs
  • about 35 cookbooks, some AWS custom, many not
  • ruby1.8 ro run chef-solo (ie.: ruby1.8 /opt/aws/opsworks/current/bin/chef-solo -j /var/lib/aws/opsworks/chef/2013-02-21-13-58-55-01.json -c /opt/aws/opsworks/current/conf/solo.rb)

Cheers,
Stef

Stephane Jourdan < " target="_blank"> >
Green Alto / 10, Rue Chaptal / 34000 Montpellier, FR
+33(0)411 934 340 / +33(0)684 531 618


On Thu, Feb 21, 2013 at 2:51 PM, Jesse Campbell < " target="_blank"> > wrote:
According to the amazon pages, this is built against https://github.com/peritor/chef/commits/scalarium-0.8-stable
which appears to be a fork of chef that hasn't been updated since the middle of 2010.

I'm just going to take a gamble and say that
a) most of my company's custom cookbooks won't work without serious modifications
b) things like 'search' and 'environments' and 'platform_family' will be entirely foreign

oh yeah, and it doesn't support centos at all, so there's another big chunk of work.

i think i'll stick with the nice shiny chef 11, thanks very much :D


On Wed, Feb 20, 2013 at 12:38 PM, Morgan Blackthorne < " target="_blank"> > wrote:
Interesting, I'm definitely curious to hear more about it. I do a lot of AMI-based bootstrapping of Chef and it would be very interesting if there was a more integrated solution where I could assign the role at say... boot time, or via autoscaling/etc.

--
~*~ 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 Wed, Feb 20, 2013 at 9:06 AM, John Martinez < " target="_blank"> > wrote:
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
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.

§