ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rishi Pidva (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8166) Implement custom command for checking connectivity to KDC, via REST API
Date Tue, 06 Jan 2015 01:30:34 GMT

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

Rishi Pidva commented on AMBARI-8166:
-------------------------------------

Looks like trunk compilation is broken due to some other change (checked one of the previous
jobs which has same error). The latest patch only contains change in newly added test file.

> Implement custom command for checking connectivity to KDC, via REST API
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-8166
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8166
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-agent, ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Rishi Pidva
>              Labels: connectivity_, kdc, kerberos
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8166-v2.patch, AMBARI-8166-v3.patch, AMBARI-8166.patch, Screen
Shot 2014-11-04 at 11.16.41 PM.png
>
>
> There needs to be a way, given the details about a KDC to verify that Ambari and (optionally)
the nodes in the existing cluster can connect to it. 
> From the cluster hosts, this test should test that the address and port combinations
are reachable. 
> From the Ambari server, this test should make sure the administrator credentials allow
at least read access to the KDC.
> As an example of a similar action, see how Oozie does this for DB check pre install.



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

Mime
View raw message