[jira] [Commented] (BIGTOP-1746) Introduce the concept of roles in bigtop cluster deployment

["Evans Ye (JIRA)" <ji...@apache.org>]

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

Evans Ye commented on BIGTOP-1746:
----------------------------------

Hi [~vishnu] I'm sorry to get back for the review so late.
I did a review on your patch, but since the patch can't apply directly to the current master, I can not run tests for it. A question I'm curious about: why the hbase-master role implies zookeeper server installation?
{code}
23	    if ("hbase-master" in $roles) {
24	      include hadoop::init_hdfs
25	      include hadoop-hbase::master
26	      include hadoop-zookeeper::server
27	      Class['Hadoop::Init_hdfs'] -> Class['Hadoop-hbase::Master']
28	    }
{code}
I'm imaging that there should be a dependency to install zookeeper services somewhere else in the cluster, for example, {{Class['Hadoop::Zookeeper'] -> Class['Hadoop-hbase::Master']}} and then we can start to install hbase-master.
Am I getting it right?

The 1.0 is about to release, so If you're still interesting in contributing the feature, I'm being able to work with you to get it in. :)

> Introduce the concept of roles in bigtop cluster deployment
> -----------------------------------------------------------
>
>                 Key: BIGTOP-1746
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1746
>             Project: Bigtop
>          Issue Type: New Feature
>          Components: deployment
>    Affects Versions: 0.8.0
>            Reporter: vishnu gajendran
>            Assignee: vishnu gajendran
>              Labels: features
>             Fix For: 1.1.0
>
>         Attachments: BIGTOP-1746.patch, BIGTOP-1746.patch, BIGTOP-1746.patch
>
>
> Currently, during cluster deployment, puppet categorizes nodes as head_node, worker_nodes, gateway_nodes, standy_node based on user specified info. This functionality gives user control over picking up a particular node as head_node, standy_node, gateway_node and rest others as worker_nodes. But, I woulld like to have more fine-grained control on which deamons should run on which node. For example, I do not want to run namenode, datanode on the same node. This functionality can be introduced with the concept of roles. Each node can be assigned a set of role. For example, Node A can be assigned ["namenode", "resourcemanager"] roles. Node B can be assigned ["datanode", "nodemanager"] and Node C can be assigned ["nodemanager", "hadoop-client"]. Now, each node will only run the specified daemons. Prerequisite for this kind of deployment is that each node should be given the necessary configurations that it needs to know. For example, each datanode should know which is the namenode etc... This functionality will allow users to customize the cluster deployment according to their needs. 



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