[jira] [Resolved] (JCLOUDS-276) Extend the BootstrapConfiguration in jclouds-chef to customize the chef-client run

["Ignasi Barrera (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCLOUDS-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ignasi Barrera resolved JCLOUDS-276.
------------------------------------

       Resolution: Not a Problem
    Fix Version/s:     (was: 1.7.3)

After thinking about the better way to fix this, I've come to the conclusion that this shouldn't be done in jclouds.

The common way to achieve this in Chef is to let users add the chef-client cookbook to the node http://community.opscode.com/cookbooks/chef-client). It allows to schedule the chef-client and configure all its options.

Implementing this in jclouds would force us to keep in sync with the chef-client parameters, and also support its multiple versions, so we'd better do it "the Chef way" and just close this issue.

> Extend the BootstrapConfiguration in jclouds-chef to customize the chef-client run
> ----------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-276
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-276
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-chef
>    Affects Versions: 1.6.2
>            Reporter: Ignasi Barrera
>            Assignee: Ignasi Barrera
>            Priority: Minor
>
> Currently the BootstrapConfiguration object allows to customize the run list of a node and the environment where it should be registered. It should be extended to allow to configure other chef-client parameters, so it can be scheduled, configured as a daemon, etc.
> All the information could be stored in a "chef-client" key in the bootstrap data bag so it can be reused by all the nodes in the same group.



--
This message was sent by Atlassian JIRA
(v6.2#6252)