Skip to content

Instantly share code, notes, and snippets.

@danielsdeleo
Last active December 19, 2015 15:29
Show Gist options
  • Select an option

  • Save danielsdeleo/5976964 to your computer and use it in GitHub Desktop.

Select an option

Save danielsdeleo/5976964 to your computer and use it in GitHub Desktop.
Updated Chef 11.6 Release Candidate Available

Hi Chefs,

Since we announced the 11.6 Release Candidate, we've been busy running test scenarios to verify new features and bug fixes. This round of testing is complete, and we've released a new RC with a handful of fixes. Unless any new issues are found, this RC will become the 11.6.0 release. If you've been wondering how you can contribute to Chef, testing this release in your environment is a great way to help out.

For the full list of changes in this release, please see the draft release notes:

http://docs.opscode.com/release_notes.html

Installing the RC w/ rubygems:

gem install chef ohai mixlib-shellout --pre

Installing the RC w/ Magical Shell Script:

curl -L "https://www.opscode.com/chef/install.sh" | sudo bash -s -- -p

Omnibus Package Links

Links for most platforms are below. Only the 64-bit versions are shown for Intel-based platforms. If you need a 32-bit package, use the shell script installer, or see the "omnitruck API" instructions.

Ubuntu 13.04

url https://opscode-omnibus-packages.s3.amazonaws.com/ubuntu/13.04/x86_64/chef_11.6.0.rc.2-1.ubuntu.13.04_amd64.deb md5 98c5443fcdc46aee75da4205d267185a sha256 aa02aeebc5bee581c629c7519b1fc5a8bbf0e4175fcba5ebacf5d17a85ce283c

Ubuntu 12.04

url https://opscode-omnibus-packages.s3.amazonaws.com/ubuntu/12.04/x86_64/chef_11.6.0.rc.2-1.ubuntu.12.04_amd64.deb md5 6c7beae3515e2925ace345616c0527fe sha256 e0b2cf96a6cdea2b8b8e54f644ef2239b7c015b3e0fc866adcc13f0c1ece7ad2

Ubuntu 10.04

url https://opscode-omnibus-packages.s3.amazonaws.com/ubuntu/10.04/x86_64/chef_11.6.0.rc.2-1.ubuntu.10.04_amd64.deb md5 f6dbc2c1b760f3a652e54e4aead8b8b7 sha256 90f34bb9fc8ec2d848c38d79d4110bfd25cf571fec7047656b2abf91c7e1ae7a

RHEL/CentOS 6, SuSE Enterprise 12

url https://opscode-omnibus-packages.s3.amazonaws.com/el/6/x86_64/chef-11.6.0.rc.2-1.el6.x86_64.rpm md5 e5520f33bd85fd1606d7fdfca63eab38 sha256 eaacd90f59f9422304eb87ef3c3e2999425f93c9933b13dd0a02198fecf027f5

RHEL/CentOS 5, SuSE Enterprise 11

url https://opscode-omnibus-packages.s3.amazonaws.com/el/5/x86_64/chef-11.6.0.rc.2-1.el5.x86_64.rpm md5 0e4b9fc0a7721106242bff7aa4c20630 sha256 c82532d921d687fe110d610a6442b14b634c70d33ead3f0743358b135a1fae3e

Debian

url https://opscode-omnibus-packages.s3.amazonaws.com/debian/6/x86_64/chef_11.6.0.rc.2-1.debian.6.0.5_amd64.deb md5 a7117c3b5cf2cac20a30d53c9fe20a74 sha256 4c585a7d117a857ae45aac80c24cbdf7af9605ac8a8dd2bc13f650daa99da6ec

Windows MSI

url https://opscode-omnibus-packages.s3.amazonaws.com/windows/2008r2/x86_64/chef-client-11.6.0.rc.2-1.windows.msi md5 eaf9d428b742e3c0d5cf93198d8fcf42 sha256 b55070fa9dd5cf263d003ef361be9f6278b21dad212f24efbd832bbe0fcedc71

Solaris (Intel)

url https://opscode-omnibus-packages.s3.amazonaws.com/solaris2/5.10/i386/chef.11.6.0.rc.2-1.solaris2.5.10.i386.solaris md5 aca8a8625701e726417370dd28b316be sha256 5fb1a1f53a76bc9a1f6d3973fc7f546c24d2c688ca13830cf98a5a53f2607715

Solaris (SPARC)

url https://opscode-omnibus-packages.s3.amazonaws.com/solaris2/5.9/sparc/chef.11.6.0.rc.2-1.solaris2.5.9.sparc.solaris md5 4f3a42a782be728702544c38c519bc91 sha256 10bec780681bb6aa863e465e94369c899c2241cd21d340469688f4cf95741b51

Omnitruck API

To fetch a package URL and checksums, you can use the Omnitruck metadata API:

curl 'https://www.opscode.com/chef/metadata?p=ubuntu&pv=13.04&m=x86_64&prerelease=true'

Valid values for platform, platform version, and architecture are defined here: https://github.com/opscode/omnibus-chef/blob/master/jenkins/chef.json

@adamedx
Copy link

adamedx commented Jul 11, 2013

Tried Windows link and it works for me, so looks good. I'm curious about the order in which platforms are listed -- is there a particular reason for the order (e.g. most popular distribution), or was it just arbitrary?

Are there any caveats to gem install approach? They'll still end up with the same gems as if they had installed via Omnibus, correct?

@danielsdeleo
Copy link
Author

Order is sorta popularity based, I haven't looked at the metrics in a while.

The gem install command will get you all 3 of the RCs we have in-flight right now. Dependency gems might differ from omnibus, but that's the same caveat as always with gem installs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment