ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay Srinivasaraghavan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13134) Stack advisor's recommendation should support both homogeneous and heterogenous nodes
Date Tue, 22 Sep 2015 07:55:04 GMT

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

Vijay Srinivasaraghavan updated AMBARI-13134:
---------------------------------------------
    Description: 
Stack advisor provides service component placement recommendations for any given set oif hosts
and services with the assumption that all the hosts are  homogeneous (same configuration -
cpu/memory). This limits the possibility of assigning hosts that are capable of being master
to associate master service components. 

By passing the host-group information with some hints specifying which distinction between
master and slave nodes, the stack advisor component could place the appropriate master service
components with the associated master hosts.

Stack advisor could parse the host group name ("masters" vs "slaves" vs "clients") and identifies
if the hosts could be treated as master or slave. In the absence of the "hint", all the hosts
will be assumed to be homogeneous (default/current implementation)   

"name":"masters-host-group1"
"name":"slaves-host-group1"
"name":"clients-host-group1"
/api/v1/stacks/HDP/versions/2.3/recommendations
{
   "hosts":[
      "host1",
      "host2"
   ],
   "services":[
      "HDFS",
      "YARN",
      "MAPREDUCE2",
      "ZOOKEEPER"
   ],
   "recommendations":{
      "blueprint":{
         "host_groups":[
            {
               "name":"masters-host-group1",
               "components":[
               ]
            },
            {
               "name":"slaves-host-group1",
               "components":[
               ]
            },
            {
               "name":"clients-host-group1",
               "components":[
               ]
            }
         ]
      },
      "blueprint_cluster_binding":{
         "host_groups":[
            {
               "name":"masters-host-group1",
               "hosts":[
                  {
                     "fqdn":"host1"
                  }
               ]
            },
            {
               "name":"slaves-host-group1",
               "hosts":[
                  {
                     "fqdn":"host2"
                  }
               ]
            },
            {
               "name":"clients-host-group1",
               "hosts":[
                  {
                     "fqdn":"host3"
                  }
               ]
            }
         ]
      }
   },
   "recommend":"host_groups"
}

  was:
Stack advisor provides service component placement recommendations for any given set oif hosts
and services with the assumption that all the hosts are  homogeneous (same configuration -
cpu/memory). This limits the possibility of assigning hosts that are capable of being master
to associate master service components. 

By passing the host-group information with some hints specifying which distinction between
master and slave nodes, the stack advisor component could place the appropriate master service
components with the associated master hosts.

Stack advisor could parse the host group name ("masters" vs "slaves") and identifies if the
hosts could be treated as master or slave. In the absence of the "hint", all the hosts will
be assumed to be homogeneous (default/current implementation)   

"name":"masters-host-group1"
"name":"alsves-host-group1"
/api/v1/stacks/HDP/versions/2.3/recommendations
{
   "hosts":[
      "host1",
      "host2"
   ],
   "services":[
      "HDFS",
      "YARN",
      "MAPREDUCE2",
      "ZOOKEEPER"
   ],
   "recommendations":{
      "blueprint":{
         "host_groups":[
            {
               "name":"masters-host-group1",
               "components":[
               ]
            },
            {
               "name":"slave-host-group1",
               "components":[
               ]
            }
         ]
      },
      "blueprint_cluster_binding":{
         "host_groups":[
            {
               "name":"masters-host-group1",
               "hosts":[
                  {
                     "fqdn":"host1"
                  }
               ]
            },
            {
               "name":"slaves-host-group1",
               "hosts":[
                  {
                     "fqdn":"host2"
                  }
               ]
            }
         ]
      }
   },
   "recommend":"host_groups"
}


> Stack advisor's recommendation should support both homogeneous and heterogenous nodes
> -------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13134
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13134
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server, blueprints
>    Affects Versions: trunk
>            Reporter: Vijay Srinivasaraghavan
>            Assignee: Srimanth Gunturi
>
> Stack advisor provides service component placement recommendations for any given set
oif hosts and services with the assumption that all the hosts are  homogeneous (same configuration
- cpu/memory). This limits the possibility of assigning hosts that are capable of being master
to associate master service components. 
> By passing the host-group information with some hints specifying which distinction between
master and slave nodes, the stack advisor component could place the appropriate master service
components with the associated master hosts.
> Stack advisor could parse the host group name ("masters" vs "slaves" vs "clients") and
identifies if the hosts could be treated as master or slave. In the absence of the "hint",
all the hosts will be assumed to be homogeneous (default/current implementation)   
> "name":"masters-host-group1"
> "name":"slaves-host-group1"
> "name":"clients-host-group1"
> /api/v1/stacks/HDP/versions/2.3/recommendations
> {
>    "hosts":[
>       "host1",
>       "host2"
>    ],
>    "services":[
>       "HDFS",
>       "YARN",
>       "MAPREDUCE2",
>       "ZOOKEEPER"
>    ],
>    "recommendations":{
>       "blueprint":{
>          "host_groups":[
>             {
>                "name":"masters-host-group1",
>                "components":[
>                ]
>             },
>             {
>                "name":"slaves-host-group1",
>                "components":[
>                ]
>             },
>             {
>                "name":"clients-host-group1",
>                "components":[
>                ]
>             }
>          ]
>       },
>       "blueprint_cluster_binding":{
>          "host_groups":[
>             {
>                "name":"masters-host-group1",
>                "hosts":[
>                   {
>                      "fqdn":"host1"
>                   }
>                ]
>             },
>             {
>                "name":"slaves-host-group1",
>                "hosts":[
>                   {
>                      "fqdn":"host2"
>                   }
>                ]
>             },
>             {
>                "name":"clients-host-group1",
>                "hosts":[
>                   {
>                      "fqdn":"host3"
>                   }
>                ]
>             }
>          ]
>       }
>    },
>    "recommend":"host_groups"
> }



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

Mime
View raw message