jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-365) ChefSolo statement should not depend on InstallChefGems
Date Tue, 12 Nov 2013 10:49:17 GMT

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

ASF subversion and git services commented on JCLOUDS-365:
---------------------------------------------------------

Commit cccdb756d14b9c62295e0df9ded5fab5256227ed in branch refs/heads/master from [~nacx]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=cccdb75 ]

JCLOUDS-365: ChefSolo should not depend on InstallChefGems


> 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