- From: Adam Jacob <adam@opscode.com>
- To: chef@lists.opscode.com
- Subject: Re: Chef questions
- Date: Mon, 25 May 2009 10:40:04 -0700
On Mon, May 25, 2009 at 1:01 AM, Stas Oskin <stas.oskin@gmail.com> wrote:
>
How stable Chef is? Can it be used in production environment?
Chef is pretty stable - there are a few parts that are still in flux,
and we're liable to have a few non-backwards compatible releases in
the near future. The things that are not liable to change:
1) The core recipe DSL - recipes you write today will almost certainly
run un-changed tomorrow.
2) The majority of the internals - things like the
Resource->Platform->Provider mechanic.
Things that are going to change in the next release, which will be the
first in a series of backwards-compat breaking releases:
1) Role support, along with the Chef Server being locked down for
AuthN by default.
2) We no longer ship all the cookbooks to every node - we now only
ship those that are required.
The next release after that will see another breaking change, namely
shifting from OpenID for the API authentication to signed headers,
much like EC2.
Finally, there will definitely be work on the search functionality.
That will likely not break back-compat (as you can just continue to
use the ferret indexes) - but no promises. :)
Regards,
Adam
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-4759 E: adam@opscode.com
Archive powered by MHonArc 2.6.16.