Please test Chef!

#1

Hi guys!

We let the 0.6.0 release get a little long in the tooth, but it’s
nearly ready to roll. We’ve got the new Web UI work, lots of bug
fixes, and some performance patches. Everything should be pretty
smooth, but I would love to get a few “yep, nothing is totally hoarked
for me” replies. Mind testing out chef from opscode/master, and
letting me know if things are working well for you?

In the future we’re going to be back on a two-week release cycle,
which makes this problem less of an issue. (Plus, we’re getting much
better integration test coverage!)

Thanks for taking the time to test,
Adam

–
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-4759 E: adam@opscode.com

0 Likes
#2

On Apr 26, 2009, at 1:12 PM, Adam Jacob wrote:

We let the 0.6.0 release get a little long in the tooth, but it’s
nearly ready to roll. We’ve got the new Web UI work, lots of bug
fixes, and some performance patches. Everything should be pretty
smooth, but I would love to get a few “yep, nothing is totally hoarked
for me” replies. Mind testing out chef from opscode/master, and
letting me know if things are working well for you?

With my existing test environment using Chef 0.5.7, I had to do a
little extra work to get chef-server to jive with our latest passenger-
ified chef-server.

I reran the chef-solo bootstrap with the tarball on S3, because the
installation wipes out the config.ru, init.rb, etc from the chef
cookbook. This should be expected on 0.6.0 release as well, as the
directory won’t exist. It’s probably a good idea to use the config.ru,
init.rb and production.rb from the bootstrap recipe since thats the
primary ‘default’ configuration from following the Chef Wiki’s
Installation page.

I also had to restart Apache2 after running the chef-solo with the
bootstrap recipes for it to properly pick up the changes.

When writing the doc for converting chef-server via runit to
passenger[1], I did test 0.5.6 to 0.5.7-as-of-Friday, and the process
was quite straightforward actually, considering the complete
deployment change, as well as the broad changes that 0.6.0 brings.

Also, on a fresh new system, I had to run ‘rake install’ via sudo to
get it to create /var/chef, due to Merb.load_dependencies on line 30
of the chef-server Rakefile. I can open a bug.

To wit, I did install 0.5.7 on a fresh Ubuntu 9.04 VM using the
"installing from HEAD" instructions as posted on the wiki and
everything worked as documented.

[1] http://wiki.opscode.com/display/chef/How+to+Convert+chef-server+from+runit+to+Passenger

–
Joshua Timberman | www.opscode.com
joshua@opscode.com | 720.878.4322

0 Likes
#3

On Apr 26, 2009, at 12:12 PM, Adam Jacob wrote:

Hi guys!

We let the 0.6.0 release get a little long in the tooth, but it’s
nearly ready to roll. We’ve got the new Web UI work, lots of bug
fixes, and some performance patches. Everything should be pretty
smooth, but I would love to get a few “yep, nothing is totally hoarked
for me” replies. Mind testing out chef from opscode/master, and
letting me know if things are working well for you?

In the future we’re going to be back on a two-week release cycle,
which makes this problem less of an issue. (Plus, we’re getting much
better integration test coverage!)

Thanks for taking the time to test,
Adam

Hey!

Chef from opscode/master works fine with chef-solo for my fairly

complex recipe set on gentoo, thumbs up. It is still marked as version
0.5.7 though, is this going to become 0.6.0 or am i missing something?

Thanks

Ezra Zygmuntowicz
ez@engineyard.com

0 Likes
#4

On 27/04/2009, at 4:02 PM, Ezra Zygmuntowicz wrote:

On Apr 26, 2009, at 12:12 PM, Adam Jacob wrote:

Hi guys!

Thanks for taking the time to test,
Adam

Hey!

Chef from opscode/master works fine with chef-solo for my fairly
complex recipe set on gentoo, thumbs up. It is still marked as
version 0.5.7 though, is this going to become 0.6.0 or am i missing
something?

It’ll be bumped when Adam builds the gems, I presume.

FWIW, my nginx-chef-server+passenger bootstrap and full environment
here is working perfectly.

I have noticed a small issue with the webUI in that when you open
branches of the treeview and close them, they cannot be opened again
(bloody javascript)

Regards,

AJ

0 Likes
#5

On Apr 26, 2009, at 3:12 PM, Adam Jacob wrote:

We let the 0.6.0 release get a little long in the tooth, but it’s
nearly ready to roll. We’ve got the new Web UI work, lots of bug
fixes, and some performance patches. Everything should be pretty
smooth, but I would love to get a few “yep, nothing is totally hoarked
for me” replies. Mind testing out chef from opscode/master, and
letting me know if things are working well for you?

I updated our server and the 35 clients that we have deployed to use
the latest from head today. Things are looking good!

-Mark

0 Likes
#6

On Apr 26, 2009, at 10:04 PM, Arjuna Christensen wrote:

I have noticed a small issue with the webUI in that when you open
branches of the treeview and close them, they cannot be opened again
(bloody javascript)

On that topic, I noticed that if an attribute has a nil value, the
next attribute is rather munged up into the same line.

–
Joshua Timberman | www.opscode.com
joshua@opscode.com | 720.878.4322

0 Likes
#7

Hi,

We let the 0.6.0 release get a little long in the tooth, but it’s
nearly ready to roll. We’ve got the new Web UI work, lots of bug
fixes, and some performance patches. Everything should be pretty
smooth, but I would love to get a few “yep, nothing is totally hoarked
for me” replies. Mind testing out chef from opscode/master, and
letting me know if things are working well for you?

Just installed from HEAD and had a few minor problems. I don’t know if
they’re related to HEAD, my existig chef-server instalation or my new
chef cookbooks that I adapted from bootstrap-0.5.7.tgz.

  • Had problems with merb-core. Yeld an error like “can’t activate
    merb-core (= 1.0.9, runtime), already activated merb-core-1.0.11”.
    Solved with

    gem uninstall merb-core -v=1.0.9
    gem install merb

  • Had problems with chef_server.conf.erb from chef cookbook. There are
    some hardcoded paths in the template:

Alias /facebox /usr/lib/ruby/gems/1.8/gems/chef-server-slice-0.5.7/
public/facebox
Alias /images /usr/lib/ruby/gems/1.8/gems/chef-server-slice-0.5.7/
public/images
Alias /javascripts /usr/lib/ruby/gems/1.8/gems/chef-server-slice-0.5.7/
public/javascripts
Alias /stylesheets /usr/lib/ruby/gems/1.8/gems/chef-server-slice-0.5.7/
public/stylesheets
Alias /web-app-theme /usr/lib/ruby/gems/1.8/gems/chef-server-
slice-0.5.7/public/web-app-theme

In my case (Debian 5.0) I solved it by changing /usr/lib/ruby/gems/1.8
to /var/lib/gems/1.8

Best Regards

Miguel Cabeça

0 Likes
#8

Hi,

Just installed from HEAD and had a few minor problems. I don’t know
if they’re related to HEAD, my existig chef-server instalation or my
new chef cookbooks that I adapted from bootstrap-0.5.7.tgz.

I also had to change the passenger recipe (add full path to passenger-
install-apache2-module):

execute “passenger_module” do
command 'echo -en “\n\n\n\n” | /var/lib/gems/1.8/bin/passenger-
install-apache2-module’
creates node[:passenger][:module_path]
end

Debian doesn’t come with the $PATH set for ruby bin directory.

Miguel Cabeça

0 Likes