I noticed that the Opscode Chef cookbooks don’t tend to support Ubuntu
Hardy (8.04.2).
Hardy is a Long Term Service (LTS) release which means Canonical will
support it for 5 years instead of turning off the apt repositories
after 18 months.
I was at a client site the other day and notice apt-get wasn’t working
on their ubuntu 7.10 servers. There is a workaround but it’s a nasty
reminder that you really only get 18 months support on the standard
releases.
Is there interest here for Hardy recipes? Are there reasons Hardy is
problematic for chef users?
thanks,
Mike
On Jun 23, 2009, at 8:36 PM, Mike Bailey wrote:
Is there interest here for Hardy recipes? Are there reasons Hardy is
problematic for chef users?
As previously stated, the primary reason is that Intrepid/Jaunty had
CouchDB available, so it was the path of least resistance. Most of the
recipes will "just work" on Hardy, excepting the ones that check for
codename intrepid or jaunty. The biggest issue I know off the top of
my head is OpenLDAP because the configuration schema changes betwen
hardy -> intrepid+.
If you find other issues with the opscode/cookbooks, please file
tickets in Jira under the Chef Cookbooks project.
--
Opscode, Inc
Joshua Timberman, Senior Solutions Engineer
C: 720.878.4322 E: joshua@opscode.com
On Tue, Jun 23, 2009 at 8:36 PM, Mike Baileymike@bailey.net.au wrote:
I noticed that the Opscode Chef cookbooks don't tend to support Ubuntu
Hardy (8.04.2).
I think it's mostly that Hardy doesn't have a couchdb package,
followed by most people develop on newer releases. Lots of cool new
technology between Hardy and Jaunty and all that.
Does chef-client/chef-solo use couchdb?
On Wed, Jun 24, 2009 at 2:34 PM, Bryan McLellanbtm@loftninjas.org wrote:
On Tue, Jun 23, 2009 at 8:36 PM, Mike Baileymike@bailey.net.au wrote:
I noticed that the Opscode Chef cookbooks don't tend to support Ubuntu
Hardy (8.04.2).
I think it's mostly that Hardy doesn't have a couchdb package,
followed by most people develop on newer releases. Lots of cool new
technology between Hardy and Jaunty and all that.
On 24/06/2009, at 4:48 PM, Mike Bailey wrote:
Does chef-client/chef-solo use couchdb?
Just the server.
Ubuntu 8.04.x was our initial most-tested platform, although many of
the new cookbooks are targeted towards Jaunty. These cookbooks are
only meant as a starting point, and supporting more distributions out
of the box is something that we'd love to do.
Feel free to open tickets against the Cookbooks project (http://tickets.opscode.com/browse/COOK
). Maybe a test integration run of the entire cookbooks as they stand
now against 8.04.2 is in order?
On Wed, Jun 24, 2009 at 2:34 PM, Bryan McLellanbtm@loftninjas.org
wrote:
On Tue, Jun 23, 2009 at 8:36 PM, Mike Baileymike@bailey.net.au
wrote:
I noticed that the Opscode Chef cookbooks don't tend to support
Ubuntu
Hardy (8.04.2).
I think it's mostly that Hardy doesn't have a couchdb package,
followed by most people develop on newer releases. Lots of cool new
technology between Hardy and Jaunty and all that.
--
AJ Christensen, Software Engineer
Opscode, Inc.
E: aj@opscode.com
I've added recipes to deprec[1] that will install Chef server/client
onto Hardy. It takes about ten minutes as it installs ruby-1.8.7-p174
and couchdb-0.8.0 from source.
sudo gem install deprec
cap deprec:chef:install HOSTS=host1.example.com
Enter Chef server hostname
chef.failmode.com
Select Chef version to install:
- client
- server
? 2
This has simplified the setup of Chef servers and client for me while
I've been testing.
[1] http://www.deprec.org/
On Wed, Jun 24, 2009 at 2:34 PM, Bryan McLellanbtm@loftninjas.org wrote:
On Tue, Jun 23, 2009 at 8:36 PM, Mike Baileymike@bailey.net.au wrote:
I noticed that the Opscode Chef cookbooks don't tend to support Ubuntu
Hardy (8.04.2).
I think it's mostly that Hardy doesn't have a couchdb package,
followed by most people develop on newer releases. Lots of cool new
technology between Hardy and Jaunty and all that.
On Wed, Jun 24, 2009 at 2:53 PM, Arjuna Christensenaj@opscode.com wrote:
Feel free to open tickets against the Cookbooks project (http://tickets.opscode.com/browse/COOK).
Thanks. I'll try to fix problems instead of just reporting them. 
Maybe a test integration run of the entire cookbooks as they stand now against 8.04.2 is in order?
Has anyone worked out how automate cookbook testing? That would be
very cool and could also be used by the monitoring system.
On 24/06/2009, at 9:57 PM, Mike Bailey wrote:
On Wed, Jun 24, 2009 at 2:53 PM, Arjuna Christensenaj@opscode.com
wrote:
Feel free to open tickets against the Cookbooks project (http://tickets.opscode.com/browse/COOK
).
Thanks. I'll try to fix problems instead of just reporting them.
Maybe a test integration run of the entire cookbooks as they stand
now against 8.04.2 is in order?
Has anyone worked out how automate cookbook testing? That would be
very cool and could also be used by the monitoring system.
I know a number of people are experimenting with Cucumber-driven
Cookbooks, but I'm not sure there is anything publicly published.
--
AJ Christensen, Software Engineer
Opscode, Inc.
E: aj@opscode.com
On Wed, Jun 24, 2009 at 5:57 AM, Mike Baileymike@bailey.net.au wrote:
On Wed, Jun 24, 2009 at 2:53 PM, Arjuna Christensenaj@opscode.com wrote:
Feel free to open tickets against the Cookbooks project (http://tickets.opscode.com/browse/COOK).
Thanks. I'll try to fix problems instead of just reporting them.
Maybe a test integration run of the entire cookbooks as they stand now against 8.04.2 is in order?
Has anyone worked out how automate cookbook testing? That would be
very cool and could also be used by the monitoring system.
Corey Haines and I started working on this GitHub - mikehale/chef-bdd: Cucumber for your chef cookbooks