Hi Chefs,
We’ve released an updated Chef 11 Client beta.
Changes
Installing
To install the omnibus package using the installer:
wget -qO- "https://www.opscode.com/chef/install.sh" | sudo bash -s -- -p
To install via rubygems:
gem install chef --pre
(note: gem will be pushed after rubygems.org maintenance is completed).
As always, please report any bugs you find here or on tickets.opscode.com.
–
Daniel DeLeo
Question: Will the standard omnibus form start automatically shipping Chef
11 once it's released? (ie; no "-- -p" required anymore)
If so, for those of us that need to make code changes and tweaks, will
there be a way to force install chef 10.18 (or whatever) from omnibus until
we are ready for Chef 11?
Thank you!
Brian
On Wed, Jan 30, 2013 at 10:52 AM, Daniel DeLeo dan@kallistec.com wrote:
Hi Chefs,
We've released an updated Chef 11 Client beta.
Changes
Installing
To install the omnibus package using the installer:
wget -qO- "https://www.opscode.com/chef/install.sh" | sudo bash -s --
-p
To install via rubygems:
gem install chef --pre
(note: gem will be pushed after rubygems.org maintenance is completed).
As always, please report any bugs you find here or on tickets.opscode.com.
--
Daniel DeLeo
On Wednesday, January 30, 2013 at 8:01 AM, Brian Hatfield wrote:
Question: Will the standard omnibus form start automatically shipping Chef 11 once it's released? (ie; no "-- -p" required anymore)
When using the installer script, you automatically get the latest release Omnibus package. The -p flag means "prerelease." Side note: I would've preferred --prerelease, but portable shell scripting.
If so, for those of us that need to make code changes and tweaks, will there be a way to force install chef 10.18 (or whatever) from omnibus until we are ready for Chef 11?
You can pass the -v VERSION flag to the installer script to specify the desired version. Note that the default knife bootstrap template does this automatically, so it installs the version of Chef that you have (but be careful if you want to use Chef 11 for knife on your workstation before upgrading to Chef 11 on your nodes). You can also browse the available (release-only) packages on http://www.opscode.com/chef/install/, download them, and install them by whatever means fits with your environment.
Thank you!
Brian
HTH,
--
Daniel DeLeo
I forgot to mention that we also fixed a bug in the packaging where the new chef-apply and chef-shell commands were not being linked [CHEF-3802]. I was only looking at the git log for chef itself. Apologies.
--
Daniel DeLeo
On Wednesday, January 30, 2013 at 7:52 AM, Daniel DeLeo wrote:
Hi Chefs,
We've released an updated Chef 11 Client beta.
Changes
Installing
To install the omnibus package using the installer:
wget -qO- "https://www.opscode.com/chef/install.sh" | sudo bash -s -- -p
To install via rubygems:
gem install chef --pre
(note: gem will be pushed after rubygems.org (http://rubygems.org) maintenance is completed).
As always, please report any bugs you find here or on tickets.opscode.com (http://tickets.opscode.com).
--
Daniel DeLeo