You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/11/21 19:30:34 UTC

[jira] [Commented] (BIGTOP-1161) Have a way to dynamically select components to be deployed by Puppet recipes.

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

jay vyas commented on BIGTOP-1161:
----------------------------------

i just looked at the {{components[0]==undef}} code block.  initially it was a little confusing why it was there, then i realized that its to provide *backwards compatibility*.   will update the READMe/comments in BIGTOP-1365.  but just leaving this comment for folks wondering the same thing that i was :)

> Have a way to dynamically select components to be deployed by Puppet recipes.
> -----------------------------------------------------------------------------
>
>                 Key: BIGTOP-1161
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1161
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: deployment
>    Affects Versions: 0.7.0
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>              Labels: hackathon-12-2013
>             Fix For: 0.8.0
>
>         Attachments: BIGTOP-1161.patch
>
>
> There are situations where installing the whole stack of the components into a designated cluster is too heavy for development or testing purposes. Say, at times I want to have just HDFS and HBase, or HDFS, MR, and Pig. 
> Currently, you'll have to hack into {{cluster.pp}} and remove parts of the recipe. 
> It'd be great to have an ability to configure the set of the components in the {{config/site.csv}} and only those configured would be deployed. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)