You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Ignasi Barrera (JIRA)" <ji...@apache.org> on 2013/09/17 10:32:51 UTC

[jira] [Created] (JCLOUDS-286) Use the Omnibus installer to install the Chef client

Ignasi Barrera created JCLOUDS-286:
--------------------------------------

             Summary: Use the Omnibus installer to install the Chef client
                 Key: JCLOUDS-286
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-286
             Project: jclouds
          Issue Type: Improvement
          Components: jclouds-chef, jclouds-scriptbuilder
    Affects Versions: 1.6.2
            Reporter: Ignasi Barrera
            Assignee: Ignasi Barrera
             Fix For: 1.7.0


Currently, when running Chef Solo or Chef to bootstrap a node, the Chef client is manually installed. The installation prices installs Ruby, RubyGems, and the Chef gems.

Since gems in ruby are automatically updated and the latest version is downloaded, this procedure may get broken when a (backwards incompatible) new version of the chef-client gem is published. This can be workarouned by specifying the versions of Ruby and the Chef gems to install when creating a ChefContext or building a ChefSolo script, but still isn't string enough.

Opscode released Omnibus, to easily install the chef-client and all its dependencies. The Omnibus installer will detect the operating system of the node, and install an appropriate Ruby and RubyGems distribution compatible with the desired chef-client version, so it should be the preferred way to install Chef. This will simplify a lot the Chef bootstrap script and reduce considerably the points where failures can happen.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira