[
https://issues.apache.org/jira/browse/AMBARI-15443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202849#comment-15202849
]
Hadoop QA commented on AMBARI-15443:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12794184/AMBARI-15443.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server ambari-web:
org.apache.ambari.server.state.cluster.ClustersDeadlockTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5935//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5935//console
This message is automatically generated.
> Make Host bulk command menu item list stack driven instead of a hardcoded
> list in UI code
> -----------------------------------------------------------------------------------------
>
> Key: AMBARI-15443
> URL: https://issues.apache.org/jira/browse/AMBARI-15443
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, ambari-web
> Affects Versions: trunk
> Reporter: Di Li
> Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-15443.patch
>
>
> The items described here are the ones on the Hosts tab, in the Actions
> drop-down list where the UI shows entries such as All Hosts. If user mouses
> over the All Hosts, it shows a sub-list including Hosts and slave components.
> The slave component items are hardcoded in hosts_table_menu_view.js as shown
> below. This jira is to put this info into each service's metainfo.xml so that
> the slave component items can be stack driven.
> components: function () {
> var serviceNames = App.Service.find().mapProperty('serviceName');
> var menuItems = [
> O.create({
> serviceName: 'HDFS',
> componentName: 'DATANODE',
> masterComponentName: 'NAMENODE',
> componentNameFormatted: Em.I18n.t('dashboard.services.hdfs.datanodes')
> }),
> O.create({
> serviceName: 'YARN',
> componentName: 'NODEMANAGER',
> masterComponentName: 'RESOURCEMANAGER',
> componentNameFormatted:
> Em.I18n.t('dashboard.services.yarn.nodeManagers')
> }),
> O.create({
> serviceName: 'HBASE',
> componentName: 'HBASE_REGIONSERVER',
> masterComponentName: 'HBASE_MASTER',
> componentNameFormatted:
> Em.I18n.t('dashboard.services.hbase.regionServers')
> }),
> O.create({
> serviceName: 'STORM',
> componentName: 'SUPERVISOR',
> masterComponentName: 'SUPERVISOR',
> componentNameFormatted:
> Em.I18n.t('dashboard.services.storm.supervisors')
> })];
> return menuItems.filter(function (item) {
> return serviceNames.contains(item.serviceName);
> });
> }.property(),
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
