You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2013/11/25 19:36:38 UTC
[jira] [Commented] (JCLOUDS-276) Extend the BootstrapConfiguration
in jclouds-chef to customize the chef-client run
[ https://issues.apache.org/jira/browse/JCLOUDS-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831734#comment-13831734 ]
Andrew Bayer commented on JCLOUDS-276:
--------------------------------------
Is this going to actually get done in the next two weeks, or should it move to post-1.7.0?
> 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
> Fix For: 1.7.0
>
>
> 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.1#6144)