ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15843) Adding Test Connection widget to a theme for custom service requires JS change
Date Wed, 13 Apr 2016 08:25:25 GMT

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

Hadoop QA commented on AMBARI-15843:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12798312/AMBARI-15843.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:green}+1 core tests{color}.  The patch passed unit tests in ambari-web.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6397//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6397//console

This message is automatically generated.

> Adding Test Connection widget to a theme for custom service requires JS change
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-15843
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15843
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.2.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15843.patch
>
>
> We have the information of Ranger KMS servers hosts in App.Hostcomponent model if the
cluster is installed. If not then its available in the localstorage. 
> It will be good to change the logic so that the source host while testing connection
is not derived from property but it is derived from component name. If theme definition can
have SOURCE_HOST = RANGER_KMS_SERVER, then UI code should be able to do the test connection
action without demanding a property like "ranger_kms_server_hosts" to be available in the
stack definition



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

Mime
View raw message