[chef] Re: Re: Re: Install specific chef version using omnibus

[Daniel DeLeo < >]

On Wednesday, September 12, 2012 at 10:35 AM, Tim Smith wrote:

Bryan,

Has Opscode put together a policy on retention of previous versions of

Chef within the Omnibus installer? I am a bit hesitant to use a script to

install a very critical part of my infrastructure without certainty that

the version I need will be there in the future. Older versions of Chef 10

are already missing from apt.opscode.com, but the use of debs allows

anyone to archive off versions they rely on to a local repository. That

goes away if you rely on a script to install Chef. While I'd like to

always run the current release of Chef, parts of my infrastructure still

run on Chef .9 and upgrading it tricky sometimes. Will there be a posted

lifecycle for each release?

Thanks,

Tim

Just to be clear, the script is just a bit of magic to figure out which OS and CPU architecture you're on, the installation is done via whatever package manager is appropriate for your system.

If you go to http://www.opscode.com/chef/install/ and click through the drop-down menus, you can get links to the actual packages, which you can archive as needed. If you want to automate this process for various OSes and architectures, you can grab the Location headers from the download URL (or just follow the redirect):

http://www.opscode.com/chef/download?v=${version}&p=${platform}&pv=${platform_version}&m=${machine}

As far as a retention policy, we haven't decided anything yet, but it's not our intention to force people to upgrade to versions they're not ready for. Since the Omnibus packages are a new feature, we decided not to backport old versions of Chef, but this doesn't imply that older versions will be purged.

HTH,

-- 

Daniel DeLeo