jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignasi Barrera (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-365) ChefSolo statement should not depend on InstallChefGems
Date Tue, 05 Nov 2013 22:50:18 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814355#comment-13814355
] 

Ignasi Barrera commented on JCLOUDS-365:
----------------------------------------

Revision here: https://github.com/jclouds/jclouds/pull/196

> ChefSolo statement should not depend on InstallChefGems
> -------------------------------------------------------
>
>                 Key: JCLOUDS-365
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-365
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-scriptbuilder
>            Reporter: Ignasi Barrera
>            Assignee: Ignasi Barrera
>            Priority: Minor
>              Labels: chef-solo
>             Fix For: 1.7.0
>
>
> There are two basic ways to install Chef to run Chef Solo: manually installing the Chef
gems, or using the Omnibus installer.
> Installing Chef should be a prerequisite for running the ChefSolo statement, and not
part/dependency of the statement itself. This will decouple the Solo execution from the way
Chef is installed and also allows to customize the installation (for example by configuring
a concrete Chef gem version, etc).



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message