This release includes a new Erlang based server which operates at great scale. Cycle Computing recently ran over 10,000 nodes against one Chef 11 server. [1]
The client will continue to be Ruby, and has many improvements itself, including:
many windows improvements
partial templates
chef-apply, a tool to run a single cookbook against a system
run list based cookbook file evaluation order
substantial improvements on node attributes and precedence handling
We also announced Facebook's use of Chef today. They will be speaking at ChefConf, if you're interested in operating infrastructure at huge scale, it's a talk you don't want to miss.
This release includes a new Erlang based server which operates at great scale. Cycle Computing recently ran over 10,000 nodes against one Chef 11 server. [1]
The client will continue to be Ruby, and has many improvements itself, including:
many windows improvements
partial templates
chef-apply, a tool to run a single cookbook against a system
run list based cookbook file evaluation order
substantial improvements on node attributes and precedence handling
We also announced Facebook's use of Chef today. They will be speaking at ChefConf, if you're interested in operating infrastructure at huge scale, it's a talk you don't want to miss.
Any information on how to migrate from chef server 10.x to 11?
I only see enterprise linux and ubuntu for chef server is that no package
for debian for this?
-Mat
On 4 February 2013 16:22, Bryan McLellan btm@opscode.com wrote:
We're really excited to have released Chef 11!
This release includes a new Erlang based server which operates at great
scale. Cycle Computing recently ran over 10,000 nodes against one Chef 11
server. [1]
The client will continue to be Ruby, and has many improvements itself,
including:
many windows improvements
partial templates
chef-apply, a tool to run a single cookbook against a system
run list based cookbook file evaluation order
substantial improvements on node attributes and precedence handling
We also announced Facebook's use of Chef today. They will be speaking at
ChefConf, if you're interested in operating infrastructure at huge scale,
it's a talk you don't want to miss.
[2013-02-04T17:08:38+00:00] ERROR: Running exception handlers
[2013-02-04T17:08:38+00:00] ERROR: Exception handlers complete
Chef Client failed. 22 resources updated
[2013-02-04T17:08:38+00:00] FATAL: Stacktrace dumped to /opt/chef-server/embedded/cookbooks/cache/chef-stacktrace.out
[2013-02-04T17:08:38+00:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: execute[/opt/chef-server/bin/chef-server-ctl start rabbitmq] (chef-server::rabbitmq line 76) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of /opt/chef-server/bin/chef-server-ctl start rabbitmq ----
STDOUT: warning: rabbitmq: unable to open supervise/ok: file does not exist
STDERR:
---- End output of /opt/chef-server/bin/chef-server-ctl start rabbitmq ----
Ran /opt/chef-server/bin/chef-server-ctl start rabbitmq returned 1
On Feb 4, 2013, at 8:22 AM, Bryan McLellan wrote:
We're really excited to have released Chef 11!
This release includes a new Erlang based server which operates at great scale. Cycle Computing recently ran over 10,000 nodes against one Chef 11 server. [1]
The client will continue to be Ruby, and has many improvements itself, including:
many windows improvements
partial templates
chef-apply, a tool to run a single cookbook against a system
run list based cookbook file evaluation order
substantial improvements on node attributes and precedence handling
We also announced Facebook's use of Chef today. They will be speaking at ChefConf, if you're interested in operating infrastructure at huge scale, it's a talk you don't want to miss.
Jeff, thanks for asking, we'll update the release notes to be more
specific about the Windows work, which spanned a range of changes from
fixing log output to improving performance of chef-client on the Windows
platform.
A bigger bang piece of work is the new registry_key resource
(registry_key Resource) that lets you
manipulate the registry without including the Windows cookbook. A nice new
feature there is the ability to control the registry's architecture
through the :architecture attribute -- automation tasks often need
explicit control over reading / writing to / from the 32-bit or 64-bit
view of the registry, and that's what this resource gives you.
You can do so much on *nix platforms with core resources, and I personally
like being able to have more of that experience on Windows.
On Mon, Feb 4, 2013 at 1:57 PM, joe.nuspl nuspl@nvwls.com wrote:
chef-server failed on CentOS-5.8 x86_64...
[2013-02-04T17:08:38+00:00] ERROR: Running exception handlers
[2013-02-04T17:08:38+00:00] ERROR: Exception handlers complete
Chef Client failed. 22 resources updated
[2013-02-04T17:08:38+00:00] FATAL: Stacktrace dumped to /opt/chef-server/embedded/cookbooks/cache/chef-stacktrace.out
[2013-02-04T17:08:38+00:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: execute[/opt/chef-server/bin/chef-server-ctl start rabbitmq] (chef-server::rabbitmq line 76) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of /opt/chef-server/bin/chef-server-ctl start rabbitmq ----
STDOUT: warning: rabbitmq: unable to open supervise/ok: file does not exist
STDERR:
---- End output of /opt/chef-server/bin/chef-server-ctl start rabbitmq ----
Ran /opt/chef-server/bin/chef-server-ctl start rabbitmq returned 1
On Mon, Feb 4, 2013 at 12:45 PM, Mat Davies ashmere@gmail.com wrote:
Any information on how to migrate from chef server 10.x to 11?
Not yet, we're planning on providing tools to help with the data
migration and will be working on that soon.
I only see enterprise linux and ubuntu for chef server is that no package
for debian for this?
We're only releasing packages for the systems we're testing and
verifying now. I don't have a date for debian support, it will likely
be based on demand. However I have installed the packages for Ubuntu
on Debian 6.0.6 and I've seen others say that it worked for them as
well.
The Chef 11 client will be. I've done a little testing and it looks
like it will work fine. We're looking to see what community support
there is for building server packages and what demand there is.
Omnibus is the official way forward for Opscode, and Omnibus does come
in a deb format. If folks want packages that are distribution policy
compliant, we're looking for that distribution's community to help
produce them.